unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43407@debbugs.gnu.org
Subject: bug#43407: 26.3; Please index Escape key (<ESC>) in manuals
Date: Wed, 16 Sep 2020 17:14:41 +0000 (UTC)	[thread overview]
Message-ID: <651d847a-d774-4c32-81bc-2a92ba46a85a@default> (raw)
In-Reply-To: <83een17knf.fsf@gnu.org>

> https://urldefense.com/v3/__https://emacs.stackexchange.com/q/60645/105__;!!G
> qivPVa7Brio!LN2r8M2IuqhOZUpWhWjcCRvPsbHvIkEwniDaMZr5orhuv7dAavkTfqLjbzFkrBKr$
> >
> > It should be made easy to find info about the relation between the Meta
> > modifier key and the Escape prefix key.
> 
> My reading of that question is that this user was confused and thought
> incorrectly that he needed the Escape key, where he really needed the
> Meta key.  So having that key in the index would not have helped him,
> perhaps even confuse him more.

No, I think he was trying to use the Escape key,
but didn't understand that it's a prefix key.

But it's not necessary to refer to that question
or what its correct interpretation is.

The request is to index coverage of the Escape
key, that is, places where we talk about <ESC>.

It's not obvious that you need to ask `i' about
<ESC> and not (alternatively) about the "Escape" key.

There should be an entry "Escape key (<ESC>)"
or similar.

> I've reviewed the places where we mention the ESC key in the manual,
> and I don't see there anything worth indexing under "Escape".  Sorry.

Too bad.  That's what some users (including me, in
this context, even though I know about <ESC>) will
look for, to find info about the key Emacs calls
<ESC>.





  reply	other threads:[~2020-09-16 17:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 19:45 bug#43407: 26.3; Please index Escape key (<ESC>) in manuals Drew Adams
2020-09-16 16:26 ` Eli Zaretskii
2020-09-16 17:14   ` Drew Adams [this message]
2021-06-12 12:20   ` 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=651d847a-d774-4c32-81bc-2a92ba46a85a@default \
    --to=drew.adams@oracle.com \
    --cc=43407@debbugs.gnu.org \
    --cc=eliz@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.
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).