And not really that human readable.

This plain text calendar would be more powerful if it came with an ICS parser.

    2021-03-03 w09 ke       8-1345 +lp bash-db; (14-1545 +mp); 1530 FxBar

Is that particularly readable? There's a whole section dedicated to how to read the entries and why the syntax is the way it is.

I'd post the last *.ics I had to parse, but it has personal info in it.

From the BEGIN:VCALENDAR line all the way down to the description being littered with \n line breaks, it is not very human readable.

I actually love plain text in general, and if this meets your needs, there’s no need to overcomplicate things.

The tradeoff is the greater feature set of ics comes with a necessarily more complicated format. We can see complexity creeping back in to this format as you scroll towards the bottom and tags are introduced, and there’s still a lot missing. With the way it is now, basic things we take for granted like recurring meetings are not handled. You’d need a separate program to insert/delete lines and do the date math if the format isn’t going to change, or more likely a special event type. If you add a recurring event, then you’d likely end up revisiting the one line per day idea.

or if I could just inject and print my own calendar events to and from the `cal` command and send that through an ical parser--item added via a plain text calendar, added to ical, and immediately updated event on my phone. It's been on my mind to just write something like this as a side project forever but...

I am remarkably lazy sometimes.

Well that's what I was thinking of, to put this plain text calendar on an e-ink screen with RPi. A google cal or ical integration out of the box.

I guess I can roll my own OAuth and parser, but then I'm not going to use this linked plain text calendar.