From: Tim Cross <theophilusx@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: Kyle Meyer <kyle@kyleam.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, 01 Apr 2022 08:37:47 +1100 [thread overview]
Message-ID: <87y20pol49.fsf@gmail.com> (raw)
In-Reply-To: <20e6f6ec-de72-fcdf-87a6-717efec931d1@gmail.com>
Max Nikulin <manikulin@gmail.com> writes:
> New calling convention for `encode-time' exists since emacs-27.1, so it is
> incompatible with yet supported emacs-26. It is unfortunate that sources in Org
> and in Emacs repository diverged, but I am unsure if it reasonable to introduce
> a new compatibility wrapper. Emacs developer may be unhappy if the change will
> be reverted to way deprecated way to call `encode-time'. For almost a year I am
> reading messages here that Emacs-28 is about to be released, so Emacs-26 is
> almost unsupported in Org.
>
I don' think that is correct. The policy is to support the previous 2
major versions, which means when Emacs 28 is released, org will need to
support both 27.x and 26.x. It will likely be necessary to have a
compatibility layer for 26.x given the changes.
next prev parent reply other threads:[~2022-03-31 21:42 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 [this message]
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=87y20pol49.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.com \
--cc=manikulin@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
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).