From: Ihor Radchenko <yantar92@posteo.net>
To: Daniel Ortmann <dortmann31415@pobox.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] incorrect result with C-c ! to correct (complete) a date [9.7-pre (release_9.6.1-306-ga645a6 @ /home/d/src/git-org-mode/lisp/)]
Date: Wed, 22 Mar 2023 11:47:51 +0000 [thread overview]
Message-ID: <87v8itnh20.fsf@localhost> (raw)
In-Reply-To: <e6ea5916-7f23-b452-a08d-f1e7a7dd1efd@pobox.com>
Daniel Ortmann <dortmann31415@pobox.com> writes:
> Starting with this manually-typed birthday date:
> [1960-10-16]
> Use the arrows to move to the text.
> Now press C-c ! and then ENTER
As documented in 8.2.1 The date/time prompt section of Org manual:
Not all dates can be represented in a given Emacs implementation. By
default Org mode forces dates into the compatibility range 1970–2037
which works on all Emacs implementations. If you want to use dates
outside of this range, read the docstring of the variable
‘org-read-date-force-compatible-dates’.
Emacs implementations that won't be able to handle out-of-range dates
are 32-bit Emacs versions. See
https://yhetil.org/emacs-devel/8735gaqm6i.fsf@localhost
If we can assume that most of Emacs versions are 32-bit, we can flip the
default value of `org-read-date-force-compatible-dates' to nil.
The default `t' value has been set 12 years ago, when 32-bit systems
were much more common.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2023-03-22 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 1:56 [BUG] incorrect result with C-c ! to correct (complete) a date [9.7-pre (release_9.6.1-306-ga645a6 @ /home/d/src/git-org-mode/lisp/)] Daniel Ortmann
2023-03-21 3:24 ` Nick Dokos
2023-03-21 14:00 ` Max Nikulin
2023-03-22 5:34 ` Daniel Ortmann
2023-03-22 12:04 ` Max Nikulin
2023-03-22 11:47 ` Ihor Radchenko [this message]
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=87v8itnh20.fsf@localhost \
--to=yantar92@posteo.net \
--cc=dortmann31415@pobox.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).