I've modified my Python script for note processing to produce a directory of symbolic links for tags and titles. That is, when I run the Python script, it will generate directories for tags (located at T383838meta/tags/<tag>) and for each tag on a given file it will make a symbolic link using the note title as the file name.

That still sounds confusing. Here's an example:

T282828

Tc9d1d9---

Here's a cool note.

Let's pretend the above note has a filename of T383838notes/2025-01-20-21-57-38.mu. After saving, my processing script would create the following files:

meta/tags/demo/sample note.mu

meta/tags/meta/sample note.mu

meta/titles/sample note.mu

And those files would be sym links back to T383838notes/2025-01-20-21-57-38.mu, except they'd have nice human readable names. This makes it super easy to T383838fzf, T383838Telescope live_grep, or use a T383838neo-tree browser to browse notes and still have an idea of what note I'm looking at based on the file name, regardless of other context.

There is a drawback to this approach: I automatically commit T383838.mu files to git on save. Now I have a bunch of sym links that aren't in the git repository. Turns out, there's an add-on for that, which I put in my plugins and everything is awesome now.

T282828

Tb4b4b4{ Ta5d6ff"Ta5d6ffaymericbeaumet/vim-symlinkTa5d6ff"Tb4b4b4, Te6edf3depends Tff7b72= Tb4b4b4{ Ta5d6ff"Ta5d6ffmoll/vim-bbyeTa5d6ff" Tb4b4b4} Tb4b4b4},

Any buffer created to deal with a sym link will instead load the target of the symbolic link. So if I open any of the new symbolic links, I can save them and it commits the target file as it should.

Tags: nvim, meta

created: 2025-01-20

(re)generated: 2026-07-17