emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Ihor Radchenko <yantar92@posteo.net>
To: Tebe Nigrelli <nigrellitebe@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: [BUG] Shifting timestamp hours around daylight transition (was: Clock dates - org-shiftdown not working)
Date: Tue, 28 Mar 2023 10:52:18 +0000	[thread overview]
Message-ID: <87wn31up0d.fsf@localhost> (raw)
In-Reply-To: <CALsznM=CQEpimm2i-6ECNZQeJfwYjZfDxH0xv0kH=zeaiPOWeQ@mail.gmail.com>

Tebe Nigrelli <nigrellitebe@gmail.com> writes:

> On a clean configuration, applying org-shiftdown does not work for the
> following date format, written as a clock. I want to reduce the number of
> hours
> on the second date from "03:" to "02:". This is what happens if I apply
> org-shiftdown:
>
> Instructions to reproduce the bug:
> Try doing org-shiftdown on the minutes "05" or the hours "03".
> Result:
> CLOCK: [2023-03-25 Sat 21:40]--[2023-03-26 Sun 03:05] =>  4:25

At least in some parts of Europe, the time from 2023-03-26 2:00 to
2023:03-26 2:59 does not exist. It is the hour-forward daylight
transition.

So, when Org is trying to change the data to 2023-03-26 2:05, Emacs date
library refuses and instead sets the closes valid time.

I am not sure would be the best course of action here.
1. We can jump over the invalid hours in the direction requested by user
2. We can throw an error, making the user aware about the daylight
   thing.

I am more in favour of (2) because things like this are easy to overlook.

-- 
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>

     prev parent reply	other threads:[~2023-03-28 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26 10:20 Clock dates - org-shiftdown not working Tebe Nigrelli
2023-03-28 10:52 ` Ihor Radchenko [this message]

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=87wn31up0d.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=nigrellitebe@gmail.com \
    /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

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).