6 ms·

I'm actually a little curious as to what sort of workflow others are using for their calendars. Personally, I use a terminal/text based program named khal: ht

by kxyvr 10y ago

I'm actually a little curious as to what sort of workflow others are using for their calendars. Personally, I use a terminal/text based program named khal: https://lostpackets.de/khal/ https://lostpackets.de/khal/ to view and edit calendar events and vdirsyncer: https://vdirsyncer.pimutils.org/en/stable/ https://vdirsyncer.pimutils.org/en/stable/ to sync this with my email provider, which supports CalDAV and CardDAV. I'm asking about others workflow because this simple setup allows easy access to calendars across multiple devices. Although I don't often do it because I don't have a need, vdirsyncer just dumps the CalDAV events into a folder in text format, so it's pretty easy just to write a shell script to modify, automate, or maintain calendar events. I also like it because it allows me to backup my calendars for record keeping sake. Now, I don't claim that this setup is for everyone, but are there useful, interesting tricks that this workflow doesn't allow?

MarcScott 10y ago
I use org mode for my calendar, which is great as it seamlessly integrates my ToDo with my Appointments. At work we use Google Calendar extensively, which means other people often make appointments for me. To pull in and push items from my schedule.org, I use org-gcal - https://github.com/myuhe/org-gcal.el https://github.com/myuhe/org-gcal.el
- kfrzcode 10y ago
  This is great, I was looking for something similar when I was in org-gcal mode last year. I'll have to revisit this link
  - kxyvr 10y ago
    That does indeed look neat. At the same time, there are extensions to CalDAV that codify how to add scheduling to the standard. Namely, RFC 6638: https://tools.ietf.org/html/rfc6638 https://tools.ietf.org/html/rfc6638 Certainly, it's something that I wish khal had. This is why I think I'm missing something. Certainly, dealing with CalDAV is a pain because many programs don't produce standards compliant files. That said, it really just looks like a CalDAV server has a folder with a bunch of text files that contain the calendar information. If I want someone to have view only access to that folder, they have read access. If I want someone to have the ability to add calendar events to my schedule, they have read/write access. The file uploads look like they use WebDAV. Syncing across devices just means syncing to the folder on the server. Exotic calendar tricks can be handled either from a server side script or a client side script followed by a sync. Now, I wish that were easier and I think there's room for improvement especially in developing a language to make it easier to write these scripts. However, is there really something fundamental that this framework doesn't have that these other calendar programs provide?
aembleton 10y ago
All my actual calendar data is stored across many calendars: 2 Google calendars, Facebook, Meetup, Victorops and Workplace. I interface with all of them through aCalendar Android app. https://play.google.com/store/apps/details?id=org.withouthat.acalendar&referrer=utm_source%3DTapirApps%26utm_campaign%3Dhomepage https://play.google.com/store/apps/details?id=org.withouthat...

by kxyvr 10y ago

MarcScott 10y ago

I use org mode for my calendar, which is great as it seamlessly integrates my ToDo with my Appointments. At work we use Google Calendar extensively, which means other people often make appointments for me. To pull in and push items from my schedule.org, I use org-gcal - https://github.com/myuhe/org-gcal.el https://github.com/myuhe/org-gcal.el

kfrzcode 10y ago
This is great, I was looking for something similar when I was in org-gcal mode last year. I'll have to revisit this link
- kxyvr 10y ago
  That does indeed look neat. At the same time, there are extensions to CalDAV that codify how to add scheduling to the standard. Namely, RFC 6638: https://tools.ietf.org/html/rfc6638 https://tools.ietf.org/html/rfc6638 Certainly, it's something that I wish khal had. This is why I think I'm missing something. Certainly, dealing with CalDAV is a pain because many programs don't produce standards compliant files. That said, it really just looks like a CalDAV server has a folder with a bunch of text files that contain the calendar information. If I want someone to have view only access to that folder, they have read access. If I want someone to have the ability to add calendar events to my schedule, they have read/write access. The file uploads look like they use WebDAV. Syncing across devices just means syncing to the folder on the server. Exotic calendar tricks can be handled either from a server side script or a client side script followed by a sync. Now, I wish that were easier and I think there's room for improvement especially in developing a language to make it easier to write these scripts. However, is there really something fundamental that this framework doesn't have that these other calendar programs provide?

aembleton 10y ago

All my actual calendar data is stored across many calendars: 2 Google calendars, Facebook, Meetup, Victorops and Workplace. I interface with all of them through aCalendar Android app. https://play.google.com/store/apps/details?id=org.withouthat.acalendar&referrer=utm_source%3DTapirApps%26utm_campaign%3Dhomepage https://play.google.com/store/apps/details?id=org.withouthat...