Robert Elz <[email protected]> writes: > In particular, given recent discussions, vi is one of my common tools > (others prefer different editors, which editor isn't important, substitute > emacs if you're a heretic, or perhaps something else), and one of my sh funcs > is "vim" which simply applies vi to a set of MH compatible args, so I can > vim last +inbox > or anything else like that). And given the editor (whichever editor) and > a message, I change *anything* in it that I feel needs changing (headers, > body, anywhere).
vi $(, show last -path) This works for maildirs as well, but probably messes up any caching done by applications that read the Maildir. coma will probably get a command to force re-caching after such operations. It would also be not very hard to move/rename the edited messages in a script. > Aside from that, all the standard file operation commands get used a lot > (mv cp ln mkdir ...) and the searching tools (grep, ... - as well as pick, > depending upon what I need) and various analysis tools (file, size, wc, ...). All these work as well, but of course grep is only useful for non-MIME mail. > Just making show scan pick (et al) work is not supplying an MH environment. That's why I chose Maildir. > I guess I should really make it also be able to be given vi args, +/ etc, > but I haven't had that need yet. I use this A LOT - sometimes just so I > can read raw mail (without it being decoded at all, and giving me 100% > confidence that is what is happening) and sometimes to make changes. For raw mail, in coma you also can use , show -raw. -- Christian Neukirchen <[email protected]> http://chneukirchen.org _______________________________________________ Nmh-workers mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/nmh-workers
