Viktor Rosenfeld <listuse...@gmail.com> writes: > The docstring of `org-icalendar-with-timestamps' already states: > > This variable has precedence over `org-export-with-timestamps'. > It can also be set with the #+OPTIONS line, e.g. "<:t".
This wouldn't be sufficient: "has precedence over" isn't a synonym for "change the meaning of". > I believe that inconsistency is desirable here. Consider the following > use case with three headlines: > > * TODO An appointment in the future > <2013-08-12 So 09:00> > * DONE A note about an appointment in the past > [2013-08-10 Fr 09:00] > * WAIT A reminder how long I've been waiting for something [2013-08-10 Fr] > > The previous behavior, with `org-icalendar-with-timestamps' set to > 'active, was that the first and the last headlines were picked up (even > though the timestamp in the last headline is inactive). This was > unexpected because the two inactive timestamps are handled > differently. This is to be expected according to `org-export-with-timestamps'. > My expectation was that only the first headline should have been > exported. This is what my patch achieves. The meaning of `org-export-with-timestamps' is the result of a discussion in this ML. Please read the whole thread starting at: http://permalink.gmane.org/gmane.emacs.orgmode/69971 Regards, -- Nicolas Goaziou
