emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Patch that enables visibility settings in org-mode iCalendar export
Date: Fri, 18 Aug 2017 11:13:50 +0200	[thread overview]
Message-ID: <87wp61me5t.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87valm3rwe.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 17 Aug 2017 12:39:45 -0700")

Hello,

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Hey, now's the time to bring up something I've wanted to do for
> a while:

I think this deserves its own thread.

> adding support for per-entry timezones to the ical export. 

It sounds good.

> I've attached a draft patch that shows what I mean. Basically you give
> an entry a TIMEZONE property in the tz database format (eg
> "Europe/London") and it will pass that on to the DTSTART/DTEND
> properties.
>
> I suppose it would also be possible to have separate properties for
> start and end timezones, then we could do plane trips!

Right. But since Org doesn't support time zones, the usefulness may be
limited.

> +When optional argument TZ is non-nil, timezone data time will be
> +added to the timestamp.  It can be the string \"UTC\", to use UTC
> +time, or a string in the IANA TZ database
> +format (e.g. \"Europe/London\").  In either case, the value of
> +`org-icalendar-date-time-format' will be ignored."

I suggest to have symbol t as an equivalent to "UTC", for compatibility
with, e.g., ZONE in `format-time-string'.

Thank you for the work.


Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2017-08-18  9:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 18:49 Patch that enables visibility settings in org-mode iCalendar export Tobias Schlemmer
2017-08-17 16:09 ` Nicolas Goaziou
2017-08-17 19:39   ` Eric Abrahamsen
2017-08-18  9:13     ` Nicolas Goaziou [this message]

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=87wp61me5t.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).