💾 Archived View for thatit.be › 2024-11-22-06-41-56.gmi captured on 2024-12-17 at 10:03:56. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
I now add a created stamp to each page, and I’ve modified the last updated logic to not write the last updated if it’s the same as the created date. In doing so I noticed that even though it’s been only two years or so, my Python coding style has changed a bit. I hope for the better. I’ve also noticed that it’s kind of nice to use the Gemtext pages as the browsing format for my notes stored locally.
Obviously Gemtext looks nice as a format for viewing text, but this is something more. There’s minimal transformation to go from the Markdown I write in to the page that gets displayed, but it still feels a bit more pleasant than reading the Markdown. I think this tiny bit of transformation is created a few unexpected effects in my brain space.
Here are the transformations:
The headings make even atomic notes more colorful. The subsections for tags and navigation create framing around the body. Not to mention it adds navigation options. My notes are obviously navigable from the links within them, but I don’t have any handy macros or anything for navigating to the tags from within my editor of choice, except from these generated pages. Well, that’s not true, I can pop up Telescope and use the live_grep option and provide an expression like ^tags:.*TAG but by the time I’m there and typing an expression cognitive load goes up and there’s a good chance my focus will be broken.
Stripping extra markdown for formatting removes some of the colorfulness from inside paragraphs, but this might actually be desirable. I wonder if I could set it up so that syntax highlighting is only in effect when I’m in insert mode. Maybe as a zen mode option? But I would only want certain syntax elements turned off. I might modify my .exrc to generate the thing saved (again – I used to do this but didn’t see the point) and keep my gem files updated as I write my markdown. Then I could even get fancy and browse the gem files but automatically switch to the markdown documents when I want to edit a note I’m reading.
Before I made this note public I updated my Python code to finally accept command line arguments and added some more features, like checking document links to make sure they resolve. I found I had some links to private notes (which would create the equivalent of a 404 for anyone browswing,) from existing public notes. I made the previously private notes public. They’re somewhat random.
I don’t think anyone would care to see it, but I know that I get annoyed when I read dev logs about code I can’t fetch and run, so I’ll be cleaning up the logic I use for my notes and putting it into a separate repository for easier re-use by others. But this will be a while. I should stick that on the todo list…
created: 2024-11-22
updated: 2024-11-23 12:19:48
(re)generated: 2024-12-17