Turns out that patching Emacs' library loading whilst silencing user feedback can lead to some really interesting bugs: https://github.com/cask/shut-up/pull/12/commits/2495e8bf3d424f88f82679dd94def6b87960c4a9
This might be the longest commit message I've ever written. I think a good message tries to persuade the maintainer to accept the PR.
miniblog.
Related Posts
Claude asked me a question today: was I looking for an Emacs plugin (because I was talking about elisp) or a Rust program (because I have configured Rust preferences)?
I'm really impressed, it's rare to see LLMs ask follow-up questions.
(I wanted Emacs in this case.)
Today I learnt that Racket *intentionally* doesn't have a traditional REPL workflow. The authors were concerned about students not understanding the state between the current session and the code on disk.
(Arguably Jupyter has some of these features now.)
I've started keeping a list of particularly interesting bugs and patches that I've worked on: https://github.com/Wilfred/interesting-code
The time that I once removed *a single closing paren* in Emacs is still my favourite.