From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ihor Radchenko <yantar92@posteo.net>, 65450@debbugs.gnu.org
Subject: bug#65450: 29.0.92; org-mode agenda date entry with calendar does not support years beyond 2037
Date: Wed, 23 Aug 2023 13:47:24 +0200 [thread overview]
Message-ID: <878ra2x9ly.fsf@web.de> (raw)
In-Reply-To: <83edjurnlq.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: 65450@debbugs.gnu.org
>> From: Ihor Radchenko <yantar92@posteo.net>
>> Date: Wed, 23 Aug 2023 06:40:39 +0000
>>
>> "Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
>>
>> > This is kind of suspicious, because 2038 is when the year 2038 problem
>> > looms. Is Emacs vulnerable?
>>
>> See `org-read-date-force-compatible-dates'. Emacs is vulnerable on some
>> platforms, AFAIR. Also, see https://yhetil.org/emacs-devel/8735gaqm6i.fsf@localhost/
Thank you for the reference!
>> After the last discussion I did not see it safe to flip the default
>> value of `org-read-date-force-compatible-dates'.
>
> So this doesn't seem to be an Emacs bug, or a bug at all, but rather a
> feature of Org? If so, we should close this bug, I guess?
Can Emacs add a fallback mechanism so org can stop working around the
issue?
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2023-08-23 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 8:35 bug#65450: 29.0.92; org-mode agenda date entry with calendar does not support years beyond 2037 Dr. Arne Babenhauserheide
2023-08-22 11:24 ` Eli Zaretskii
2023-08-23 6:40 ` Ihor Radchenko
2023-08-23 11:42 ` Eli Zaretskii
2023-08-23 11:47 ` Dr. Arne Babenhauserheide [this message]
2023-08-23 12:06 ` Eli Zaretskii
2023-08-23 12:25 ` Ihor Radchenko
2023-08-26 13:29 ` Stefan Kangas
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ra2x9ly.fsf@web.de \
--to=arne_bab@web.de \
--cc=65450@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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.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).