emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Randomcoder <randomcoder1@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: [proposal] timezone-aware timestamps enhancement
Date: Fri, 20 Mar 2015 11:29:08 +0200	[thread overview]
Message-ID: <20150320092908.GB7494@xw> (raw)
In-Reply-To: <87r3sm6z9z.fsf@delle7240.chemeng.ucl.ac.uk>

Hi Eric,

I've also seen these threads from the archive of the mailing list
discussing about the very same thing. 
In summary it seems that in 2008 Carsten's opinion on this was
that it would add a lot of complexity and it's a pandora's box
about to be open.

In 2014, Nicolas's reply seems a bit more encouraging.


On Wed, Mar 18, 2015 at 04:33:44PM +0000, Eric S Fraga wrote:
> There is no specific solution unfortunately.  Having spent a year living
> and working across time zones, I was unable to find a good
> solution.  And, in fact, the problem was compounded by trying to
> synchronise org data with Google's calendar and with MS Outlook.  I
> eventually simply stopped synchronising and relied on my computer
> having the time that was appropriate for where I was at the time. All

So would your computer find out the timezone and switch it automatically ?
(IIRC Ubuntu does that by default)

On Wed, Mar 18, 2015 at 04:33:44PM +0000, Eric S Fraga wrote:
> org data were "local" time with a fluid definition of "local".

I'd be interested in knowing a bit more about the "fluid definition".

  parent reply	other threads:[~2015-03-20  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18  8:13 [proposal] timezone-aware timestamps enhancement Randomcoder
2015-03-18 16:33 ` Eric S Fraga
2015-03-18 18:09   ` Ken Mankoff
2015-03-20  9:40     ` Randomcoder
2015-03-20 19:11       ` Ken Mankoff
2015-03-23 11:33       ` e.fraga
2015-03-20  9:29   ` Randomcoder [this message]
2015-03-23 11:35     ` e.fraga

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=20150320092908.GB7494@xw \
    --to=randomcoder1@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --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).