Jean Louis <bugs@gnu.support> writes: >> >> I am not sure what is the problem. >> >> The timestamps that should stay in local time will be automatically >> >> updated as your system TZ is updated. >> > >> > Then Org shall know what was local time! Without being specified in >> > the time stamp, it has to be specified somewhere, as computer can't >> > know at which time zone was it specified. >> >> We need nothing to use current time zone. And we already do it. >> >> System clock knows the current time zone. Emacs has an ability to >> determine current time zone. See `current-time-zone'. This works >> automatically (and already) because we use `encode-time'. > > Then you did not understand the point. > > For users who use Org personally, in single place, single time zone, > who do no travel, who do not share headings, tasks, and files > internationally, they really do not need hussle with time zones! > > However, when nice strong guy makes an Org file with list of tasks in > Ukraine and send it to nice girl Florida, she will simply think that > at 9 o'clock she has to discuss making visa with her fiance, but > fiance is already pissed off because she did not appear at online > meeting.
Sure. Then, a guy from Ukraine can add default timezone to the shared file/heading. It will then apply to all the timestamps that do not explicitly specify the time zone in the file/heading contents. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>