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: Thu, 09 Jun 2022 09:21:40 -0400	[thread overview]
Message-ID: <lz8rq69dln.fsf@3c22fb11fdab.ant.amazon.com> (raw)
In-Reply-To: <87h74u86t9.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 09 Jun 2022 12:33:38 +0200")

> * Lars Ingebrigtsen <ynefv@tahf.bet> [2022-06-09 12:33:38 +0200]:
>
> Sam Steingold <sds@gnu.org> writes:
>
>>> 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 ;-)
>
> I rather think that it's not a very useful thing, though.  As proposed,
> the `Z n' command would do the same as `c' followed by `n'.  And that's
> easier to type, so why not just type that instead?

1. In my case, it will be "c n n" (ISTR that the first "n" says "no next
   unread article" or something like that, and only the second goes to
   the next group - there might be an option that I set 15 years ago
   that does it) - but that hardly matters.

2. Going to the next group using "Z n" works in all other groups, why
   not here in digest?

At any rate, arguing about it is counterproductive.
No is no, let us move on.

Thank you for your explanations!

-- 
Sam Steingold (https://youtube.com/channel/UCiW5WB6K4Fx-NhhtZscW7Og) on darwin Ns 10.3.2113
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://honestreporting.com https://mideasttruth.com https://www.memritv.org
He who laughs last did not get the joke.





  reply	other threads:[~2022-06-09 13:21 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
2022-06-09 10:33     ` Lars Ingebrigtsen
2022-06-09 13:21       ` Sam Steingold [this message]
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=lz8rq69dln.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).