From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: TIMEZONE property for ical export
Date: Sat, 19 Aug 2017 10:34:54 +0200 [thread overview]
Message-ID: <87fucolzv5.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87ziawx1f7.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 18 Aug 2017 09:53:32 -0700")
Hello,
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Out of curiosity, what's your stance on supporting time zones in Org's
> timestamps? It would be an enormous amount of work, obviously, but in
> principle?
In principle I agree this would be a very good thing, if possible at
all.
> That's pretty much what it was before I messed with it, and I was a
> little confused because no callers of `org-icalendar-convert-timestamp'
> ever used the optional fourth argument at all. My thinking was that
> users might want to explicitly set the timezone to "UTC". To be honest
> I'm not sure why they would, but I also don't know why we'd accept t
> when nothing uses it. I found the whole handling of utc-or-not a bit
> confusing. What do you think?
I have no strong opinion about this. I was merely concerned about
consistency. E.g., when using `format-time-string', I never think about
"UTC" for the last optional argument.
BTW, as long as Org doesn't support time zones, the "ox-icalendar"
property may be prefixed with "ICALENDAR_" (e.g., ICALENDAR_TZ).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-08-19 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 16:53 TIMEZONE property for ical export Eric Abrahamsen
2017-08-19 8:34 ` Nicolas Goaziou [this message]
2017-08-19 17:13 ` Eric Abrahamsen
2017-08-19 19:25 ` Nicolas Goaziou
2017-08-19 19:56 ` Eric Abrahamsen
2017-08-19 21:20 ` Nicolas Goaziou
2017-08-19 21:54 ` Eric Abrahamsen
2017-08-19 22:14 ` Nicolas Goaziou
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=87fucolzv5.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).