From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: What were the Emacs versions with dates limited to 1970 .. 2037 year range?
Date: Sun, 12 Jun 2022 12:22:48 +0300 [thread overview]
Message-ID: <83wndmutg7.fsf@gnu.org> (raw)
In-Reply-To: <8735gaqm6i.fsf@localhost> (message from Ihor Radchenko on Sun, 12 Jun 2022 17:13:25 +0800)
> From: Ihor Radchenko <yantar92@gmail.com>
> Date: Sun, 12 Jun 2022 17:13:25 +0800
>
> Org mode currently supports an old workaround for 32-bit year range
> limitation:
>
> org-read-date-force-compatible-dates docstring:
>
> > Should date/time prompt force dates that are guaranteed to work in Emacs?
> >
> > Depending on the system Emacs is running on, certain dates cannot
> > be represented with the type used internally to represent time.
> > Dates between 1970-1-1 and 2038-1-1 can always be represented
> > correctly. Some systems allow for earlier dates, some for later,
> > some for both. One way to find out is to insert any date into an
> > Org buffer, putting the cursor on the year and hitting S-up and
> > S-down to test the range.
>
> The workaround has been introduced about 11 years ago.
>
> Could anyone tell if this issue is still present in Emacs 25 or newer or
> maybe on some OS?
Any 32-bit build of Emacs is potentially prone to this problem,
depending on what time-related APIs it is using. If time_t is a
32-bit type, this problem will still exist.
next prev parent reply other threads:[~2022-06-12 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 9:13 What were the Emacs versions with dates limited to 1970 .. 2037 year range? Ihor Radchenko
2022-06-12 9:22 ` Eli Zaretskii [this message]
2022-06-12 9:51 ` Ihor Radchenko
2022-06-12 10:00 ` Eli Zaretskii
2022-06-12 14:21 ` Stefan Monnier
2022-06-12 14:41 ` Eli Zaretskii
2022-06-13 0:30 ` Po Lu
2022-06-13 2:37 ` Eli Zaretskii
2022-06-13 9:25 ` Stefan Kangas
2022-06-13 11:49 ` Eli Zaretskii
2022-06-13 13:19 ` Stefan Monnier
2022-06-13 13:29 ` Eli Zaretskii
2022-06-13 16:40 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wndmutg7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yantar92@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.