unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: karl@freefriends.org, emacs-devel@gnu.org
Subject: Re: rcirc manual
Date: Sat, 14 Jan 2006 10:51:19 +0200	[thread overview]
Message-ID: <umzhz19bs.fsf@gnu.org> (raw)
In-Reply-To: <m1ExXDb-0004EmC@rattlesnake.com> (bob@rattlesnake.com)

> Date: Fri, 13 Jan 2006 22:16:23 +0000 (UTC)
> From: "Robert J. Chassell" <bob@rattlesnake.com>
> 
>     @key{TAB} is typeset to show an image of a key on a keyboard.  I
>     think it is not the right markup in this case, because this manual
>     does not talk about keys, it talks about typing a TAB.
> 
> >From the Texinfo Manual:

Bob, I know what the Texinfo manual says about this issue, I just
think it's not 100% clear what it means in practice.  For example, you
could use either @kbd{M-@key{x}} or @kbd{M-x} (since `x' ``describes a
key by name''), but the Texinfo manual doesn't touch this dilemma.

Over the years, I formed a personal opinion about this, based on the
way @key typesets its argument in print, and that opinion was what I
wrote: @key is appropriate when talking about keys on the keyboard,
like in the Emacs manual chapter which explains the
Backspace/Delete/DEL issue or in the "Inserting Text" section that
explains the basics.  Everywhere else, with rare exceptions, I think
the effect of @key is not what you want; in particular @kbd{M-@key{x}}
looks ugly.

So, in the situation like the one which led to this discussion, if the
text is something like "press the TAB key", then @key{TAB} is the
right markup, but if the text says "you can use TAB for completion",
I'd use @kbd{TAB}.

  reply	other threads:[~2006-01-14  8:51 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 [this message]
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
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=umzhz19bs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).