vm-unload-message confuses regular folder

[John Hein]

rev 1209

I inadvertently hit 'O' in a regular folder (not imap) and now can't save the changes I made. When I hit 'S', I get:

This is currently available only for imap folders.

[Uday Reddy (reddyuday)]

John Hein writes:

> Public bug reported:
>
> rev 1209
>
> I inadvertently hit 'O' in a regular folder (not imap) and now can't
> save the changes I made. When I hit 'S', I get:

Hi John, my usual prescription is that when things go wrong like this,
the folder should not be saved. The disk copy would be fine on its
own, and you don't want to overwrite it.

One possible recovery option is to go back to the message that is
supposedly unloaded, and type 'o' to make it "loaded" again. That
might reset its state.

But I will take a look at the general problem in detail in any case.

Cheers,
Uday

[John Hein (xpqheqdvq4)]

Unfortunately, I don't remember the message I "unloaded". But marking all the messages and doing M N o didn't help. I still get the "only for imap" complaint.

And the file on disk is not okay - it's missing lots of changes (and there's no #foo# file to restore). And I can't write it to a different file (C-x C-w). I'm trying to figure out a way to get it saved to another file right now.

By the way, a backtrace (not that it's that useful):

Debugger entered--Lisp error: (error "This is currently available only for imap folders.")
  signal(error ("This is currently available only for imap folders."))
  error("This is currently available only for imap folders.")
  vm-discard-real-message-body([[#<marker at 180321652 in Ic> #<marker at 180321652 in Ic>$
  vm-discard-fetched-messages()
  vm-save-folder(nil)
  call-interactively(vm-save-folder nil nil)

[Uday Reddy (reddyuday)]

Here is quick patch that will allow you to save the file.

Cheers,
Uday

[Uday Reddy (reddyuday)]

Dear John, did you get to save the folder? Did the patch work?

[John Hein (xpqheqdvq4)]

Yes, I could save it and the patch worked - just got a chance to try it. Thanks.

[John Hein (xpqheqdvq4)]

And rev 1212 (well, 1210, I suppose) closes this bug in quick testing.

[Uday Reddy (reddyuday)]

Revision 1220.1.2 adds another fix.