* Rocco Rutte <[EMAIL PROTECTED]> [2002-03-21 01:01]: > > The pipe command doesn't save the output of the > > command as a new version of the message. It also > > doesn't mark the original message as deleted. > > Right. But why not write a macro which: > 1) pipes the message to a command (this command may > be a shell script using another instance of Mutt > to send the *changed* mail to yourself), > 2) marks the old message as deleted and > 3) syncs the mailbox > ? > > Should even fit on a line in your config > as works by pressing just *one* key.
well, you can put everything on one key, but... you don't want this if some part of the command sequence fails, right? so many things can go wrong here. i would not issue a delete command if I was not really sure. in this case this means that the changed messages arrives in the mailbox. but how can you make sure about this? this certainly needs extra code in mutt. and it cannot be 100% sure as the message has been changed, right? I think it is better to copy the message to the current folder and editing that copy. It's yet another workaround - but not a bad one, is it? :-) Sven
