From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: emacs-devel@gnu.org
Subject: Re: Arithmetic range error
Date: Sat, 09 Feb 2019 00:44:43 +0100 [thread overview]
Message-ID: <87o97l6e1g.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2h8denz27.fsf@gmail.com> (Robert Pluim's message of "Fri, 08 Feb 2019 15:18:40 +0100")
Hello,
Robert Pluim <rpluim@gmail.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Robert Pluim <rpluim@gmail.com>
>>> Date: Fri, 08 Feb 2019 14:34:29 +0100
>>> Cc: emacs-devel@gnu.org
>>>
>>> The problem comes from org's desire to have the ctime as a single
>>> integer. Reverting the commit that changed org to use 'floor' will
>>> just result in truncation (but people might not care about that, since
>>> weʼd be dropping the high bits of the timestamp). Ideally org would
>>> handle the list form of timestamps, but thatʼs something for org
>>> developers to decide.
>>
>> Indeed, this is a matter for Org developers to handle. CC'ing Bastien
>> for that reason.
>
> Nicolas does a lot of org work as well, CC'd.
>
> Thinking about it some more, the old method already truncated the
> ctime anyway, and has done for a long time, so perhaps restoring it is
> not unwarranted.
I modified Org (master branch) so that it uses the list representation
of time values in this situation.
Thank you for the suggestion.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-02-08 23:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 10:55 Arithmetic range error Colin Baxter
2019-02-08 12:25 ` Robert Pluim
2019-02-08 13:05 ` Colin Baxter
2019-02-08 13:15 ` Robert Pluim
2019-02-08 13:19 ` Eli Zaretskii
2019-02-08 13:34 ` Robert Pluim
2019-02-08 14:04 ` Eli Zaretskii
2019-02-08 14:18 ` Robert Pluim
2019-02-08 23:44 ` Nicolas Goaziou [this message]
2019-02-09 7:02 ` Colin Baxter
2019-02-10 10:06 ` Paul Eggert
2019-02-10 12:59 ` Nicolas Goaziou
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=87o97l6e1g.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-devel@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.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).