From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-agenda thinks timestamps after 23:00 correspond to the next day [9.5.2 (release_9.5.2-25-gaf6f12 @ /home/ignacio/repos/emacs/lisp/org/)]
Date: Thu, 31 Mar 2022 19:38:51 +0700 [thread overview]
Message-ID: <t247ct$ik5$1@ciao.gmane.io> (raw)
In-Reply-To: <PAXPR06MB7760238F410CBE3203F78EE0C61E9@PAXPR06MB7760.eurprd06.prod.outlook.com>
On 29/03/2022 20:09, Ignacio Casso wrote:
>
> Let's consider the timestamp "<2022-03-29 mar 23:00>" as an example:
>
> 1) (org-parse-time-string "<2022-03-29 mar 23:00>") returns (0 0 23 29 3
> 2022 nil nil nil).
>
> 2) (encode-time '(0 0 23 29 3 2022 nil nil nil)) returns '(25155 29520)
> in Emacs 27, but (25155 33120) in Emacs 29
Ubuntu-20.04 LTS has emacs-26.3, so...
Could you, please, try
(encode-time '(0 0 23 29 3 2022 nil -1 nil))
^^^
Accordingly to
"TIME is a list (SECOND MINUTE HOUR DAY MONTH YEAR IGNORED DST ZONE)."
it should be daylight saving time flag and -1 means "guess" unlike nil
that tells "no DST".
Emacs-26 does not support DST:
(encode-time SECOND MINUTE HOUR DAY MONTH YEAR &optional ZONE)
Current master HEAD:
(encode-time TIME &rest OBSOLESCENT-ARGUMENTS)
If my guess is right, `org-parse-time-string' should add -1 instead of
nil in that position.
next prev parent reply other threads:[~2022-03-31 12:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 13:09 [BUG] org-agenda thinks timestamps after 23:00 correspond to the next day [9.5.2 (release_9.5.2-25-gaf6f12 @ /home/ignacio/repos/emacs/lisp/org/)] Ignacio Casso
2022-03-30 7:13 ` Ignacio Casso
2022-03-30 9:48 ` [BUG] org-agenda thinks timestamps after 23:00 correspond to the next day Max Nikulin
2022-03-30 10:17 ` Ignacio Casso
2022-03-31 12:38 ` Max Nikulin [this message]
2022-03-31 14:11 ` [BUG] org-agenda thinks timestamps after 23:00 correspond to the next day [9.5.2 (release_9.5.2-25-gaf6f12 @ /home/ignacio/repos/emacs/lisp/org/)] Ignacio Casso
2022-03-31 16:57 ` Max Nikulin
2022-03-31 21:37 ` Tim Cross
2022-04-05 4:20 ` Kyle Meyer
2022-04-22 15:47 ` Max Nikulin
2022-04-23 7:20 ` Ignacio Casso
2022-04-23 8:23 ` Max Nikulin
2022-10-01 10:14 ` Ihor Radchenko
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='t247ct$ik5$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).