From: Nick Dokos <ndokos@gmail.com>
To: 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: Mon, 20 Mar 2023 23:24:19 -0400 [thread overview]
Message-ID: <87ttyeg524.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: e6ea5916-7f23-b452-a08d-f1e7a7dd1efd@pobox.com
Do `C-h v org-read-date-force-compatible-dates` and read the doc
string of the variable. You can customize the variable and set it to
`nil' which will give you a much wider range of dates to choose from
*assuming that your Emacs is compiled for and runs on a system that
can deal with such dates* (this is related to the "2038" problem[1] where
32-bit (signed) timestamps will not be enough to count the number of seconds
since the "beginning of time" (that's 1970-01-01 at least as far as
Unix is concerned :-))
This is a difficult compatibility problem which is being worked on on
many fronts and I think there have been discussions about it on this
list.
But read the doc string, experiment on your system and see if you can
live with the consequences of choosing the "other" value for the
variable.
[1] https://en.wikipedia.org/wiki/Year_2038_problem
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
next prev parent reply other threads:[~2023-03-21 3:25 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 [this message]
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
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=87ttyeg524.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.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).