From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell Adams Subject: Re: Timezones revisited Date: Wed, 1 Feb 2017 17:05:41 +0100 Message-ID: <20170201160541.GI7187@volibear.adamsinfoserv.com> References: <20170131230346.GV7187@volibear.adamsinfoserv.com> <87shnxuczj.fsf@pellet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53983) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYxQn-0007cK-9h for emacs-orgmode@gnu.org; Wed, 01 Feb 2017 11:06:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cYxQk-0007S5-3Z for emacs-orgmode@gnu.org; Wed, 01 Feb 2017 11:06:49 -0500 Received: from cross.birch.relay.mailchannels.net ([23.83.209.46]:61431) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cYxQg-0007Ob-3I for emacs-orgmode@gnu.org; Wed, 01 Feb 2017 11:06:46 -0500 Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id B9F9CA4634 for ; Wed, 1 Feb 2017 16:06:14 +0000 (UTC) Received: from kefka.asoshared.com (unknown [100.96.16.128]) by relay.mailchannels.net (Postfix) with ESMTPA id 1712EA3F40 for ; Wed, 1 Feb 2017 16:06:12 +0000 (UTC) Received: from 5ed25635.cm-7-3b.dynamic.ziggo.nl ([94.210.86.53]:4325 helo=localhost) by kefka.asoshared.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1cYxQB-0000vO-Ji for emacs-orgmode@gnu.org; Wed, 01 Feb 2017 11:06:11 -0500 Content-Disposition: inline In-Reply-To: <87shnxuczj.fsf@pellet> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org On Wed, Feb 01, 2017 at 07:50:24AM -0800, Eric Abrahamsen wrote: > Russell Adams writes: > > > > Does the time stamp input support some form of timezone input? I > > checked the manual and tried a few methods and they don't appear > > supported. > > If the time stamp format doesn't support timezone info, then the input > method won't either, unfortunately. I had one of my occasional attacks > of enthusiasm about this subject recently -- using org-caldav while > you're traveling really exposes the limitations of timezone-unaware > scheduling. That's my case. Now I'm using the date command with -d to translate for me. > Would it be completely out of the question to support an optional > timezone marker? From (nth 1 (current-time-zone))? > > <2017-02-01 Wed PST> > > The plumbing for time calculations would be... an adventure. But it > seems like it could be done in a backwards-compatible way. I gave some thought to the idea of storing all timestamps in GMT and then each buffer could have a timezone defined or use the system time. Then the relative time would be overlaid in viewing the file. That's a real stretch though, as I think this would take significant effort. I think for now a simple method to input a time from another timezone and convert it to your own would suffice. That wouldn't change anything regarding storage or working with timestamps, only a one time conversion a the time of data entry. I wonder if that isn't a fast change? Thanks. ------------------------------------------------------------------ Russell Adams RLAdams@AdamsInfoServ.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3