Post B55P1LFUxPnyF2Drea by mirabilos@toot.mirbsd.org
 (DIR) More posts by mirabilos@toot.mirbsd.org
 (DIR) Post #B55P1L3neuRnekkWQ4 by rqm@exquisite.social
       0 likes, 0 repeats
       
       I have to say I don't know why, until some recent discussions on the #OpenBSD mailing lists, I have not heard of the built-in calendar(1) program, but I am totally sold on its simplicity. Really easy recurring and moving events and date calculations based on Easter etc.  It is parsed by cpp(1) and so you can # include other calendar files in your personal one.I really really like this and will consider moving to this format -- 2-way sync with this via vdirsyncer or similar would be awesome to see.
       
 (DIR) Post #B55P1LFUxPnyF2Drea by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @rqm I switched to it years ago and display today’s+tomorrow’s events in every shell (from ~/.mkshrc) as that’s the only way I don’t miss appointments left and right.If you use the #MirBSD implementation, which has an extra "parse for export" flag with support for time-of-day, you can have one-way conversion to #iCalendar, which you can then read-only subscribe to from e.g. smartphones, or Bloatzilla Thunderbird.Two-way is unwise, they hve vastly different "mightyness", e.g. recurrence is handled differently, and #BSD #calendar can do offsets from Easter and so (and MirBSD’s also from Advent), and #if and #include and cpp comments, etc. (which I use heavily in my private calendar, I even have a script to pre-fill with comment headings for the next year per calendar week).https://evolvis.org/~tg/calendars/ has my public calendars in both formats (and links for subscribing to them through Google, for those who use that). The conversion cronjob runs nightly, as it uses "today" as startpoint for recurring events.