From: Stefan Kangas <stefankangas@gmail.com>
To: Mike Kupfer <kupfer@rawbw.com>, 72204@debbugs.gnu.org
Cc: "Eric Abrahamsen" <eric@ericabrahamsen.net>,
"Łukasz Stelmach" <stlman@poczta.fm>
Subject: bug#72204: Acknowledgement (30.0.60; missing NEWS entry for gnus-summary-limit-to-age change)
Date: Sun, 21 Jul 2024 12:30:10 -0700 [thread overview]
Message-ID: <CADwFkmmjt3R1m8K3sdfNqNLfp4kePheHbAcE3=h_zzfLT2hyXw@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmn7+s-m_Oo990Y01pyqQV4hWd_jSTeyGLGbuv8hC1Xu2A@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
> Mike Kupfer <kupfer@rawbw.com> writes:
>
>> Oh, another change to gnus-summary-limit-to-age that's probably worth
>> calling out: it looks like "less than 1 day old" now means "since
>> midnight". In Emacs 29, it meant "less than 24 hours old".
>
> I'd recommend opening a new bug report for this issue.
BTW, I suppose this is due to:
commit 0dd7e6e3aeac1ab0a03f2ed2ad108deecde82447
Author: Eric Abrahamsen <eric@ericabrahamsen.net>
Date: Sat Sep 23 16:31:10 2023 -0700
Have gnus-summary-limit-to-age operate on calendar days
Reported and patched by Łukasz Stelmach <stlman@poczta.fm>.
* lisp/gnus/gnus-sum.el (gnus-summary-limit-to-age): Rather than
24-hour blocks. Also use `read-number', and drop the confusing option
to reverse younger/older both with the prefix argument and with a
negative number.
next prev parent reply other threads:[~2024-07-21 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 5:42 bug#72204: 30.0.60; missing NEWS entry for gnus-summary-limit-to-age change Mike Kupfer
[not found] ` <handler.72204.B.17214541487223.ack@debbugs.gnu.org>
2024-07-20 15:11 ` bug#72204: Acknowledgement (30.0.60; missing NEWS entry for gnus-summary-limit-to-age change) Mike Kupfer
2024-07-21 19:28 ` Stefan Kangas
2024-07-21 19:30 ` Stefan Kangas [this message]
2024-07-25 7:41 ` Eli Zaretskii
2024-07-21 19:34 ` bug#72204: 30.0.60; missing NEWS entry for gnus-summary-limit-to-age change Stefan Kangas
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='CADwFkmmjt3R1m8K3sdfNqNLfp4kePheHbAcE3=h_zzfLT2hyXw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=72204@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=kupfer@rawbw.com \
--cc=stlman@poczta.fm \
/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).