unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>, "Colin Baxter 😺" <m43cap@yandex.com>
Cc: emacs-devel@gnu.org
Subject: Re: terminal scrolling in help
Date: Mon, 13 Dec 2021 05:49:36 -0800	[thread overview]
Message-ID: <CADwFkmnnx=5EmEmQ+tGa2_Hu-zw3X0dSPuv4KvXrQmRygEXyGg@mail.gmail.com> (raw)
In-Reply-To: <83ilvsmzjg.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Colin Baxter 😺 <m43cap@yandex.com>
>> Cc:
>> Date: Mon, 13 Dec 2021 07:39:02 +0000
>>
>> 1. emacs-27.2 -nw -Q <RET>
>> 2. C-h ?
>>
>> The user is then told to use Space or Del to scroll options. This works
>> in xterm, stterm and urxvt.
>>
>> In emacs-28.0.90 (and emacs-29.0.50) the user is now told to use
>> <PageDown>, <PageUp> to scroll, neither of which work in xterm,
>> stterm or urxvt
>>
>> I am wondering why the scroll advice was changed?

Because those are more natural keys to use on graphical displays.

> How about providing a patch that adds SPC and DEL to the advice?

Can we detect that we are running in a terminal and show SPC and DEL
there, while showing <PageDown> and <PageUp> on graphical displays?



  reply	other threads:[~2021-12-13 13:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  7:39 terminal scrolling in help Colin Baxter 😺
2021-12-13 12:58 ` Eli Zaretskii
2021-12-13 13:49   ` Stefan Kangas [this message]
2021-12-13 14:27     ` Alan Mackenzie
2021-12-13 14:49       ` Stefan Kangas
2021-12-13 15:10     ` Eli Zaretskii
2021-12-13 18:12       ` Stefan Kangas
2021-12-13 18:16         ` Eli Zaretskii
2021-12-13 21:26     ` James Cloos
2021-12-13 13:52   ` Eli Zaretskii
2021-12-13 16:24     ` Colin Baxter 😺
2021-12-13 17:00 ` Yuri Khan
2021-12-13 17:34   ` Colin Baxter 😺
2021-12-13 17:50     ` Yuri Khan
2021-12-13 19:05       ` Colin Baxter 😺
2021-12-13 19:23         ` Yuri Khan
2021-12-13 20:22           ` Colin Baxter 😺
2021-12-13 20:27           ` Andreas Schwab
2021-12-13 17:08 ` Andreas Schwab

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='CADwFkmnnx=5EmEmQ+tGa2_Hu-zw3X0dSPuv4KvXrQmRygEXyGg@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=m43cap@yandex.com \
    /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).