Russell Adams <address@hidden> 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.
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.
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.
E