all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lars Magne Ingebrigtsen'" <larsi@gnus.org>, <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 13:25:08 -0700	[thread overview]
Message-ID: <643171B994DD48F486E3C007543F7F5C@us.oracle.com> (raw)
In-Reply-To: <m3ei1vi96y.fsf@quimbies.gnus.org>

> > I think you are looking for "User Input" and "Keys" nodes.
> 
> Yes, I can't remember "notation" as a word people use for keys.
> 
> Closing this bug report.

It's not about anyone using "notation" as a word for keys.

It's about being able to easily locate the notational conventions we use in our
manuals.

As I said, contrast the case of the Elisp manual.

In the Elisp manual too we should probably add "notational conventions" as an
index entry, in addition to the existing entry "typographical conventions"
(which takes you to node `Some Terms', a subnode of node `Conventions').

But in that manual (Elisp) things are much clearer because of this top-level
table of contents entry:

 `Conventions' - How the manual is formatted

There is no similar organization for the Emacs manual, and consequently it is
more difficult to find a presentation of "how the manual is formatted".






  reply	other threads:[~2011-07-12 20:25 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
2011-07-12 17:51     ` Eli Zaretskii
2011-07-12 19:35       ` Lars Magne Ingebrigtsen
2011-07-12 20:25         ` Drew Adams [this message]
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=643171B994DD48F486E3C007543F7F5C@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=3801@debbugs.gnu.org \
    --cc=larsi@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.