Friday night watching the Phillies, drinking 🍷 and setting up #mu4e in #emacs pushed over the edge by @pymander and @jameshowell
Actually surprised I've never gone down this rabbit hole despite using emacs for decades.
@randyridenour @jameshowell @greg @pymander No kidding! It took me forever to get the #O365 auth flow worked out, but #pizauth worked wonders with #mu4e.
Granted, I don't use email with or via #emacs, as I don't yet quite trust I won't wind up deleting everything on the server side. Plus, I have not yet sorted out the whole "everybody in the organization uses outlook calendar".
@panmaster @me I use #imapfilter for presorting, #mbsync to sync with imap servers, custom python scripts for cleanup, and tie it all together with #notmuch. Actual reading of emails in #mu4e that calls notmuch and indexes using #mu.
Does that make me a weirdo? Probably. That and wearing toe socks.
NERD DAD FRIDAY NIGHT WITH @greg
If I'm honest, there's a bit of faffing around to get #mu4e configured (see footnote¹). But golly, it sure is worth it.
Just being able to compose emails natively in #Emacs is very OHHHHHHhhhhh **THAT** FEELS BETTER
and then being able to capture Org tasks that link to messages is very UNLIMITED POWER!!!! (see figure)
and then over the next couple years gradually smoothing and polishing your email workflow with little customizations just exactly for little old you is very [wildebeest-levitating-in-blissful-meditation]
If I were to presume to provide advice it would be: consider it a gradual transition, and resolve to savor the process and enjoy each incremental improvement.
___
¹There's a separate binary, which requires a separate quirky compile-from-source installation and configuration. Like most Emacs mail clients, it relies on mbsync to sync local copies with your IMAP server. And then there are countless quirks in its UI, endlessly customizable in the good/bad way to which we are all accustomed.
Friday night watching the Phillies, drinking 🍷 and setting up #mu4e in #emacs pushed over the edge by @pymander and @jameshowell
Actually surprised I've never gone down this rabbit hole despite using emacs for decades.
RE: https://fosstodon.org/@pymander/116381801119625280
Amen, brother! In #mu4e under #Emacs "The ability to write custom code to both process and create email is extremely powerful and a great time saver."
UPDATED BLOG POST: Finally tracked down and fixed a little bug in "Custom sorting of mu4e headers"
https://jamesendreshowell.com/2026-01-08-custom-sorting-of-mu4e-headers.html
(setopt shr-use-colors nil)
THIS SETTING COMPLETELY FIXES what has been by far my biggest annoyance with mu4e. Namely the ghastly clash of awful foreground and background colors in messages that can only be rendered as HTML.
Thanks to Wouter Groeneveld for this tip and many other improvements to mu4e!
https://brainbaking.com/post/2026/01/customizing-the-emacs-email-experience-with-mu4e/
@marlinz's "Constantly fighting for structure" includes "constantly fighting against friction, because the slightest friction can become paralyzing, especially additively."
Conversely, removing distractions becomes a long-term exercise in continuous subtraction. Removing UI elements until only the essential is visible. Removing steps in workflows. Paradoxically, ADDING steps (single keystrokes) to workflows in order to reveal options in steps rather than presenting all the choices. Each reduction is tiny, but the cumulative effect—over years—is a huge reduction in stress and a huge increase in productivity throughout the day.
Much more of the day in focus. Much more of the day in flow.
For someone else's brain, context switching between a bunch of desktop apps might feel like the same cognitive burden as switching between #Emacs buffers. But for me, #OrgMode, #mu4e, and #magit have not just changed how I work.
They allow me to control how I work, with results that have been a binary, qualitative improvement.