My Custom Emacs Setup
&gt; <i>At the end of the day I do spend time on my configuration, but it&#x27;s hardly the part-time job folks make it out to be.</i><p>If you never go deep (like me) then yes, it absolutely is a part-time job. Sometimes a full-time job, even.<p>The article is very interesting regardless and I&#x27;ve bookmarked it but the above smelled like elitism and I had to call it out.<p>I have no doubt that if you go deep on a tool that&#x27;s widely considered mystical -- Emacs and GIT are very typical examples -- then you&#x27;ll save time in the future. But I suppose those tools are never made with the other kinds of people in mind: those who want to learn the incantations with which their daily work is served and who don&#x27;t want to hack on their tool or never gain hardcore proficiency with it.<p>I stared evaluating VIM after 18 years with Emacs. I&#x27;ve seen less cryptic errors when I worked with C++&#x27;s STL 15 years ago. At some point enough is enough and I&#x27;m tired of being blamed that I haven&#x27;t lived inside Emacs&#x27; code -- when all I want is to be able to see syntax-colored panes, edit them, and have very light IDE features.