Lukas Fleischer

Are you using a very old version of the calcurse-caldav script? This sounds like a bug that has been fixed back in late 2016; see issue #38 and commit e76b96c9...

calcurse does not yet support multiple calendars. As of now, the only workaround is to sync each individual calendar to a different data directory and browse them individually with calcurse.

Sure. The core problem is not the synchronization but moreso the fact that calcurse itself cannot handle multiple calendars yet.

Jordan Bancino investigated and found that this seems to be caused through a combination of OpenBSD's SSL library and the httplib2 version currently shipped with OpenBSD. Including Jordan's full email...

Thank you both for the constructive discussion. I agree that there are valid use cases for both floating-time appointments and fixed-time appointments. If we were to add functionality for the...

This should only happen if you modify the calendar both locally with calcurse and on the server, without syncing in between. The hooks could easily be changed to warn you...

You should use the post-save hook. You can also trigger a calcurse reload from there if that helps?

A few additions: * The merge tool can be configured with the `MERGETOOL` environment variable. * If we want to attempt an automated merge and only show a merge tool...

For non-interactive merges, we should probably also keep track of the diffbase (i.e. a snapshot of the data files at the time they were loaded in calcurse and before external...

Anything based on sorting and/or duplicate detection is not a good idea. @TripleTrable pointed out one potential problem. Another one is an item that is edited both remotely and locally...