Incredibly inefficient, to check the file system for every single word. So it's in a fork for now while I decide just what to do with this new super power.
It's interesting to compare this approach with Gemini.
Gemini: links on their own line, support arbitrary link text.
Me: inline links are ok, but the text will always be the URL.
As preparation for tomorrow's wheel reinvention jam, I just created a fork of lines.love with all the drawing support ripped out. Time to take it in a new direction.
No overlapping, no tiling, just an infinite 2D surface of columns. Commands open new columns.
Wordstar-style menu up top of important commands in current context, and their shortcuts.
Command palette at top left that filters commands available in current context.
Files/nodes can have links. Links can form graphs, as the picture shows (original: http://www.maplefish.com/todd/papers/Experiences.html)
Links have labels (next/previous by default).
Graph-traversal commands can take an argument (next/previous by default) of the edge label you want to follow.
'add' adds an edge immediately to the current node, 'append' traverses the edge repeatedly to the end, then adds.
'step' navigates along an edge from the current node and opens it in a new column, 'unroll' traverses the edge repeatedly to the end and collects all nodes into a single column.
I'm doing a major migration of my notes schema to make it work better with my note-taking app. In the process I've been reading a random (mostly embarrassing) sampling of 10+ years of notes. But here's a non-embarrassing one:
Jun 2012: I need fuck you software.
That pretty much explains why I started Mu 2 years later :D
To be precise, I've been migrating my existing 10+ year old note-taking workflows out of terminal and unix tools into a more integrated and hopefully more accessible environment.
