I'd love to preserve my compositions list in a manageable text file which should act as a #SSOT.
Current status: nightmare. A mixup of #orgmode (cool), #yaml (oh no), and spreadsheets (fck!).
Yesterday I stumbled upon #recfiles and #recutils
https://www.gnu.org/software/recutils/
I think this could work. Please convince me not.
I just learned about #recfiles. A database for plain text lovers like me.
https://youtu.be/A1whwi-Gc0Y
(or https://vid.priv.au/watch?v=A1whwi-Gc0Y if you don't like yt)
@Are0h Do you mean something like #Recfiles or more like dumping records in individual files in some directory?
I'd say the latter is less subject to catastrophic screw-ups when editing manually.
As for largely unstructured flat files, there was a thread that I think explains well-enough why I think they're a horrible idea: https://social.treehouse.systems/@psykose/109967460650885493
sudoers file: # 1000 ALL=(ALL) NOPASSWD: ALL ^ a comment #1000 ALL=(ALL) NOPASSWD: ALL ^ allows uid 1000 to do anything nice format!
#Recfiles (https://www.gnu.org/software/recutils/) are an interesting option for human-readable data formats that remain machine-usable.
Similarly for simply 'write-ing alists or readable structure definitions to files.
Logseq looks pretty good for personal wiki/knowledge management/notes-taking stuff. I like a lot of things about it.
But I’m resisting the usual urge to go all-in once I find something good, to transfer everything from my previous systems to this asap.
Going slow will let me find out what the weak spots of this particular ecosystem are, before I invest too much into it. Then, I can figure what use-cases are best fit for it, and what should remain in other systems.
choan 🍉
Jon Arvid
LisPi
Sundar