From: Eli Zaretskii <eliz@gnu.org>
To: Allen Li <vianchielfaura@gmail.com>
Cc: 25747@debbugs.gnu.org
Subject: bug#25747: 25.1.91; hideshow binding C-c @ C-h overrides help
Date: Thu, 16 Feb 2017 18:11:06 +0200 [thread overview]
Message-ID: <83vasaxgit.fsf@gnu.org> (raw)
In-Reply-To: <CAJr1M6euwX5MEo8tq7TNrDB0LUSzu9V3x9=JYqzYJjCCoFA=qQ@mail.gmail.com> (message from Allen Li on Thu, 16 Feb 2017 00:54:34 -0800)
> From: Allen Li <vianchielfaura@gmail.com>
> Date: Thu, 16 Feb 2017 00:54:34 -0800
> Cc: 25747@debbugs.gnu.org
>
> You can get a list of subcommands for a particular prefix key by
> typing C-h, ?, or F1 (describe-prefix-bindings) after the prefix
> key. (There are a few prefix keys for which not all of these keys
> work—those that provide their own bindings for that key. One of
> these prefix keys is ESC, because ESC C-h is actually C-M-h,
> which marks a defun. However, ESC F1 and ESC ? work fine.)
>
> I guess this is working as intended, then?
I don't know, it could be.
> I was thinking of the recommendation in the style guide, which I
> have read many times more than the manual:
>
> Don’t bind C-h following any prefix character (including
> C-c). If you don’t bind C-h, it is automatically available as
> a help character for listing the subcommands of the prefix
> character.
Perhaps we should make that somewhat softer, e.g. "We don't recommend
binding C-h ... if it can be avoided.." or somesuch.
next prev parent reply other threads:[~2017-02-16 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 22:30 bug#25747: 25.1.91; hideshow binding C-c @ C-h overrides help Allen Li
2017-02-16 5:57 ` Eli Zaretskii
2017-02-16 8:54 ` Allen Li
2017-02-16 16:11 ` Eli Zaretskii [this message]
2020-11-15 1:14 ` Stefan Kangas
2020-11-15 1:47 ` Drew Adams
2021-12-01 19:18 ` Lars Ingebrigtsen
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=83vasaxgit.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25747@debbugs.gnu.org \
--cc=vianchielfaura@gmail.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).