From: David Engster <deng@randomsample.de>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Timestamps in properties not exported by icalendar exporter
Date: Sat, 22 Feb 2014 14:19:17 +0100 [thread overview]
Message-ID: <8738jbi8tm.fsf@engster.org> (raw)
In-Reply-To: <871tyvz86p.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 22 Feb 2014 12:41:02 +0100")
Nicolas Goaziou writes:
> David Engster <deng@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 properties are not valid Org timestamps, per Org
> syntax.
OK.
>> I think it would make sense if the exporter also looked for
>> time-stamps in the properties.
>
> There are already plenty of locations to use timestamps. We have
> scheduled, deadline, plain timestamps... I don't think we need more of
> them.
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), so using a property for it seemed like a good
idea. Anyway, I understand your reasoning, and I guess we should change
how gnus-icalendar generates its Org entries.
-David
next prev parent reply other threads:[~2014-02-22 13:19 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
2014-02-22 10:38 ` David Engster
2014-02-22 11:41 ` Nicolas Goaziou
2014-02-22 13:19 ` David Engster [this message]
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=8738jbi8tm.fsf@engster.org \
--to=deng@randomsample.de \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).