* Derek Martin <inva...@pizzashack.org> [2013-02-02 11:44 -0600]:
[save-message]
> Now, I will grant you, this feature is a bit schizophrenic.  It also
> assumes that once it has done whatever it's going to do, that you no
> longer want the existing copy of the message, and marks it for
> deletion.  At which point I have to go and undelete it, which I've
> always found annoying.  Because when I use this feature, I do in fact
> want a separate copy of the message.  Pretty much always.  I suspect
> that it behaves this way because ME (I'm assuming) decided that the
> two operations, moving a message to another folder, and saving a
> message to a file, were functionally equivalent, and therefore elected
> for the economy of only implementing one.  Trouble is, in neither case
> does it really do what the user wants it to do, IMO.  What the user
> really wants, I believe, are the three behaviors I described above.

There is <copy-message> (bound to C by default).

Nicolas
-- 
http://www.rachinsky.de/nicolas

Reply via email to