Even more note organizing strategies

Some things I've realized I can do that might making de-Obsidifying even more appealing.

Automatic dates-as-filenames

All of my notes/links currently use a timestamp as the filename so I don't have to know what I'm going to call something in advance. The "generate unique note name" feature (plugin?) is how I've created pretty much all my files. It's not a particularly ocmplicated operation, I wasn't sure the best way to replicate that across environments.

Turns out, there is a pretty simple wat to replicate the fielname creation in pretty much any shell:

echo "$(date '%Y%m%D%H%M%S').md"

so, anywhere I've got a shell, making the files is actually pretty easy. That's how I made this file (with Helix)!

"Private" files

I have a bunch of things I'm either not ready to publish yet, or might not want to publish period. I've toyed around with the thought of handling notes as branches, but branches can't be private, so that doesn't solve that problem.

But you know what can be private? A whole remote! It might be a bit ugly, but I could have an entirely separate git remote to store WIP stuff, and then get it merged whenever I feel like it without having it sit around locally.

Frontmatter

The other thing I was using Obsidian plugins for was automatic frontmatter. Shell commands come to the rescue there, too, because (as long as I get better at using a solid text editor) I can pipe in commands.

For example, here's how to add a current timestamp for the creation date thing.

!date -Isecond

Unrelated, Helix stuff

Learning about it! Some things I'm figuring out:

• Basically, trying to use incremental movements as little as possible. I guess I should read the tutorial, but one strategy I've liked using so far is select everything (%), then use s to search (regex matches, within the selection), then edit from there. To fix a typo, once I have my match , within the selectionselected I can use c to "change" it, or go to the end of the line or whatever.
• ; collapses a selection to a single cursor, which is handy if you're using selections to jump around I guess (keeps it from being all messy if you're looking to just move then edit)
• The "word" go-to maneuver (g then w) is fantastic. No need to come up with clever regex to move around (if you don't want to), you can just jump exactly where you want with a two-letter code. Honestly it should be at the start of the tutorial (not that I made it very far into the tutorial).
• Another handy movement/selection trick is jumping to next/prev characters via f (forwards) or F (backwards). It's nice for moving around the structure that crops up in unstructured stuff, like sentences or clauses.