From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: info-gnus-english@gnu.org
Subject: Re: gnus-article-summary-next
Date: Fri, 16 Dec 2022 14:52:30 +0000 [thread overview]
Message-ID: <87bko3e6z5.fsf@ucl.ac.uk> (raw)
In-Reply-To: <86zgbnn2r4.fsf@csic.es>
On Friday, 16 Dec 2022 at 09:58, Juan José García-Ripoll wrote:
> They are not consistent with each other, right?
Yes, not consistent and, more to the point, they are not the defaults.
You (or something in your configuration) is changing these.
Generally, n/p go to next/prev unread and N/P next/prev whether read or
not.
--
Eric S Fraga via gnus (Emacs 30.0.50 2022-12-02) on Debian 11.5
prev parent reply other threads:[~2022-12-16 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 9:45 gnus-article-summary-next Juan José García-Ripoll
2022-12-15 10:45 ` gnus-article-summary-next Emanuel Berg
2022-12-15 12:39 ` gnus-article-summary-next Eric S Fraga
2022-12-16 8:58 ` gnus-article-summary-next Juan José García-Ripoll
2022-12-16 14:52 ` Eric S Fraga [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bko3e6z5.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).