From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: karl@freefriends.org (Karl Berry) Newsgroups: gmane.emacs.devel Subject: Re: rcirc manual Date: Sun, 15 Jan 2006 16:23:45 -0600 Message-ID: <200601152223.k0FMNj227346@f7.net> References: NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1137365701 724 80.91.229.2 (15 Jan 2006 22:55:01 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 15 Jan 2006 22:55:01 +0000 (UTC) Cc: bob@rattlesnake.com, rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 15 23:54:57 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EyGll-0000oa-O1 for ged-emacs-devel@m.gmane.org; Sun, 15 Jan 2006 23:54:41 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EyGo0-0007Xd-Tf for ged-emacs-devel@m.gmane.org; Sun, 15 Jan 2006 17:57:00 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EyGK8-0006WV-4c for emacs-devel@gnu.org; Sun, 15 Jan 2006 17:26:08 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EyGK7-0006WG-NY for emacs-devel@gnu.org; Sun, 15 Jan 2006 17:26:07 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EyGK7-0006WD-L8 for emacs-devel@gnu.org; Sun, 15 Jan 2006 17:26:07 -0500 Original-Received: from [64.34.169.74] (helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EyGNV-0004Ej-AF; Sun, 15 Jan 2006 17:29:37 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: rms@gnu.org Original-Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id k0FMNj227346; Sun, 15 Jan 2006 16:23:45 -0600 Original-To: eliz@gnu.org In-Reply-To: X-Mailman-Approved-At: Sun, 15 Jan 2006 17:56:51 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:49142 Archived-At: 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}.