Ask HN: Resources to grok Emacs and use it well?
I am keen to crowdsource a study of emacs workflow practices, where we can collect, compare and analyse different development practices among emacs users. This should help other emacs users to borrow modes&#x2F;keybindings&#x2F;specific techniques&#x2F;tricks.<p><i></i>* Motivation<p>This is inspired by an ongoing conversation about emacs with a friend and a debugging interview that I really enjoyed.<p><i></i>* Exchanging emacs tips with a friend<p>A friend of mine is pretty proficient in emacs: org-mode all the things, written &gt;500 LoC of elisp, tried several distributions. We still regularly teach each other about existing emacs functionality and exchange messages along the lines of:
- I just found that there is a function foo, which I have made a keybinding foo and can now search open a tab with a SO search with text from the clipboard
- whaaat? That&#x27;s super useful!
- I know, right?<p>He works with a couple of greybeards, who also seem to be constantly finding emacs functionality that makes their lives easier, which suggests it would be beneficial for all of us to watch others in emacs.<p><i></i>* Interview<p>I was given a real git repo that I needed to load into my environment (spacemacs on Linux) to debug and fix failing tests. They sat me down during the onsite (the days when we would go to interview in person), told me to download the repo from the URL, told me how to run the tests (after activating the python venv) and watched me debug and fix failing tests - only 5 were failing from about 100. The interviewers were not proficient in emacs, but I felt that they could follow my thought process and workflow. I had only recently set up python dap-mode and felt clunky navigating in pdb through dap, so ended up print debugging.<p>It made me think how interesting it would be to watch other people with different backgrounds and experiences debug the same problem and how often I would learn new tricks or debugging techniques. Having a good understanding of the problem and the code allows you to focus on the activity of programming and watch out for new ways of tackling the same problem.<p><i></i>* What will we investigate<p>Furthermore, it might be interesting to see what debugging practices are statistically more succesful in tracking down the bug faster (and control them for overall years of programming experience and emacs proficiency).<p>If our sample is big enough we can answer questions like:
Correlation between overall years of programming experience and debugging time? 
Who is faster at debugging: printf or gdb debugger people? 
Which keybindings and modes are most frequent across users? 
Is there a correlation between having custom elisp functions and debugging time?<p><i></i>* Format<p>I will prepare a representative repo in the most popular language (I am most comfortable in Python, happy to consider other languages, if people prefer), bury some bugs in it (that will be easy), administer the study and summarise the findings in a spreadsheet&#x2F;write-up.<p>Following the debugging session outlined above. Every participant:<p>starts recording their screen<p>Starts a fresh emacs instance with their config and loads a emacs lisp script that we provide for printing keypresses and recording keypresses + function calls to a log file.<p>download the prepared repo<p>run tests<p>investigate failing tests<p>fix them<p>commit their changes<p>The participant ends the screen recording session before sending me<p><pre><code>   - the video to me or youtube&#x2F;dailymotion URL 
   - plaintext keylog history
   - &lt;optional&gt; link to their elisp config
</code></pre>
I appreciate logging keypresses&#x2F;function calls might feel intrusive, so if you are uncomfortable doing that - don&#x27;t! At the same time, if we want to share good debugging practices and general emacs tricks - I see this as the most impactful way to share techniques and elisp snippets.<p>I watch it, sumarise the findings and present a write-up.<p>Who is interested?