unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: uzibalqa <uzibalqa@proton.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Pressing ? does not allow window scrolling through the list of info commands
Date: Fri, 07 Jul 2023 13:46:32 +0000	[thread overview]
Message-ID: <wY4cAchfAG1T1R6UAP39FUMQq6GVkwnsbgeEMwd0_SpKjuBLWt5E45e5RfJmXPTax-xkGzZb4E15xoatPvki2zvFZmqqks1jW-F-y7RkXwY=@proton.me> (raw)
In-Reply-To: <83fs5zg919.fsf@gnu.org>

------- Original Message -------
On Saturday, July 8th, 2023 at 1:12 AM, Eli Zaretskii <eliz@gnu.org> wrote:


> > Date: Fri, 07 Jul 2023 13:03:46 +0000
> > From: uzibalqa uzibalqa@proton.me
> > Cc: help-gnu-emacs@gnu.org
> > 
> > Not being able to operate upon the '?' buffer is very problematic. For instance,
> > if one wishes to increase or decrease the font size, one cannot do so because they
> > get redirected to the manual.
> 
> 
> Users who want to change their font should be already very familiar
> with how Info mode works.

Certainly not, because they could be using some premade tool.  Not being 
able to change the font with keys is unworkable for accessibility purposes.
 
> > The buffer should be made to behave as a normal buffer, using some key to get out of it.
> 
> 
> I disagree, and I already explained why.

Come up with some other method of going back to the manual.  You have a '?' tool that
nobody uses because the way to view it is worthless.  You know as I do that the workings
of the '?' tool is like nothing else, extremely weird as it always tried to get you back
to the manual rather than read the information.  Changing the font size (with key sequence)
works well for the manual.  Same ability should be extended to the '?' tool as well.






  reply	other threads:[~2023-07-07 13:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  0:37 Pressing ? does not allow window scrolling through the list of info commands uzibalqa
2023-07-07  5:31 ` Eli Zaretskii
2023-07-07  6:00   ` Yuri Khan
2023-07-07  6:38     ` Eli Zaretskii
2023-07-07 11:38       ` uzibalqa
2023-07-07 11:40         ` uzibalqa
2023-07-07 12:54           ` Eli Zaretskii
2023-07-07 13:03             ` uzibalqa
2023-07-07 13:12               ` Eli Zaretskii
2023-07-07 13:46                 ` uzibalqa [this message]
2023-07-07 15:03                   ` [External] : " Drew Adams
2023-07-07 14:58               ` Drew Adams
2023-07-07 15:04                 ` uzibalqa
2023-07-07 14:51         ` Drew Adams
2023-07-07 18:28       ` Yuri Khan
2023-07-07 19:06         ` Eli Zaretskii
2023-07-07 19:11           ` uzibalqa
2023-07-07 21:58             ` Stephen Berman
2023-07-07 19:34           ` Yuri Khan
2023-07-07 19:40             ` Eli Zaretskii
2023-07-07 19:52               ` Eli Zaretskii
2023-07-07 19:57                 ` Jean Louis
2023-07-07 20:07                 ` uzibalqa
2023-07-07 20:11               ` Yuri Khan
2023-07-07 20:19                 ` uzibalqa
2023-07-07 19:48             ` uzibalqa
2023-07-07 19:08         ` [External] : " Drew Adams
2023-07-07 19:31       ` Jean Louis
2023-07-07 11:30   ` uzibalqa
2023-07-07 12:51     ` Eli Zaretskii

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='wY4cAchfAG1T1R6UAP39FUMQq6GVkwnsbgeEMwd0_SpKjuBLWt5E45e5RfJmXPTax-xkGzZb4E15xoatPvki2zvFZmqqks1jW-F-y7RkXwY=@proton.me' \
    --to=uzibalqa@proton.me \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).