mutt c.f. MH: tell us more
Posted Jun 17, 2004 13:53 UTC (Thu) by mmarsh
In reply to: mutt c.f. MH: tell us more
Parent article: The Grumpy Editor's guide to mail clients: introduction
I think the "restrictiveness" that MH users (myself included) feel is not so much specific to mutt, but rather driven by the flexibility of MH. The fact that I can compose a message or a reply and while that's still active check out new mail (or cross-reference another message) is extremely useful, and what prompted me to switch from elm. I've also had situations where I'll be writing a message to a friend, and in the meantime another message comes in that demands immediate response. With a "drafts" folder in MH, this is no problem. Putting aside a message for later is also easy, though I'm sure mutt also has this capability.
Granted, some or all of these things can be done with the graphical mail clients. However, if you're using a terminal-based client, it's really tough to beat the level of flexibility in MH, and that flexibility comes from the fact that it's not a single client, but a suite of applications that run on the same directory structure.
That being said, MH isn't the only mail software I use. Since my mail has to be fetched via IMAP, I use fetchmail (both at work and at home). At work my script for fetchmail passes the messages to procmail for filtering, and I check the messages marked as spam using mutt. That's mainly because I've had some spam messages cause inc to segfault.
Another mail suite I could point out is IM, which seems to be included in mew (at least on RH). It's MH-like, and uses the same directories. It knows imap, though, which is nice, though it doesn't know krb5 in the context of imap. IM and MH are fairly easy to combine -- the only thing I had to do was use "imget" instead of "inc" -- but it doesn't update the MH context, so after getting new mail "curr" isn't updated.
to post comments)