| I've been using a variation of this for at least four years now (the first line from the first git commit starts with 2018-07-29, but I'd been already using it for a while). I use a simpler syntax, such as "2022-06-01 Event description" or "2022-06-01 12-13 meeting" because I don't really care about week numbers and week days are handled separately (see screenshot). Through the years I've added more features as it became more interwoven with the rest of my (plain-text) productivity system. For example, I have reminders: 2022-06-01 2100! take out the trash. This notifies me at 21 on whatever device I'm using at the moment (computer or smartphone notification) I have a vim syntax and ftplugin files that help in visualizing important things (eg. the date and time are highlighted; inactive events (starting later) are shaded a bit) with support for easy and ergonomic moving of things (keyboard shortcuts to postpone tasks by one day, one week, etc) and also handling of recurring events (every X days/weeks/months/etc). Relevant data is integrated into dashboards (e.g. the number of remaining events/tasks for the day is shown in my desktop statusbar); each morning (or the evening before) I can get an email with the tasks for tomorrow, etc. The only thing I'm missing, since lately I have begun attending several meetings and have started timeboxing my work time as well, is the ability to see those nice boxes one sees e.g. in google calendar in day or week view. However I think that this plaintext file could be parsed and a view like that could be generated with relatively little effort. example screenshot: https://0x0.st/oBIr.png edited to add. I just noticed that OP's solution is one day per line. Mine is one event per line, which I find much more readable and versatile. You can change the date or time of an event and then simply `sort` the file and it's automagically in order |
Your syntax highlight sounds like a nice addition.