unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Aaron S. Hawley" <aaron.s.hawley@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs manual: correct @code to @kbd
Date: Mon, 08 Jun 2009 23:01:52 -0400	[thread overview]
Message-ID: <E1MDray-0005Fa-A2@fencepost.gnu.org> (raw)
In-Reply-To: <aea22dab0906081158v4e415158vc4d83da28f828f08@mail.gmail.com> (aaron.s.hawley@gmail.com)

> Date: Mon, 8 Jun 2009 14:58:52 -0400
> From: "Aaron S. Hawley" <aaron.s.hawley@gmail.com>
> 
> I found a dozen places in the Emacs manual where the markup should be
> @kbd and not @code.
> 
> Here's a patch.

Thanks.

However, some of your corrections are wrong.  For example, this:

> --- doc/emacs/custom.texi	4 Jun 2009 03:13:28 -0000	1.22
> +++ doc/emacs/custom.texi	8 Jun 2009 18:49:57 -0000
> @@ -1706,7 +1706,7 @@
>  @end example
> 
>    When the key sequence includes function keys or mouse button events,
> -or non-@acronym{ASCII} characters such as @code{C-=} or @code{H-a},
> +or non-@acronym{ASCII} characters such as @kbd{C-=} or @kbd{H-a},

Since this talks about _characters_, not keystrokes, @kdb is
inappropriate here, I think.

> -the current alternative with a special color; type @code{C-@key{SPC}}
> +the current alternative with a special color; type @kbd{C-SPC}

This should be @kbd{C-@key{SPC}}, because we don't want "SPC to be
confused for the 3 characters S P C.

Thanks again for working on this.




  reply	other threads:[~2009-06-09  3:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 18:58 Emacs manual: correct @code to @kbd Aaron S. Hawley
2009-06-09  3:01 ` Eli Zaretskii [this message]
2009-06-09 12:10   ` Aaron S. Hawley
2009-06-10  2:39     ` Stephen J. Turnbull
2009-06-10  2:33   ` Richard Stallman
2009-06-10 22:03   ` Stefan Monnier

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=E1MDray-0005Fa-A2@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=aaron.s.hawley@gmail.com \
    --cc=emacs-devel@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).