Emacs is still becoming *more* customisable over time! For example, in 2016, the backtrace function became a user-level function. https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=27cada035a79b633e856a437dd0e037acc1d61c6
This allows users to introspect, debug or write their own!
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.