emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Shironeko <shironeko@tesaguri.club>
To: emacs-orgmode@gnu.org
Subject: Re: Idea for handling timezones
Date: Fri, 23 Apr 2021 09:45:14 +0800	[thread overview]
Message-ID: <d42945fc3c20e30cec60aaa31fa0f4e9013ccbbf.camel@tesaguri.club> (raw)
In-Reply-To: <s4co6i$8gk$1@ciao.gmane.io>

Hi all,

I originally thought having the timezone in the header of the file would make
things simpler, since it meant all the timestamp would be in the same timezone,
rather than potentially different ones. But it seems that that might not be
inline with how others use their org files.

org actually already has a keyword for a per entry timezone, 
The problem with it is that no other facility of org plugs into that, it only
counts when exporting into other calendar systems, which I think is strange. If
it is indeed better to be able to set timezone per entry, then I think
supporting this properly in org would be best.

Only having CST etc timezone abbreviations is indeed problematic, because it is
ambiguous and kinda difficult to enter, also people don't necessarily
communicate with the correct designation (maybe they mean EDT but used EST, but
the time is unambiguously EDT).

With repeat tasks I don't think it would be a problem for tasks that repeats
daily or longer (since by definition they add to the day/month/year directly,
not counting how many days there are in a month for example). For hourly
repeating tasks it is indeed ambiguous, but I don't have an idea on what would
be better. Maybe people that have those can chime in.


  reply	other threads:[~2021-04-23  1:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  7:40 shironeko
2021-04-02 11:34 ` tomas
2021-04-03  0:36   ` Shironeko
2021-04-03  7:56     ` tomas
2021-04-03  8:03       ` shironeko
2021-04-03  8:30         ` tomas
2021-04-03  9:26           ` Shironeko
2021-04-03 11:23             ` Greg Minshall
2021-04-03 15:00               ` Russell Adams
2021-04-03 18:51                 ` Greg Minshall
2021-04-03 20:06                   ` Samuel Wales
2021-04-03 22:47                   ` Tim Cross
2021-04-04  0:51                     ` Tom Gillespie
2021-04-04 16:06                       ` Maxim Nikulin
2021-04-23  1:45                         ` Shironeko [this message]
2021-04-23  7:54                           ` tomas
2021-04-03 12:43             ` tomas
2021-04-03 12:47               ` Shironeko
2021-04-03 13:20                 ` Shironeko
2021-04-02 23:37 ` Tim Cross
2021-04-03  0:31   ` Samuel Wales
2021-04-03  0:43   ` Shironeko
2021-04-03  0:53     ` Samuel Wales
  -- strict thread matches above, loose matches on Subject: below --
2021-03-31  2:23 Shironeko

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:

  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=d42945fc3c20e30cec60aaa31fa0f4e9013ccbbf.camel@tesaguri.club \
    --to=shironeko@tesaguri.club \
    --cc=emacs-orgmode@gnu.org \


* 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


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).