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 14:44:02 +0100 [thread overview]
Message-ID: <87sirbxnx9.fsf@gmail.com> (raw)
In-Reply-To: <8738jbi8tm.fsf@engster.org> (David Engster's message of "Sat, 22 Feb 2014 14:19:17 +0100")
David Engster <deng@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 don't think it is really difficult to change
a timestamp through Elisp, due to specialized functions (e.g.
`org-schedule').
Anyway, if you think this area can be improved, feel free to make
suggestions.
> so using a property for it seemed like a good idea.
This has been discussed a few times on this ML already.
Carsten's argument is that new users shouldn't have to deal with hidden
data, like property drawers, for such basic features.
IMO, it also have an advantage from an implementation POV: important
timestamps are located right below the headline, whereas a property
drawer can be found anywhere in the whole section.
> Anyway, I understand your reasoning, and I guess we should change how
> gnus-icalendar generates its Org entries.
I think so, too.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-02-22 13:43 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
2014-02-22 13:44 ` Nicolas Goaziou [this message]
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=87sirbxnx9.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).