Leo <sdl....@gmail.com> writes: > I did for the first time publishing from weblogger yesterday, I just > found out today that a post got overridden and there's no way to find > the content back.
Leo, I'm so sorry to here this. I'd like to work on the problem, but I'll need some idea of what you were doing when working on it. I assume this wasn't caused by the behavior of C-c C-k that you mentioned before? If that was the problem, there is an easy fix that I've already applied, but wanted to have more changes before making a full release. Look for, and comment out the line that looks like this: (define-key map "\C-c\C-k" 'weblogger-delete-entry) Another way I've seen that problem caused is when weblogger.el “does too much” during weblogger-next-entry and weblogger-prev-entry. I need to do more work on tracking that particular bug down, but I think it can be solved with the following patch: --- weblogger.el 2010-03-11 06:53:33 +0000 +++ weblogger.el 2010-03-21 03:08:18 +0000 @@ -1001,7 +1001,7 @@ "Move to the entry identified by NUM in the ring. If RELATIVE is set, then add it to the current index and go to that entry." (if (buffer-modified-p) - (weblogger-save-entry nil nil)) + (error "Save this entry first!")) (unless weblogger-entry-list (weblogger-api-list-entries weblogger-max-entries-in-ring)) (let ((entry-id (if relativep If you've run into this problem some other way, then please let me know so I can work on tracking it down. Mark. -- http://hexmode.com/ The world is a dangerous place, not because of those who do evil, but because of those who look on and do nothing. — Albert Einstein _______________________________________________ Emacsweblogs mailing list Emacsweblogs@nongnu.org http://lists.nongnu.org/mailman/listinfo/emacsweblogs