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 always integer values of
>> ho
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 (current-time-zone))?
>>
>> <2017-02-01 Wed PST>
>>
>> The plumbing for t
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, Newfoundland
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 working with several different timezones and I only
need
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 timezon
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 converted to my local time.
>
> Do
