txt-agenda VS org-caldav

I'm not really one for shilling my (decidedly unprofessional) coded projects, but submit that I have put together a shell script[1] that builds an agenda using date stamps from passed text files. The script is POSIX compliant if you pass a flag, but otherwise uses Fzf to filter and jump to entries. It's basically like a less extensible, but much shorter (in terms of lines of code) version of Org Agenda. I'm currently extending it to export an ICS file, which will allow automatic import into calendar services from Google, Fastmail, Apple, or whatever. Two-way calendar sync is beyond my will for faff, but if the spirit so moves someone I wouldn't stand in the way.

[1]: https://github.com/shushcat/txt-agenda

For CalDAV there is org-caldav or khalel. For CardDAV there is khalel. In my experience, though, using these packages is kind of involved and not very satisfying.

- Org-Caldav

PS: I've asked a similar question before and I know of org-caldav, which still requires a CalDAV proxy and org-gcal, which only works for Google.

Yeah, thanks for mentioning this - that was indeed my plan. I’m using org-caldav successfully on one machine, but I’m finding it hard to run across multiple machines. https://github.com/dengste/org-caldav/issues/270

org-caldav for calendar sync

I have a few files that are specifically reserved just for calendar/todo syncs. Then I set them up with org-caldav.

Random example of someone dealing with it... :

I use org-caldav with emacs-calfw.

I have Org-Caldav partially working with davmail and Office365. (Yes my employer hates me and I have to use Outlook!) In Thunderbird items I create on the phone appear in Org-Mode. But for Org-Caldav items I create on the phone do not appear. Items created in Emacs Org-Capture in the todo.org file do appear in Outlook (and Thunderbird).