From: karl@freefriends.org (Karl Berry)
Cc: bob@rattlesnake.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: rcirc manual
Date: Sun, 15 Jan 2006 16:23:45 -0600 [thread overview]
Message-ID: <200601152223.k0FMNj227346@f7.net> (raw)
In-Reply-To: <uvewl5l2p.fsf@gnu.org>
In any case, the explanation in the Texinfo manual should be more
clear on this, IMHO. It should explain what keys are suitable for
@key, and why.
Here is what the `key' node says now. Documentation improvements are
always welcome, of course. I'm not too clear myself on exactly how to
make it better.
@node key
@subsection @code{@@key}@{@var{key-name}@}
@findex key
Use the @code{@@key} command for the conventional name for a key on a
keyboard, as in:
@example
@@key@{RET@}
@end example
You can use the @code{@@key} command within the argument of an
@code{@@kbd} command when the sequence of characters to be typed
includes one or more keys that are described by name.
[...]
There are subtleties to handling words like `meta' or `ctrl' that are
names of modifier keys. When mentioning a character in which the
modifier key is used, such as @kbd{Meta-a}, use the @code{@@kbd} command
alone; do not use the @code{@@key} command; but when you are referring
to the modifier key in isolation, use the @code{@@key} command. For
example, write @samp{@@kbd@{Meta-a@}} to produce @kbd{Meta-a} and
@samp{@@key@{META@}} to produce @key{META}.
next prev parent reply other threads:[~2006-01-15 22:23 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
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 [this message]
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=200601152223.k0FMNj227346@f7.net \
--to=karl@freefriends.org \
--cc=bob@rattlesnake.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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).