"Dr. Detlef Steuer" <ste...@hsu-hh.de> writes: > The use case is a calendar for a local bicycle group. The different > tours all have a start time, but usually only vague end times > (duration: 2-3 hours, or duration: day) > > Therefore it would not be enough to set a default duration time for all > tours.
I see, makes sense. > The conversion happens beginning from some excel sheet, where there are > no end times, into R into org into ics :-) Is Org a necessary part of the loop here? There's apparently an iCalendar package for R: https://www.rdocumentation.org/packages/calendar/versions/0.2.0 If you're already processing the data in R, maybe you could just output iCalendar format directly there? Then you'd presumably have less complexity and more control. > I understand why one would introduce a default length, as you explained > above. Nevertheless I would like to be able to configure any default if > needed. If you want to do this on the Elisp side, it depends on how you're calling `org-icalendar-export-to-ics'. Could you do any of these? 1) use a file-local variable in the Org file to set `org-agenda-default-appointment-duration' to the default value just in that file 2) write a wrapper function for `org-icalendar-export-to-ics' which let-binds `org-agenda-default-appointment-duration' during the export 3) add advice to `org-icalendar-export-to-ics' which let-binds `org-agenda-default-appointment-duration' during the export > (And/or explain the fact there is a default in the docs.) I > know, patches welcome, most probably :-) Probably! But I won't speak for Ihor... ;) HTH! Richard
