gnus

Introduction

In my last email-related post, I discussed Disciplined Email via Gnus. I theorized that reading email like a newsgroup would enforce more disciplined, efficient email use. I stand by that philosophy, but changed my email client to Notmuch.

Why Switch from Gnus to Notmuch

Reasons for switching from Gnus to Notmuch include:

Local copy of email: I had been doing email over IMAP, both work and personal. I was interested in getting a local copy of my email for backup and availability purposes. For this, I use OfflineImap, which synchronizes IMAP email with a local maildir. This integrates nicely with Notmuch, while I found Gnus maildir support slow and clunky.
Fast search: Search lives at the core of Notmuch. As a response to the Sup email client (get it?), Notmuch provides indexing, and searching, while search seems peripheral to Gnus.
Unified email: I like the unified inbox I get with K9 mail on my Android phone. I find separation between email accounts unnatural. Notmuch provides a single “inbox” tag for new messages, regardless of the account; I did not figure out how to do this easily in Gnus.

Nits About this Setup

A couple smaller things bug me about my current setup, though possibly not enough for me to spend time fixing:

OfflineImap occasionally goes to lunch: I think this happens when OfflineImap is running when I put my laptop to sleep. When it wakes up again OfflineImap eats a CPU, so I go kill it. I run OfflineImap via cron, so I don’t need to restart anything.
Email forwards sent from default account: When responding to email via the Notmuch emacs mail client (which uses Message Mode) does the right thing–if you have multiple email accounts, it sends the response from the account that received the email. However, email forwards send from the default account, even if a different account received the original email.

Conclusion

I find email with Notmuch + OfflineImap superior to Gnus + IMAP.

I’m a believer in the Inbox Zero philosophy; that is, I don’t like my brain to be in my inbox. If I have more than about 5 read emails sitting around, I get uncomfortable. I recently noticed myself getting sloppy with email, so I watched the Merlin Mann’s original Inbox Zero video for a refresher. The part of the video where Mann describes typical email processing as a deli chef who reads the orders multiple times, organizes them in different ways, but never actually makes a sandwich. Email is a support tool to help us actually do things. It is a means to an end, not an end in itself.

So, I took a look at the tools and processes I use for email. Since email is text, IMHO it belongs in emacs. I have been using emacs mew for a while now, since I like how it allows you to keep using emacs when it’s doing IMAP operations. I also use k9mail on my Android phone to check email hourly. My plan was to process email in mew daily, and keep in touch with the rest on my phone.

My analysis is I got sloppy in three aspects:

I read too much email on my phone. I was e.g. catching up on mailing lists on my phone, when really that should be done at my daily mew session.
In my daily mew check, I would leave mail for processing later.

To combat this, I started using Gnus instead of mew. The key feature of Gnus is that it reads email like a newsgroup reader–that is, once an email is marked is “read,” by default it no longer shows up in your inbox. This provides a constant reminder that email should be read once and processed, not left in the inbox to reread and process later.

As a side benefit, I find Gnus to display email beautifully. HTML emails show inline images properly. It displays messages properly threaded. I love the overall look-and-feel.

This is my current plan for disciplined email. In a month or two of using Gnus, I’ll check in to see how my email processing is going.

Email Update: Notmuch

Introduction

Why Switch from Gnus to Notmuch

Nits About this Setup

Conclusion

Disciplined Email via Emacs Gnus