From: Max Nikulin <manikulin@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Ignacio Casso <ignaciocasso@hotmail.com>, 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: Fri, 22 Apr 2022 22:47:24 +0700 [thread overview]
Message-ID: <e10fefb2-5ffd-6045-444f-4f086080b593@gmail.com> (raw)
In-Reply-To: <87czhw2mak.fsf@kyleam.com>
On 05/04/2022 11:20, Kyle Meyer wrote:
> Max Nikulin writes:
>
>> Emacs copy of Org changed the way of calling `encode-time' as a result
>> interpretation of last nils returned by `org-parse-string' altered from
>> ignored to "no DST".
>>
> My suggestion:
>
> 1. Send a report to bug-gnu-emacs@gnu.org describing the issue. Ask
> that Paul revert those changes.
>
> I can do this at some point this week.
Ignacio, have you tried recent emacs master branch? Paul reverted most
of his changed, see
8ef37913d Paul Eggert 2022-04-06 07:48:05
Port Org encode-time usage back to Emacs 25
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=54731
> 2. Audit and update the call sites on our side, along with some
> compatibility layer.
>
> The first isn't necessary, but it avoids the problem living in the Emacs
> master branch until the updated Org code base (main branch) is synced
> with it (which hasn't started yet).
next prev parent reply other threads:[~2022-04-22 15:48 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 ` [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/)] Max Nikulin
2022-03-31 14:11 ` 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 [this message]
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=e10fefb2-5ffd-6045-444f-4f086080b593@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ignaciocasso@hotmail.com \
--cc=kyle@kyleam.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
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).