Good tab expansion in a very virtual filesystem would work wonders:

    $ cat /cal/nexttues<TAB>
    $ cat /cal/2024/08/13/

    $ cat /cal/nextweek<TAB>
    $ cat /cal/2024/w32/

I seem to recall that I had lunch with somebody last July:

    $ grep -ir somebody /cal/2023/07/
    /cal/2023/07/12/events:13:00-14:00 Lunch with somebody

Not this exactly, but I used to keep a calendar as a text file, where each day was a single line containing the date, week day and possibly some events.

Something like:

    4h sun: 1500 dentist's appointment, 1800 dinner with friends

Where a=jan, b=feb, c=marc, ... l=dec.

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.

If I gzip my meetings, will they get shorter? If so, I'm on board.

I think you mean

  $ ls /cal/2024/08/04

Or perhaps

  $ cat /cal/2024/08/04/*

;)

I was thinking about this and came to the conclusion that I'd want to define some events per date, like you illustrated (`"12:30 dentist" > /cal/2024/08/04`), but others I'd like to define per event, like `2024-08-23 12:30 > /cal/massage`, which seemed messy. I didn't really resolve this question for myself.

This would be fantastic and very in line with Unix philosophy.

So the question begs: how hard would this be to write.

Because I want it!

Will all users on the system have to share the same calendar?