From: Titus von der Malsburg <malsburg@posteo.de>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Michael Brand <michael.ch.brand@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Time-zone in dates
Date: Wed, 08 Jul 2015 10:22:09 -0700 [thread overview]
Message-ID: <87r3oi7ef2.fsf@posteo.de> (raw)
In-Reply-To: <87615uiovg.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]
On 2015-07-08 Wed 09:40, Eric S Fraga wrote:
> On Wednesday, 8 Jul 2015 at 11:16, Russell Adams wrote:
>
> [...]
>
>> Then would you store the time in UTC only, or support a full timestamp
>> that included timezone?
>>
>> Finally when being displayed they can use the user's $TZ by default,
>> and maybe a suffix of @ TZ inside the date syntax?
>
> The ideal implementation, in my opinion, would have time stamps defined
> & stored with time zone information, as given by the user when creating
> them (although this could default to UTC, say, if not present in the
> time stamp) but displayed according to the user's $TZ (or overridden
> with emacs variable) in cases like agenda views.
I like this proposal because it solves the problem at hand (as far as I
can tell) but isn’t over-engineered. I also like that the date string
that the user sees would be the string stored in the file, at least in
the default case (non-agenda view). The mostly literal display of files
is what sets org-mode apart from other outlines because that allows
users to take full advantage of Emacs’ powerful text editing
capabilities.
> For upwards compatibility, however, it might be best if time stamps with
> no time zone information be considered to be at the user's timezone,
> as it is now.
This point is important. Whatever the solution is it should not break
documents and workflows for users who don’t care about time zones. I
agree that time zones are important for some people but let’s face it,
org-mode made it thus far without support time zones, which suggests
that it’s not that big of a deal for most users.
Titus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-07-08 17:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 13:40 Time-zone in dates Oleg Sivokon
2015-06-26 14:12 ` Eric S Fraga
2015-06-26 14:33 ` Left Right
2015-06-26 14:38 ` J. David Boyd
2015-06-26 15:10 ` Eric S Fraga
2015-06-26 19:20 ` Nicolas Goaziou
2015-06-26 19:57 ` francois
2015-06-26 21:48 ` Nicolas Goaziou
2015-06-29 13:17 ` Eric S Fraga
2015-06-30 1:17 ` Nick Dokos
2015-06-30 7:36 ` Eric S Fraga
2015-06-30 15:08 ` Nick Dokos
2015-07-01 6:27 ` Eric S Fraga
2015-07-01 10:04 ` Michael Brand
2015-07-01 11:22 ` Eric S Fraga
2015-07-07 17:27 ` Russell Adams
2015-07-08 15:59 ` Don Armstrong
2015-07-08 16:16 ` Russell Adams
2015-07-08 16:40 ` Eric S Fraga
2015-07-08 17:22 ` Titus von der Malsburg [this message]
2015-07-07 17:14 ` Don Armstrong
2015-07-01 15:17 ` Nick Dokos
2015-07-01 22:17 ` Left Right
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=87r3oi7ef2.fsf@posteo.de \
--to=malsburg@posteo.de \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@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).