From: Nicolas Goaziou <n.goaziou@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Timestamps in properties not exported by icalendar exporter
Date: Sat, 22 Feb 2014 10:44:54 +0100 [thread overview]
Message-ID: <87lhx34h2h.fsf@gmail.com> (raw)
In-Reply-To: <87bny0ia7d.fsf@engster.org> (David Engster's message of "Fri, 21 Feb 2014 19:37:10 +0100")
Hello,
David Engster <deng@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 of the properties, but you get the idea);
>
> ** Some appointment (location)
> :PROPERTIES:
> :ICAL_EVENT: t
> :ID: 040000008200E00074C5B7101A82E00800
> :DT: <2013-12-09 Mon 13:00-13:30>
> :END:
>
> Body text
>
>
> 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 organizer decides to change the event and sends a change
> request).
>
> The exporter could of course simply take the first timestamp it finds in
> the properties, but it could be the wrong one; for instance, there could
> be a LOGBOOK timestamp before the one in DT. Hence I think it would be
> nice if you could tell the exporter which property to use as timestamp
> during export.
Can't you just walk the buffer and turn such properties into plain
time-stamps (or scheduled, deadline...), in a hook?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-02-22 9:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 18:37 Timestamps in properties not exported by icalendar exporter David Engster
2014-02-22 9:44 ` Nicolas Goaziou [this message]
2014-02-22 10:38 ` David Engster
2014-02-22 11:41 ` Nicolas Goaziou
2014-02-22 13:19 ` David Engster
2014-02-22 13:44 ` Nicolas Goaziou
2014-02-22 16:12 ` David Engster
2014-02-22 17:42 ` Nicolas Goaziou
2014-02-22 17:52 ` David Engster
2014-02-22 13:47 ` Nick Dokos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhx34h2h.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).