unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: karl@freefriends.org, emacs-devel@gnu.org
Subject: Re: rcirc manual
Date: Sat, 14 Jan 2006 17:47:34 +0000 (UTC)	[thread overview]
Message-ID: <m1ExpV0-0004R8C@rattlesnake.com> (raw)
In-Reply-To: <uacdy26d0.fsf@gnu.org> (message from Eli Zaretskii on Sat, 14 Jan 2006 17:10:03 +0200)

    AFAIU, @key{M-x} is wrong, since there's no key labeled "M-x".

Ah ... I think of this as pressing the Meta key and the `X' key
simultaneously.  Thus, the Texinfo Manual does talk of these
instances:

    (texinfo)key 

        Use the `@key' command for the conventional name for a key on
        a keyboard ...

However, this terminology may be confusing.  Some people refer to a
`keychord' when they speak of C-x or M-C-f.  Perhaps the Texinfo node
should be changed to `for a key or keychord' rather than simply `for a
key'.

However, the word `key' does have an established meaning.  When I run
`describe-bindings' in this *mail* buffer, `C-x' is labeled `key' and
`Prefix Command' is labeled `binding'.

Perhaps the phrase `keychord' should be used occasionally, as in
(eintr)Note for Novices

    Sometimes a combination like this is called a keychord, since it
    is similar to the way you play a chord on a piano.

But it seems to me that most of the time, the Texinfo Manual should
follow the regular meaning of `key'.

-- 
    Robert J. Chassell                         
    bob@rattlesnake.com                         GnuPG Key ID: 004B4AC8
    http://www.rattlesnake.com                  http://www.teak.cc

  reply	other threads:[~2006-01-14 17:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 17:47 rcirc manual Björn Lindström
2006-01-13 11:21 ` Eli Zaretskii
2006-01-13 14:10   ` Alex Schroeder
2006-01-13 15:08     ` Eli Zaretskii
2006-01-13 15:11       ` Alex Schroeder
2006-01-14 16:14     ` Richard M. Stallman
2006-01-13 15:48   ` Thien-Thi Nguyen
2006-01-13 15:55     ` Eli Zaretskii
2006-01-13 22:16       ` Robert J. Chassell
2006-01-14  8:51         ` Eli Zaretskii
2006-01-14 12:20           ` Robert J. Chassell
2006-01-14 15:10             ` Eli Zaretskii
2006-01-14 17:47               ` Robert J. Chassell [this message]
2006-01-15 23:07                 ` Richard M. Stallman
2006-01-15  7:49           ` Richard M. Stallman
2006-01-15 19:48             ` Eli Zaretskii
2006-01-15 22:23               ` Karl Berry
2006-01-16  4:26                 ` Eli Zaretskii
2006-01-15 22:29               ` Robert J. Chassell
2006-01-16 14:15               ` Richard M. Stallman
2006-01-21 13:01                 ` Eli Zaretskii
2006-01-23  0:09   ` Alex Schroeder
2006-01-27 18:48     ` 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

  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=m1ExpV0-0004R8C@rattlesnake.com \
    --to=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    --cc=karl@freefriends.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).