From: Maxim Nikulin <m.a.nikulin@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Paul Eggert <eggert@cs.ucla.edu>
Cc: 55635-done@debbugs.gnu.org
Subject: bug#55635: `make-decoded-time' incorrectly sets DST to nil, it should be -1 (guess)
Date: Sat, 28 May 2022 23:31:43 +0700 [thread overview]
Message-ID: <0e506652-fb7d-5707-8247-7747ff1e53b0@gmail.com> (raw)
In-Reply-To: <87zgj23pn9.fsf@gnus.org>
On 28/05/2022 17:41, Lars Ingebrigtsen wrote:
> Paul Eggert writes:
>
>> To try to lessen the confusion I installed the attached, which fixes
>> the reported bug so I'll close the bug report. Please feel free to
>> revert if you see a problem with it (I'm just trying to save time here
>> by being bold).
>
> Thanks; I think that looks like the correct thing here.
Thank you, with the committed changes my examples work as I expect.
Paul, do you have any comment concerning the last part of the bug report?
`decoded-time-add' docstring:
> (decoded-time-add (decode-time) (make-decoded-time :month 2))
I think, it is confusing that `make-decoded-time' is used to create
timestamps *and* time intervals. They are different types, for example
sum of intervals is meaningful (despite may be ambiguous) while there is
no point to add timestamps. Daylight saving time and timezone are
something alien for intervals. Though I am unsure if it is reasonable to
mark intervals by e.g. 'time-interval symbol or to make these types
distinct by some other way.
next prev parent reply other threads:[~2022-05-28 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 14:46 bug#55635: `make-decoded-time' incorrectly sets DST to nil, it should be -1 (guess) Maxim Nikulin
2022-05-26 12:13 ` Lars Ingebrigtsen
2022-05-27 2:11 ` Paul Eggert
2022-05-27 10:40 ` Lars Ingebrigtsen
2022-05-27 19:26 ` Paul Eggert
2022-05-28 10:41 ` Lars Ingebrigtsen
2022-05-28 16:31 ` Maxim Nikulin [this message]
2022-05-28 16:53 ` Eli Zaretskii
2022-05-28 17:25 ` Paul Eggert
2022-05-29 13:10 ` Lars Ingebrigtsen
2022-05-29 22:04 ` Paul Eggert
2022-05-31 12:25 ` Maxim Nikulin
2022-06-13 21:30 ` Paul Eggert
2022-06-14 15:57 ` Maxim Nikulin
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=0e506652-fb7d-5707-8247-7747ff1e53b0@gmail.com \
--to=m.a.nikulin@gmail.com \
--cc=55635-done@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.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).