The tools I use to read email affect how I read it (more than I thought)

October 8, 2023

Up until recently, I read most of my email with exmh, a graphical X frontend on (N)MH, and some of it with command line NMH tools. I've used exmh at work for a long time, and then at home from early 2020 onward (when I started working from home a lot). Recent changes in my home Internet made using exmh from home less pleasant, so I started trying out the only other current (N)MH frontend that I know of, MH-E in GNU Emacs. Initially this was only from home, but then I started using it at work as well, partly with the excuse of building up familiarity with it faster (and sanding off a whole assortment of rough edges faster).

Since both exmh and MH-E are frontends on the same core of NMH, I didn't expect my mail reading to be much changed by using MH-E at home, although I did expect to miss several features exmh has that MH-E doesn't. To my surprise, things didn't work out like that at all. One of the most visible signs of the shift to me is that I'm back to reading technical mailing lists, after mostly stopping earlier. Another sign of the shift is that I dove into several historical 'dumping ground' folders and cleaned them out, and my inbox is probably more under control than before (I don't keep my inbox empty).

Although I can't be completely sure, I feel that I can put my finger on a few MH-E features that have enabled this. One is that MH-E makes it easy for me to get a large scale summary of a folder (including my inbox). Normal mail clients, including exmh, more or less statically divide space between a 'message list' section and a section for the message you're reading. MH-E has this distinction too, but because everything is Emacs buffers it's natural to expand the message list to take up all of the space when you're not looking at a message, and then if you look at a message it goes back to the split.

A second feature is MH-E's support for a threaded message list display. MH-E's threading is fast to turn on and off, and it makes it easy to blast through a thread all at once (or kill it, in some cases). Being able to see a thread in my inbox all at once encourages me to delete all of it at once if the thread is now closed and I don't need to keep track of it any more, and the thread display makes these blocks of discussions much more obvious in the first place. Threads also make it easier to read technical mailing lists (and to rapidly skip things I don't really care about).

(One reason to be slightly dubious that these features are all of the story is the well known effect where if you start paying attention to something, you tend to do it more and better for a while. There's also the 'Ikea effect', where you have more affection for things that you've put together yourself. I've been doing a lot of putting together of my MH-E Emacs setup.)

There are definitely things from exmh that I still miss and that I feel make me less productive in some ways in MH-E. But it's clear that using MH-E has changed my mail reading behavior in positive ways too, and far more than I expected. So this is yet another illustration that the specifics of tools can matter more than I expected, and small elements can have outsized effects (as can elements I discount the importance of, like a thread display of mail).


Comments on this page:

I just about remember my switch from Windows to Linux, almost 20 years ago. The two big main blockers were finding and getting used to how to edit text files and how to do mail. Getting mail set up was far more complicated than what I was used to on Windows where machine-local email is not a thing, so the MTA/MDA/MUA split just doesn’t exist, and every client can and must assume you have an upstream SMTP/POP/IMAP server that you can just configure in the settings and you’re good to go. But I had the fortune of being told to go with mutt as my MUA, and oh my goodness, it had threads. The GUI clients I was used to did not. It was a night and day difference in keeping on top of mailing lists. I really can’t overstate it. And it got even better still when I had the bright idea to throw out the inbox/outbox split that every client I had used before had, by having mutt Fcc my own mail to the inbox instead of a separate folder: then I could use threading for my non-list correspondence too – threading in all folders, for everything.

Once I got to that point, I’d go on and on about how great this was whenever there was a conversation to which it was relevant. And then GMail came out a year or two later and made something very similar available to everyone, without having to set up mail on a Unixoid system. Today all graphical clients have at least a conversation view for mail threads, if not full threading. So I long since stopped talking about it.

I’ll be surprised if you find the benefit of this change wearing off with the novelty. I expect it to stick.

By Yeechang Lee at 2023-10-10 04:06:32:

I have used Emacs VM to read mail for almost three decades now, and until your comment today had never considered whether and how its behavior (similarly varying between just a list of messages, just one message, or two buffers showing both) has affected my reading habits. I do believe that using VM overall is a superpower for email handling.

VM also has a threaded view, but I do not turn it on by default and do not often invoke it. I do, however, use a keyboard macro that enhances the built-in vm-kill-thread-subtree.

Does MH, or the various clients, support breaking digests? VM has that (sadly, not working with an increasing number of lists), and that is definitely useful.

If you enjoy using MH, maybe the more modern https://github.com/leahneukirchen/mblaze would be interesting to you as well.

It uses Maildir and handles mime quite well from what I can tell.

By cks at 2023-10-10 09:36:59:

In theory (N)MH has burst to burst apart digests into individual messages, but I've never used it so I don't know how well it works in practice (especially today, where people may be inventing their own digest formats left and right).

Written on 08 October 2023.
« The three modern formats for email forwarded by people
My understanding of various sorts of completion in GNU Emacs »

Page tools: View Source, View Normal.
Search:
Login: Password:

Last modified: Sun Oct 8 23:28:08 2023
This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.