Thinking more about the "auto eval definitions" approach, I think it breaks down when debugging. If I want to step through the existing definition, it'd be really awkward to re-evaluate the definition at my cursor.
miniblog.
Related Posts
There are docs resources like https://diataxis.fr/ that categorise documents based on format and intended audience.
They don't say where you should start, or what order you should write docs.
I'm currently thinking README > reference > tutorial > how-tos. Agree/disagree?
On thinking of books like software, treating them as evolving artifacts, and URLs versus paper book publishers:
I've been thinking about making difftastic smarter about context. In principle it understands structure, so I could limit context to the enclosing definition.
However, sometimes it's nice to see surrounding code. Line 644 isn't useful, but maybe 655 is. Opinions?
