Hello,
David Engster d...@randomsample.de writes:
I have the problem that a certain kind Org entries is not exported by
the icalendar exporter, namely those created by the gnus-icalendar
package.
This package creates Org entries from calendar invites in the following
way (I've omitted some
Nicolas Goaziou writes:
David Engster d...@randomsample.de writes:
These entries show up in the agenda just fine, but the icalendar
exporter does not export it because the timestamp is in the properties
(the gnus-icalendar package puts it there so that you can easily change
it if the
David Engster d...@randomsample.de writes:
Yes, I could do that for my specific setup. But it would be nice if this
stuff could just work, so that things like Outlook calendar invites
can be directly exported to .ics.
AFAIU, we're talking about a third-party package which implements its
own
Nicolas Goaziou writes:
David Engster d...@randomsample.de writes:
I mean, those entries show up in the agenda, so I found it rather
surprising that they are completely ignored by the exporter.
This is an agenda bug, which probably use a regexp to find timestamps.
But timestamps in
David Engster d...@randomsample.de writes:
It's these multitude of timestamp locations which makes changing the
timestamp of an existing entry through Elisp so tedious (I had to deal
with that in org-caldav)
The number of locations may be daunting but all of them make sense
actually. Also, I
Nicolas Goaziou n.goaz...@gmail.com writes:
David Engster d...@randomsample.de writes:
Yes, I could do that for my specific setup. But it would be nice if this
stuff could just work, so that things like Outlook calendar invites
can be directly exported to .ics.
AFAIU, we're talking about a
Nicolas Goaziou writes:
David Engster d...@randomsample.de writes:
It's these multitude of timestamp locations which makes changing the
timestamp of an existing entry through Elisp so tedious (I had to deal
with that in org-caldav)
The number of locations may be daunting but all of them
David Engster d...@randomsample.de writes:
I'm actually not sure what org-element is capable of nowadays. What I'd
like to have is a way to parse entries into a structure
See `org-element-parse-buffer'.
which lets me access certain elements of the entry, like headline,
timestamps,
Nicolas Goaziou writes:
David Engster d...@randomsample.de writes:
I'm actually not sure what org-element is capable of nowadays. What I'd
like to have is a way to parse entries into a structure
See `org-element-parse-buffer'.
which lets me access certain elements of the entry, like
I have the problem that a certain kind Org entries is not exported by
the icalendar exporter, namely those created by the gnus-icalendar
package.
This package creates Org entries from calendar invites in the following
way (I've omitted some of the properties, but you get the idea);
** Some
10 matches
Mail list logo