Discussion:
[VM] returning from virtual folders
Julian Bradfield
2012-03-11 14:20:02 UTC
Permalink
The new feature that quitting a virtual folder preserves the current
message, is sometimes useful. More often, for me, it's annoying to
have my place lost in the main folder.
Could it be customizable?
And I'd suggest that it would be good to set the mark in the main
folder summary at the previous current message (for the new
behaviour), or what would be the new current message (for the old
behaviour).
Uday Reddy
2012-03-11 19:12:57 UTC
Permalink
Post by Julian Bradfield
The new feature that quitting a virtual folder preserves the current
message, is sometimes useful. More often, for me, it's annoying to
have my place lost in the main folder.
Could it be customizable?
Indeed, making it "customizable" is a good idea.

One possibility is to use the distinction between `vm-quit' and
`vm-quit-no-change'. `vm-quit' in a virtual folder used to do expunging and
saving etc., which was undesirable in an interactive virtual folder. I
believe the current trunk has gotten rid of all of that. So, there is no
difference between `vm-quit' and `vm-quit-no-change' at the moment.

We could say that `vm-quit-no-change' returns you to the original message in
the base folder and `vm-quit' returns you to the current message in the base
folder.

Do you think that would be enough?
Post by Julian Bradfield
And I'd suggest that it would be good to set the mark in the main
folder summary at the previous current message (for the new
behaviour), or what would be the new current message (for the old
behaviour).
Is this about the old bug report

https://bugs.launchpad.net/vm/+bug/936517

That is fixed in the trunk.

Cheers,
Uday
Julian Bradfield
2012-03-11 20:10:17 UTC
Permalink
Post by Uday Reddy
We could say that `vm-quit-no-change' returns you to the original message in
the base folder and `vm-quit' returns you to the current message in the base
folder.
That's a good idea - I didn't think of that.
Post by Uday Reddy
Post by Julian Bradfield
And I'd suggest that it would be good to set the mark in the main
folder summary at the previous current message (for the new
behaviour), or what would be the new current message (for the old
behaviour).
Is this about the old bug report
No. It's about making it easy to do the other thing from the one you
actually did!
Uday Reddy
2012-03-11 20:22:55 UTC
Permalink
Post by Julian Bradfield
Post by Uday Reddy
Post by Julian Bradfield
And I'd suggest that it would be good to set the mark in the main
folder summary at the previous current message (for the new
behaviour), or what would be the new current message (for the old
behaviour).
Is this about the old bug report
No. It's about making it easy to do the other thing from the one you
actually did!
In that case, I need you to amplify the point. What do you mean by "the
mark"? Emacs mark? VM is not in the habit of changing the Emacs mark.

VM doesn't have any other mark that I know of.

I could perhaps put a message on the stack so that vm-goto-message-last-seen
finds it.

Cheers,
Uday
Uday S Reddy
2012-03-11 20:53:00 UTC
Permalink
Post by Uday Reddy
I could perhaps put a message on the stack so that vm-goto-message-last-seen
finds it.
vm-goto-message-last-seen already works for the new behaviour.

Cheers,
Uday

Continue reading on narkive:
Loading...