Aw, that's not what I hoped it would be. An actual file-based calendar UI is a neat idea, where you can (for instance) echo into a file to create a calendar event on the command line.
It would be cool to see a filesystem layer present a tree of ICS files where editing one also updated your various API-based web calendars.
I don't have more than 10 entries per week. Partly because I prefer real work over meetings, so I work at a place that does not have a lot of meetings. And once you don't have many, it's easier to remember other appointments, no need to use a calendar for everything. So even if this had been a useful mapping of calendar entries into a directory tree, I would not have felt an urge to use it.
Could one use the txtai python libe to be told to train on the temporal relationships between events that pass through it as an fastAPI endpoint to a calender... then as the events head to whatever is holding them in the calendar - txtai is training and indexing, first on temporal notes, then on context. so you ould easly as it to give you a
"Show all the social events that happen on wednesdays with a dress code"
(but it learns the nature of certain events, when they occur and social clues around what /who /wheres are typically occuring...
"This venue typically holds events on W F S and the clientelle is typicalaly this, attendance that, rsvps x, cost ~$$"
$ cat /cal/2024/08/04/events
$ cat /cal/nexttues<TAB>
$ cat /cal/2024/08/13/
$ cat /cal/nextweek<TAB>
$ cat /cal/2024/w32/
$ grep -ir somebody /cal/2023/07/
/cal/2023/07/12/events:13:00-14:00 Lunch with somebodyA couple of weeks ago I was surprised and annoyed that adding an event with description "10:30-11:00 Pointless Meeting" no longer scheduled my Pointless Meeting. Tried again very carefully. Wasn't working. Worked again the next day. Did anyone else experience this?
I can't wait for them to feed my description to an LLM to generate the event. "Schedule drinks at 7 at the bar behind the office next Tuesday. Invite my favourite colleagues and their teammates. Make them curious but not suspicious."
Something like:
4h sun: 1500 dentist's appointment, 1800 dinner with friends
The initial file was autogenerated with a 10-line Python script.
You can have variations on this, like allowing multiple rows per day, one row per event.
I also used to keep an unstructured "journal.txt" file, where notes were separated by two blank lines, and you could reference topics (like #toRead) and dates (like #4h24) with #, like social media hashtags.
$ ls /cal/2024/08/04
$ cat /cal/2024/08/04/*
Because I want it!
I reckon, yeah.
From this article[1] writing a FUSE filesystem doesn't look that hard.
I might give it a go this weekend. Assuming I remember!
[1] https://blog.trieoflogs.com/2021-05-25-fuse-filesystem-go/
Explain how it is better vs having a simple cli that parse args and store that into SQLite.
access - for discovery and poking around you won't need a dedicated tool, just `cat` or `less` or `vim`