Re: [O] Timezones revisited

Russell Adams writes: > On Wed, Feb 01, 2017 at 11:14:15AM -0500, Peter Neilson wrote: >> On Wed, 01 Feb 2017 10:50:24 -0500, Eric Abrahamsen >> Presumably everyone already knows that the timezones are more complicated >> than hoi polloi believe? The offsets are not

Re: [O] Timezones revisited

Russell Adams writes: > On Wed, Feb 01, 2017 at 07:50:24AM -0800, Eric Abrahamsen wrote: >> Russell Adams writes: [...] >> Would it be completely out of the question to support an optional >> timezone marker? From (nth 1

Re: [O] Timezones revisited

On Wed, Feb 01, 2017 at 11:14:15AM -0500, Peter Neilson wrote: > On Wed, 01 Feb 2017 10:50:24 -0500, Eric Abrahamsen > Presumably everyone already knows that the timezones are more complicated > than hoi polloi believe? The offsets are not always integer values of > hours. For example,

Re: [O] Timezones revisited

On Wed, 01 Feb 2017 10:50:24 -0500, Eric Abrahamsen wrote: Russell Adams writes: I understand that Org's timestamp format does not include timezone information. Making that change would be an impractical modification. I'm frequently

Re: [O] Timezones revisited

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

Re: [O] Timezones revisited

Russell Adams writes: > I understand that Org's timestamp format does not include timezone > information. Making that change would be an impractical modification. > > I'm frequently working with several different timezones and I only > need to store a time stamp