From: Jean Louis <bugs@gnu.support>
To: Sterling Hooten <hooten@gmail.com>
Cc: "Thomas S. Dye" <tsd@tsdye.online>,
Tim Cross <theophilusx@gmail.com>,
Ihor Radchenko <yantar92@posteo.net>,
Daryl Manning <daryl@wakatara.com>,
rjhorn@alum.mit.edu, emacs-orgmode@gnu.org
Subject: Re: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda
Date: Fri, 27 Jan 2023 12:54:02 +0300 [thread overview]
Message-ID: <Y9OfOg4PM0LbJCyH@protected.localdomain> (raw)
In-Reply-To: <3035CDD5-41DD-4516-9E4E-9E0DF16BE2E0@gmail.com>
* Sterling Hooten <hooten@gmail.com> [2023-01-27 09:06]:
> Offset
> Constant duration difference between times of two time scales
> (ISO). i.e., a quantity to combine with a time scale to produce
> a wall time. e.g., Nepal uses a +5:45 offset from the UTC time
> scale.
I would be careful calling it constant as time offset is changing
depending of daylight saving time. It is not constant.
Time offset time stamp may be derived from time zone time. I am sure
about this.
Time zone time stamp cannot be unambiguously derived from time
offset. I am mostly sure about this.
> What kinds of representations would a calendar system capable of
> handling timezones require?
>
> • Instant (fixed)
> • This is referring to an unambiguous moment in time
> • e.g., 2007-02-03T05:00:00.000Z
> • Offset (fixed)
> • This captures the idea of "when did it happen for the person who
> made the observation"
> • e.g., 2007-02-03T04:00:00.000+01:00
Offset is not that fixed, maybe from viewpoint of storage as maybe it
is considered fixed in it's representation, but you have to keep in
mind that time offset by it's definition is changing itself, suddenly,
depending of daylight saving and time zone.
I am trying to find well described reference to read, try here:
Time Zones vs. Offsets – What's the Difference? Which Is Best?:
https://spin.atomicobject.com/2016/07/06/time-zones-offsets/
,----
| Putting It All Together
|
| Given a time zone and a UTC time, you can know the offset—and
| therefore the local time. Given a local time and an offset, you can
| know UTC time, but you do not know which time zone you’re in (because
| multiple timezones have the same offset). Given UTC and an offset, you
| can know the local time. Given a time zone and an offset, you don’t
| know much. That’s why a calendar systems work with time zones,
| offsets, and UTC; we need the offset to go from local time to UTC, and
| we need the time zone to go from UTC to local time.
`----
> • Instant with explicit offset and zone (fixed)
> • e.g., 2007-01-01T02:00:00.000+01:00[America/Chicago]
> • Zoned local date time (floating)
> • Tricky, requires decisions about how to interpret timestamps after
> political changes.
> • e.g., 2007-01-01T01:00:00.000[America/Chicago]
For calendars it is good to follow recommendation Internet Calendaring
and Schedulingn Core Object Specification (iCalendar)
iCalendar - Date and time format:
https://en.wikipedia.org/wiki/ICalendar#Date_and_time_format
In other words it is good to follow what other successful applications
are already doing.
For example, if you open Evolution calendar in Gnome:
evolution -c calendar
and make task, and save that task as iCalendar, then you can see what
time stamp format is used there for exchange purposes.
Representation for user using Org file is different from
representation for sharing purposes, as user already (mostly) have
specified local time zone on this computer, while sharing object such
as iCalendar file must take that information of local time zone and
store it unambiguously.
> I claim that before dealing with the nuances of calendar appointments,
> repeating events, agenda displays etc, that Org must first support
> fixed/absolute time instead of just floating time.
Parameters needed to make it fixed are already in computer, only
disconnected.
changing this time stamp for Org:
<2023-01-27 Fri 10:18>
to something "fixed" would break Org compatibility for past Org files.
While new unambigious time stamp formats may be introduced, the way to
go is with past time stamps is to understand the time stamp for
representation and calculation purposes by using OR logical function:
timestamp-time-zone OR heading-time-zone OR file-time-zone OR system-time-zone
as by using those, for now still disconnected parameters, one can get
the fixed time for representation purposes (Org export or sharing) or
calculation purposes (on local computer and by using some shared Org
objects).
> Without some basis time scale the conversions from time zones and
> offsets to some incremental time point is impossible. Resolving this
> prerequisite will also simplify the timezone discussion because we
> won't be mixing calendar issues with time issues.
I guess that OR consideration above may remedy it and keep past
compatibility while expanding more specific time stamp as option.
> What would a roadmap be?
>
> • Design and implement an absolute and offset timestamp system
> • Decide on a time scale
> • Decide on a format and syntax
> • Implement instant timestamps
> • Implement offeset timestamps
> • Design and implement the time zone aware calendar system This is a
> separate project.
Sounds complex to me and over board for program that tries to define
data type by using simple text written ambiguously by many people.
> What format and syntax should Org use?
>
> A heretical suggestion: We should abandon the day of week abbreviation
> and use a new format.
Day of week abbreviation is useful. Full day is even more
useful. Removing what is useful is not useful.
There is no calendar application that I know that does not specify
days of week.
> The current format generates a three leter abbreviation of the day of
> the week [2023-01-25 Wed 12:12]. I suggest supporting this as a
> legacy/simple format but switch to a format/encoding like
> [2023-01-25T15:13:42Z] for the new system.
Which format is more useful for people?
I find [2023-01-25 Wed 12:12] more useful, rather than the other one,
for reason that it has clear date, day of week and time.
And I always consider that Emacs packages like Org shall be designed
to be useful to majority of people, rather than to few who may have
the idea very right, but not comforting the majority of people.
There is no calendar application that I know that by default uses UTC
format, which representation is of course contradictory to large
majority of time zones and to people got used to, to display their
time in their time zone.
> Specifically I'm advocating for an extended ISO 8601 format,
> compatible with expanded dates and Level 2 of the EDTF, with some
> (bracket?) notation surrounding it such that Org can parse the
> syntax as a timestamp. I advocate further for the use of durations
> and repeating intervals to follow the same standard format. Thus
> instead of a range being formatted as:
>
> [2023-01-25 Wed 13:57]–[2023-01-26 Thu 13:57]
>
> it would be:
>
> [2023-01-25T16:57:42Z/2023-01-26T16:57:42Z].
Such representations should not become default to users, but used in
representation, or sharing, or re-writing of time stamps by user
option.
Using such time stamps by default in Org file is confusing for people
and showing time which is not their time to majority of people.
I am surprised and in same time disappointed, that your analysis leads
to conclusion that users should represent their time in UTC.
> What are the problems with the day of the week in existing format?
>
> • The day of the week is redundant information and can be rebuilt from
> an ISO date Any user who wishes to display a format with the day of
> the week can do so.
It is redundant or who?
Is it redundant for majority of Org users?
Maybe it is reundant for you?
For some people?
Do you know for who?
I never even heard some user here complaining for day of week
representation. Let me add one big fricking LOL here.
Any user who wishes to do anything could be left to program it alone
and do what they wish.
But programming should be useful to people by majority of demands and
wants.
> • It's a nonstandard format
The statement above miss the context. Non-standard where? How? In
which context?
In context of Org file is prime standard.
In context of Evolution calendar it is not standard, but neither the
graphical representation of a task in such calendar is standard.
Program's representation of time is NOT REQUIRED to be standard,
rather it shall be useful to user using the program to understand the
information.
In other words, representation shall be simple and readable,
understandable!
> Although the Org documentation says that the timestamps are
> "inspired by the standard ISO 8601 date/time format" the use of a
> day name is not contained in the ISO specification.
Being inspired does not mean "conforming to ISO 8601"
There is distinction, different context, of using time stamps inside
of Org file, and different context of "worldwide exchange and
communication of date and time related data", see ISO 8601 purposes.
I fully agree that in exchange or sharing of date/time information,
Org program should sometims use ISO 8601, but not in all exports.
For example in HTML export it is enough to say time and time zone. But
some people like to export it in ISO 8601. Such considerations could
be user option.
Right now HTML export is ambiguous as it does not have time zone.
The usage of ISO 8601 should rather depend on method exchange or
exporting.
But it should not be user's representation, as user is not a robot, or
program that is supposed to read computer-meant time stamps.
And you forgot to list disadvantages of making Org for robots, not for
human.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-01-27 13:11 UTC|newest]
Thread overview: 330+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 8:56 [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda Daryl Manning
2023-01-13 12:51 ` Tim Cross
2023-01-14 6:27 ` Daryl Manning
2023-01-14 12:46 ` Jean Louis
2023-01-14 11:18 ` Ihor Radchenko
2023-01-14 11:26 ` Daryl Manning
2023-01-14 11:42 ` Ihor Radchenko
2023-01-15 5:11 ` Max Nikulin
2023-01-15 13:41 ` Ihor Radchenko
2023-01-16 16:43 ` Max Nikulin
2023-01-16 18:37 ` Ihor Radchenko
2023-01-17 17:40 ` Max Nikulin
2023-01-18 9:59 ` Ihor Radchenko
2023-01-18 16:25 ` Jean Louis
2023-01-18 16:24 ` [SOLUTION] " Jean Louis
2023-01-20 10:57 ` Ihor Radchenko
2023-01-20 11:29 ` Daryl Manning
2023-01-20 11:36 ` Ihor Radchenko
2023-01-20 15:10 ` Daryl Manning
2023-01-20 11:39 ` Fraga, Eric
2023-01-20 11:48 ` Ihor Radchenko
2023-01-21 12:55 ` Jean Louis
2023-01-21 13:41 ` Ihor Radchenko
2023-01-21 9:21 ` Ihor Radchenko
2023-01-21 10:14 ` Max Nikulin
2023-01-22 11:49 ` Ihor Radchenko
2023-01-20 22:51 ` Tim Cross
2023-01-14 13:03 ` Tim Cross
2023-01-14 13:22 ` Ihor Radchenko
2023-01-15 19:10 ` Jean Louis
2023-01-16 11:21 ` Ihor Radchenko
2023-01-16 11:30 ` Daryl Manning
2023-01-16 11:39 ` Ihor Radchenko
2023-01-16 15:43 ` Daryl Manning
2023-01-16 19:07 ` Ihor Radchenko
2023-01-16 19:22 ` Robert Horn
2023-01-16 19:41 ` Ihor Radchenko
2023-01-16 20:47 ` Robert Horn
2023-01-16 21:02 ` Tom Gillespie
2023-01-16 21:48 ` Robert Horn
2023-01-17 8:53 ` Ihor Radchenko
2023-01-17 3:55 ` Daryl Manning
2023-01-17 8:22 ` Tim Cross
2023-01-17 9:15 ` Ihor Radchenko
2023-01-17 9:45 ` Tim Cross
2023-01-18 9:15 ` Ihor Radchenko
2023-01-18 11:43 ` Tim Cross
2023-01-18 12:02 ` Ihor Radchenko
2023-01-18 21:16 ` Tim Cross
2023-01-19 5:29 ` Jean Louis
2023-01-19 6:25 ` Thomas S. Dye
2023-01-19 14:17 ` Jean Louis
2023-01-19 15:55 ` Thomas S. Dye
2023-01-21 13:10 ` Jean Louis
2023-01-21 16:23 ` Thomas S. Dye
2023-01-21 13:50 ` Jean Louis
2023-01-21 14:31 ` Max Nikulin
2023-01-21 16:55 ` Thomas S. Dye
2023-01-19 7:23 ` Tim Cross
2023-01-19 14:32 ` Jean Louis
2023-01-19 20:09 ` Tim Cross
2023-01-19 23:02 ` Thomas S. Dye
2023-01-19 23:51 ` Tim Cross
2023-01-20 0:24 ` Thomas S. Dye
2023-01-20 3:46 ` Tim Cross
2023-01-20 6:14 ` Thomas S. Dye
2023-01-27 6:06 ` Sterling Hooten
2023-01-27 6:09 ` Daryl Manning
2023-01-27 9:54 ` Jean Louis [this message]
2023-01-27 21:04 ` Tim Cross
2023-01-29 4:09 ` Jean Louis
2023-01-29 6:21 ` Thomas S. Dye
2023-01-29 6:46 ` Daryl Manning
2023-01-29 14:10 ` Ihor Radchenko
2023-01-30 19:37 ` Jean Louis
2023-01-31 0:53 ` Thomas S. Dye
[not found] ` <0597910b-9b01-3c0c-5d06-da171e0de4cd@gmx.at>
2023-01-31 6:08 ` Jean Louis
2023-01-29 6:31 ` Max Nikulin
2023-01-30 20:36 ` Jean Louis
2023-01-30 20:38 ` Jean Louis
2023-01-29 20:26 ` Tim Cross
2023-01-30 20:55 ` Jean Louis
2023-01-30 21:54 ` Tim Cross
2023-01-31 7:04 ` Jean Louis
2023-01-31 8:14 ` Max Nikulin
2023-01-31 13:02 ` Jean Louis
2023-01-27 11:09 ` Ihor Radchenko
2023-01-27 12:49 ` Sterling Hooten
2023-01-27 13:00 ` Ihor Radchenko
2023-01-27 15:03 ` Jean Louis
2023-01-30 13:08 ` Ihor Radchenko
2023-01-27 20:58 ` Tim Cross
2023-01-30 11:25 ` Greg Minshall
2023-01-31 11:48 ` [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda) Ihor Radchenko
2023-01-31 12:19 ` Daryl Manning
2023-01-31 12:41 ` Ihor Radchenko
[not found] ` <CAL9aZksf8AGF=dXg0KAtLPyu1ATt1fLpvdsjN6GMCuK2KRQ56w@mail.gmail.com>
2023-01-31 13:33 ` Ihor Radchenko
2023-01-31 13:22 ` Jean Louis
2023-01-31 13:46 ` Ihor Radchenko
2023-01-31 19:59 ` Jean Louis
2023-02-01 12:42 ` Ihor Radchenko
2023-02-01 15:28 ` Jean Louis
2023-02-01 16:30 ` Ihor Radchenko
2023-01-31 20:12 ` Jean Louis
2023-02-01 5:46 ` tomas
2023-02-01 7:29 ` Jean Louis
2023-02-01 7:52 ` Tim Cross
2023-02-01 8:32 ` Jean Louis
2023-02-01 8:46 ` Ihor Radchenko
2023-02-01 9:38 ` Tim Cross
2023-02-01 10:15 ` Ihor Radchenko
2023-02-01 14:53 ` Jean Louis
2023-02-01 16:36 ` Ihor Radchenko
2023-02-01 10:46 ` Max Nikulin
2023-02-01 14:43 ` Jean Louis
2023-02-01 16:45 ` Ihor Radchenko
2023-02-02 3:05 ` Max Nikulin
2023-02-02 8:59 ` Ihor Radchenko
2023-02-01 9:40 ` [POLL] Proposed syntax for timestamps with time zone info Stefan Nobis
2023-02-01 9:45 ` Ihor Radchenko
2023-02-01 14:38 ` [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda) Jean Louis
2023-02-01 16:50 ` Ihor Radchenko
2023-02-03 15:48 ` [POLL] Proposed syntax for timestamps with time zone info Stefan Nobis
2023-02-04 5:07 ` Jean Louis
2023-02-01 9:06 ` Stefan Nobis
2023-02-01 9:20 ` tomas
2023-02-01 9:48 ` Stefan Nobis
2023-10-29 1:04 ` Jean Louis
2023-02-06 15:34 ` Marcin Borkowski
2023-02-06 17:03 ` tomas
2023-02-07 21:08 ` Jean Louis
2023-10-29 1:02 ` Jean Louis
2023-02-01 7:00 ` [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda) Thomas S. Dye
2023-02-01 7:41 ` Jean Louis
2023-01-31 17:56 ` [POLL] Proposed syntax for timestamps with time zone info Fraga, Eric
2023-01-31 18:13 ` Ihor Radchenko
2023-01-31 18:22 ` Fraga, Eric
2023-01-31 18:56 ` [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda) Greg Minshall
2023-02-01 12:48 ` Ihor Radchenko
2023-02-01 12:52 ` tomas
2023-02-02 4:49 ` Greg Minshall
2023-01-31 20:41 ` Tim Cross
2023-01-31 23:50 ` Samuel Wales
2023-02-01 13:01 ` Ihor Radchenko
2023-02-04 22:33 ` Samuel Wales
2023-02-04 22:49 ` Samuel Wales
2023-02-05 10:38 ` Ihor Radchenko
2023-02-01 11:56 ` Christian Moe
2023-02-01 12:20 ` Ihor Radchenko
[not found] ` <87o7qdsf7h.fsf@christianmoe.com>
2023-02-01 13:26 ` POSIX TS spec reverses the meaning of TZ offset compared to ISO (was: [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda)) Ihor Radchenko
2023-02-01 13:51 ` tomas
2023-02-01 21:57 ` POSIX TS spec reverses the meaning of TZ offset compared to ISO (was: [POLL] Proposed syntax for timestamps with time zone info Heinz Tuechler
2023-02-01 22:50 ` Samuel Wales
2023-02-02 9:01 ` Ihor Radchenko
2023-02-02 3:22 ` Max Nikulin
2023-02-02 7:45 ` POSIX TS spec reverses the meaning of TZ offset compared to ISO Heinz Tuechler
2023-02-02 8:33 ` tomas
2023-02-02 9:37 ` Heinz Tuechler
2023-02-04 15:44 ` Max Nikulin
2023-02-02 5:35 ` POSIX TS spec reverses the meaning of TZ offset compared to ISO (was: [POLL] Proposed syntax for timestamps with time zone info tomas
2023-02-02 8:56 ` Ihor Radchenko
2023-02-01 15:16 ` POSIX TS spec reverses the meaning of TZ offset compared to ISO (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda) Max Nikulin
2023-02-02 8:34 ` Ihor Radchenko
2023-02-02 13:59 ` Max Nikulin
2023-02-02 14:06 ` Ihor Radchenko
2023-02-01 15:41 ` [POLL] Proposed syntax for timestamps with time zone info " Jean Louis
2023-02-02 8:38 ` Ihor Radchenko
2023-02-03 11:31 ` Jean Louis
2023-02-04 10:58 ` Ihor Radchenko
2023-02-04 19:32 ` Jean Louis
2023-02-05 9:14 ` Ihor Radchenko
2023-02-02 3:46 ` Timothy
2023-02-02 9:12 ` Ihor Radchenko
2023-02-02 9:12 ` Timothy
2023-02-02 9:20 ` Ihor Radchenko
2023-02-02 9:27 ` Timothy
2023-02-02 9:38 ` [POLL] Proposed syntax for timestamps with time zone info Stefan Nobis
2023-01-30 12:30 ` [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda Ihor Radchenko
2023-01-30 15:30 ` Greg Minshall
2023-01-30 15:38 ` Ihor Radchenko
2023-01-30 15:48 ` Greg Minshall
2023-01-20 4:03 ` Max Nikulin
2023-01-20 5:39 ` Tim Cross
2023-01-20 7:28 ` Max Nikulin
2023-01-20 8:11 ` Tim Cross
2023-01-20 15:29 ` Max Nikulin
2023-01-20 22:56 ` Tim Cross
2023-01-20 9:35 ` Fraga, Eric
2023-01-20 10:48 ` Ihor Radchenko
2023-01-20 6:46 ` Thomas S. Dye
2023-01-20 7:34 ` Max Nikulin
2023-01-20 8:17 ` Tim Cross
2023-01-20 12:17 ` Max Nikulin
2023-01-20 16:09 ` Thomas S. Dye
2023-01-20 16:56 ` Max Nikulin
2023-01-20 20:37 ` Thomas S. Dye
2023-01-21 0:14 ` Tim Cross
2023-01-21 0:37 ` Thomas S. Dye
2023-01-21 5:53 ` Max Nikulin
2023-01-21 15:55 ` Thomas S. Dye
2023-01-22 12:14 ` Max Nikulin
2023-01-22 13:35 ` Thomas S. Dye
2023-01-22 14:09 ` Max Nikulin
2023-01-20 23:38 ` Tim Cross
2023-01-21 6:21 ` Max Nikulin
2023-01-21 21:29 ` Tim Cross
2023-01-22 5:50 ` UTC or not UTC for timestamps in the past ([FEATURE REQUEST] Timezone support in org-mode) Max Nikulin
2023-01-22 6:17 ` Thomas S. Dye
2023-01-22 8:35 ` Max Nikulin
2023-01-22 16:54 ` Thomas S. Dye
2023-01-23 6:28 ` Jean Louis
2023-01-23 16:04 ` Thomas S. Dye
2023-01-24 2:34 ` Max Nikulin
2023-01-24 2:44 ` Thomas S. Dye
2023-01-24 4:48 ` Max Nikulin
2023-01-24 19:18 ` Jean Louis
2023-01-24 9:34 ` Ihor Radchenko
2023-01-24 16:41 ` Thomas S. Dye
2023-01-26 15:37 ` Max Nikulin
2023-01-26 16:31 ` Thomas S. Dye
2023-01-27 21:21 ` Tim Cross
2023-01-22 7:48 ` Tim Cross
2023-01-24 17:09 ` Max Nikulin
2023-01-24 19:20 ` Jean Louis
2023-01-24 20:50 ` Tim Cross
2023-01-19 10:35 ` [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda Ihor Radchenko
2023-01-19 17:57 ` Alexander Adolf
2023-01-21 13:51 ` Jean Louis
2023-01-18 17:09 ` Max Nikulin
2023-01-17 8:45 ` Ihor Radchenko
2023-01-19 16:56 ` Robert Horn
2023-01-19 17:44 ` Alexander Adolf
2023-01-19 17:48 ` Alexander Adolf
2023-01-17 15:37 ` Jean Louis
2023-01-18 9:29 ` Ihor Radchenko
2023-01-18 16:11 ` Jean Louis
2023-01-18 21:31 ` Tim Cross
2023-01-19 10:40 ` Ihor Radchenko
2023-01-17 17:28 ` Max Nikulin
2023-01-17 19:49 ` Ihor Radchenko
2023-01-18 16:21 ` Jean Louis
2023-01-18 16:20 ` Jean Louis
2023-01-20 16:27 ` Max Nikulin
2023-01-19 17:33 ` Alexander Adolf
2023-01-16 20:25 ` Tim Cross
2023-01-17 9:07 ` Ihor Radchenko
2023-01-17 15:24 ` Jean Louis
2023-01-18 9:34 ` Ihor Radchenko
2023-01-18 16:07 ` Jean Louis
2023-01-19 10:43 ` Ihor Radchenko
2023-01-19 14:37 ` Jean Louis
2023-01-15 20:43 ` Jean Louis
2023-01-16 11:25 ` Ihor Radchenko
2023-01-17 15:19 ` Jean Louis
2023-01-18 9:38 ` Ihor Radchenko
2023-01-16 5:01 ` Tom Gillespie
2023-01-16 12:31 ` Ihor Radchenko
2023-01-16 20:32 ` Tim Cross
2023-01-16 20:51 ` Tom Gillespie
2023-01-17 9:12 ` [FR] Allow BC years in timestamps (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda) Ihor Radchenko
2023-01-13 19:06 ` [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda Jean Louis
2023-01-14 7:12 ` Max Nikulin
2023-01-14 9:32 ` Tim Cross
2023-01-14 11:08 ` Russell Adams
2023-01-14 11:35 ` Ihor Radchenko
2023-01-14 12:00 ` Russell Adams
2023-01-14 12:16 ` [FR] Allow end date and max repeat count for timestamps with repeaters (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda) Ihor Radchenko
2023-01-15 1:09 ` Samuel Wales
2023-01-15 13:45 ` Ihor Radchenko
2023-01-15 23:49 ` Samuel Wales
2023-01-15 23:53 ` Samuel Wales
2023-01-16 13:01 ` Ihor Radchenko
2023-01-14 12:19 ` [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda Ihor Radchenko
2023-01-14 12:21 ` Russell Adams
2023-01-14 12:31 ` Ihor Radchenko
2023-01-14 11:30 ` Ihor Radchenko
2023-01-14 14:09 ` Tim Cross
2023-01-14 14:38 ` Ihor Radchenko
2023-01-14 14:48 ` tomas
2023-01-14 15:05 ` Ihor Radchenko
2023-01-14 16:50 ` tomas
2023-01-14 17:06 ` Ihor Radchenko
2023-01-14 17:13 ` tomas
2023-01-15 19:54 ` Jean Louis
2023-01-14 21:52 ` Tim Cross
2023-01-15 13:52 ` Ihor Radchenko
2023-01-20 14:34 ` Alexander Adolf
2023-01-15 20:03 ` Jean Louis
2023-01-15 19:52 ` Jean Louis
2023-01-16 13:11 ` Ihor Radchenko
2023-01-14 20:56 ` Tim Cross
2023-01-15 20:24 ` Jean Louis
2023-01-15 4:37 ` Max Nikulin
2023-01-15 5:03 ` Max Nikulin
2023-01-15 20:28 ` Jean Louis
2023-01-16 13:17 ` Ihor Radchenko
2023-01-14 11:55 ` Max Nikulin
2023-01-14 13:50 ` Tim Cross
2023-01-14 16:50 ` Max Nikulin
2023-01-14 20:30 ` Tim Cross
2023-01-15 4:00 ` Max Nikulin
2023-01-15 7:53 ` Tim Cross
2023-01-15 19:26 ` Jean Louis
2023-01-16 13:20 ` Ihor Radchenko
2023-01-15 14:00 ` Ihor Radchenko
2023-01-14 13:08 ` Jean Louis
2023-01-14 16:58 ` Max Nikulin
2023-01-14 19:43 ` Tim Cross
2023-01-15 6:37 ` tomas
2023-01-15 14:07 ` Ihor Radchenko
2023-01-15 20:43 ` Tim Cross
2023-01-16 5:20 ` Tom Gillespie
2023-01-16 13:29 ` Ihor Radchenko
2023-01-16 17:30 ` Tom Gillespie
2023-01-16 17:53 ` Ihor Radchenko
2023-01-16 13:27 ` Ihor Radchenko
2023-01-15 19:14 ` Jean Louis
2023-01-16 4:20 ` Max Nikulin
2023-01-15 19:12 ` Jean Louis
2023-01-14 5:14 ` Samuel Wales
2023-01-14 5:51 ` Tom Gillespie
2023-01-14 6:40 ` tomas
2023-01-26 15:24 ` Org mode timestamps on the Moon ;] (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda) Ihor Radchenko
2023-01-26 16:08 ` Org mode timestamps on the Moon ;] Fraga, Eric
2023-01-26 16:28 ` Thomas S. Dye
2023-01-26 23:40 ` Org mode timestamps on the Moon ;] (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda) Tom Gillespie
2023-01-30 10:13 ` Org mode timestamps on the Moon ; ] " Greg Minshall
2023-01-30 13:05 ` Org mode timestamps on the Moon ;] " Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2023-01-15 19:16 [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda Thomas S. Dye
2023-01-28 6:26 Max Nikulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y9OfOg4PM0LbJCyH@protected.localdomain \
--to=bugs@gnu.support \
--cc=daryl@wakatara.com \
--cc=emacs-orgmode@gnu.org \
--cc=hooten@gmail.com \
--cc=rjhorn@alum.mit.edu \
--cc=theophilusx@gmail.com \
--cc=tsd@tsdye.online \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).