From: Emanuel Berg <incal@dataswamp.org>
To: info-gnus-english@gnu.org
Subject: Re: gnus-article-summary-next
Date: Thu, 15 Dec 2022 11:45:43 +0100 [thread overview]
Message-ID: <871qp12be0.fsf@dataswamp.org> (raw)
In-Reply-To: <861qp1f1ac.fsf@csic.es>
Juan José García-Ripoll wrote:
> 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.
Uhm, later/earlier date ... ?
But p should be up, n down.
Compare C-n for `next-line' and C-p for `previous-line'.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-12-15 10:46 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 ` Emanuel Berg [this message]
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 ` 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=871qp12be0.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--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).