Hi Richard, > Hi Detlef, > > Detlef Steuer <ste...@hsu-hh.de> writes: > > > My question: Is it possible to export to ics without an end time? > > > > If not, how can a different default lengths for icalendar export > > only be defined? > > > > I guess the two hour setting is kind of arbitrary. Couldn't that be > > a variable, if the icalendar standard requires an end time? > > I don't know much about the Org-specific parts of this, but I can tell > you that the iCalendar standard does not require it.
thank you already for that clarification. > > However, I suspect that the reason the 2 hour default is there in the > code you pointed to is that external calendar applications might not > display events correctly that have a start time but no end time or > duration. (Think of the typical web-based calendar, where an event is > a box with a height corresponding to its duration: an event with no > end time and no duration might not be visible/readable.) > > Can you describe your use case more completely? Do you need to be able > to export without an end time? Why don't you want to set > org-agenda-default-appointment-duration? (Presumably you could do this > dynamically for iCalendar export, without affecting org-agenda, if > that would solve your problem.) > 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. The conversion happens beginning from some excel sheet, where there are no end times, into R into org into ics :-) 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. (And/or explain the fact there is a default in the docs.) I know, patches welcome, most probably :-) Anyway I just happened to stumble upon this and wanted to understand what happens. Thx for your answer Detlef > Best, > Richard
