As you know, I’m fond of the notion of living in Emacs to the greatest extent possible. For me, that’s an ongoing process much like a Japanese garden: a process that is always seeking perfection but that is never complete. Others, like Lee Hinman, have made better progress.
Hinman calls his Emacs configuration EOS, The Emacs Operating System. It’s a thing of beauty. He has modules for nearly every component of his workflow—even most of his Web browsing. Those modules are written in Org mode with lots of explanatory text to help you understand what’s going on.
The module setup is nice because it allows you to choose the parts that support your workflow while ignoring the rest. If you’re not a Twitter user, for example, you can just ignore that module. Most people probably won’t want to use EOS out of the box but its module structure and internal documentation make it easy to adapt. If you have a minimal configuration, a good strategy would be to clone EOS, make the changes that are sensible for your workflow, and then install it. If you already have an extensive configuration, Hinman’s configuration will serve as a model for rationalizing your configuration’s structure and as a source of ideas for additions to your configuration.
Even if you aren’t interested in moving your life into Emacs, Hinman’s configuration is worth looking at for the many ideas you can mine from it. It’s an excellent resource.
UPDATE : Forgot to mention that I found the EOS link from this tweet by Arne Babenhauserheide
And a nice #Emacs setup: https://t.co/tmWHwR1NL8
— (ArneBab)) (@ArneBab) October 19, 2016