unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam Steingold <sds@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55834@debbugs.gnu.org
Subject: bug#55834: 29.0.50; gnus: Z n in digest group does not catch up
Date: Wed, 08 Jun 2022 11:26:33 -0400	[thread overview]
Message-ID: <lzczfj9nx2.fsf@3c22fb11fdab.ant.amazon.com> (raw)
In-Reply-To: <87czfke6u8.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 07 Jun 2022 19:11:59 +0200")

> * Lars Ingebrigtsen <ynefv@tahf.bet> [2022-06-07 19:11:59 +0200]:
>
> Sam Steingold <sds@gnu.org> writes:
>
>> Expected behavior (observed until about a month ago?):
>> `Z n` should catch up the digest and move on to the parent group; if
>> there are no unread message (my case) it should also catch this one up
>> and move to the next group with unread messages, marking this group in
>> *Groups* as empty (this is the regression: it did so before, but not
>> anymore).
>
> Are you sure that it ever did this?

Well, I think so - but I could be wrong.

> So I'm wondering if you have some special code to deal with
> digests/"parent" groups?

Nope.

Please consider this bug report as an RFE ;-)

Thank you!

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.2113
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://youtube.com/channel/UCiW5WB6K4Fx-NhhtZscW7Og https://ij.org/
Hypocrisy is the Vaseline of political intercourse.





  reply	other threads:[~2022-06-08 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 16:05 bug#55834: 29.0.50; gnus: Z n in digest group does not catch up Sam Steingold
2022-06-07 17:11 ` Lars Ingebrigtsen
2022-06-08 15:26   ` Sam Steingold [this message]
2022-06-09 10:33     ` Lars Ingebrigtsen
2022-06-09 13:21       ` Sam Steingold
2022-07-11 11:21         ` Lars Ingebrigtsen

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=lzczfj9nx2.fsf@3c22fb11fdab.ant.amazon.com \
    --to=sds@gnu.org \
    --cc=55834@debbugs.gnu.org \
    --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).