Sadly I have lost a second blog post

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Sadly I have lost a second blog post

Leo Liu-5

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. Some post I wrote on the 8 March. To prevent me from
losing more posts I think I will leave weblogger alone for quite a while
until I find time to fix it to suit my needs. :(

Leo



_______________________________________________
Emacsweblogs mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/emacsweblogs
Reply | Threaded
Open this post in threaded view
|

Re: Sadly I have lost a second blog post

Mark A. Hershberger
Leo <[hidden email]> 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
[hidden email]
http://lists.nongnu.org/mailman/listinfo/emacsweblogs
Reply | Threaded
Open this post in threaded view
|

Re: Sadly I have lost a second blog post

leon-8
Hello Mark,

It wasn't C-c C-k due to the first lost post, I have been very careful
with it. I can't recall the exact sequence of events, roughly:

I wrote the post and then C-x C-s but there was some sort of error so
I pasted the post directly into blogger instead. Then I came back to
that buffer in emacs and tried C-x C-s again to get the same error,
eventually I killed that buffer (I can't remember which command I used
to kill the buffer) and another buffer showed up showing the content
of another post and this buffer was killed by C-x k. I was in a hurry
to leave so I didn't check what's happening on the server until the
next day.

Best wishes,

Leo

On 21 March 2010 03:09, Mark A. Hershberger <[hidden email]> wrote:

> Leo <[hidden email]> 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
[hidden email]
http://lists.nongnu.org/mailman/listinfo/emacsweblogs