From: "Drew Adams" <drew.adams@oracle.com>
To: <bugs@gnus.org>
Cc: 3801@debbugs.gnu.org
Subject: bug#3801: 23.0.96; Emacs manual: add index entry for "notation, keys" or "key notation"
Date: Tue, 12 Jul 2011 09:27:55 -0700 [thread overview]
Message-ID: <95D5526B48D74870BE3EFD9A49582EE2@us.oracle.com> (raw)
In-Reply-To: <m3wrfnjze5.fsf@quimbies.gnus.org>
> > I tried looking for the place in the Emacs manual where the notation
> > for key sequences (the one used in the doc) is described. I tried
> > `notation' and found there was only one match:
> > `gdb-use-colon-colon-notation'. Users should be able to find this by
> > looking for terms such as `notation' and `conventions'.
>
> In what circumstances does Emacs talk about notations for key
> sequences?
The conventions used in the doc should be described. They are, for the Elisp
manual: see node `Conventions' and its subnodes. See how detailed those nodes
are, and how well they explain the notations used in the Elisp manual.
The Emacs manual should also describe the notations it uses. In particular,
key-sequence notation.
There should be a description of how the manual indicates key sequences,
including for different kinds of keys (e.g. angle-bracket notation vs no angle
brackets).
If there is not yet such a desciption, it should be added. And then it should
be indexed (this bug report).
next prev parent reply other threads:[~2011-07-12 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 21:19 bug#3801: 23.0.96; Emacs manual: add index entry for "notation, keys" or "key notation" Drew Adams
2011-07-12 15:24 ` Lars Magne Ingebrigtsen
2011-07-12 16:27 ` Drew Adams [this message]
2011-07-12 17:51 ` Eli Zaretskii
2011-07-12 19:35 ` Lars Magne Ingebrigtsen
2011-07-12 20:25 ` Drew Adams
2011-07-12 20:25 ` Drew Adams
2011-07-12 20:33 ` Eli Zaretskii
2011-07-12 21:16 ` Drew Adams
2011-07-13 2:53 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=95D5526B48D74870BE3EFD9A49582EE2@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=3801@debbugs.gnu.org \
--cc=bugs@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.