Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: gnus-article-summary-next
Date: Fri, 16 Dec 2022 09:58:55 +0100	[thread overview]
Message-ID: <86zgbnn2r4.fsf@csic.es> (raw)
In-Reply-To: <87k02sx2mw.fsf@ucl.ac.uk>

Ok, I think I get my confusion

p -> gnus-summary-prev-article
P -> gnus-summary-next-unread-article

n -> gnus-summary-next-article
N -> gnus-summary-prev-unread-article

They are not consistent with each other, right?

Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Thursday, 15 Dec 2022 at 10:45, Juan José García-Ripoll wrote:
>> Hi,
>>
>> a brief question. Has anything changed in Emacs 28? I am used to Shift-p
>> and Shift-n to navigate the emails but now those keys act in reversed
>> order: previous means later date and next means earlier date, moving
>> downwards and upwards in a sorted summary buffer. This seems to be
>> contrary to what I did not too long ago.
>
> What are the keys actually bound to?  For me, in a summary buffer, I
> have
>
> N: gnus-summary-next-article
> P: gnus-summary-prev-article
>
> Whether that is next/prev date obviously depends on the sorting in your
> buffer but for me they move point down (N) or up (P), as I would expect.

-- 
Juan José García Ripoll
http://juanjose.garciaripoll.com
http://quinfog.hbar.es



  reply	other threads:[~2022-12-16  8:59 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   ` Juan José García-Ripoll [this message]
2022-12-16 14:52     ` gnus-article-summary-next Eric S Fraga

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=86zgbnn2r4.fsf@csic.es \
    --to=juanjose.garciaripoll@gmail.com \
    --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).