A sign of ag.el's success is that users are learning its commands before occur.el!
miniblog.
Related Posts
... and my third refactoring with Cursor changed some function calls that I didn't want it to modify. Subtle.
I've had the most success with AI coding tools when I know exactly what I want the output to look like.
Perhaps the biggest driver of docs success is prestige. How cool are the docs tools, and how proud are you to have contributed to the docs?
Which tools do this best? Racket docs look pretty great, for example.
I've realised that the Haskell 'slogan' "avoid success at all costs" is ambiguous.
It can be parsed as "avoid success, at all costs" or "avoid success-at-all-costs". I'm not always sure which meaning is intended.
