From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: rcirc manual Date: Mon, 16 Jan 2006 06:26:30 +0200 Message-ID: References: <200601152223.k0FMNj227346@f7.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1137385613 17467 80.91.229.2 (16 Jan 2006 04:26:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 16 Jan 2006 04:26:53 +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 Mon Jan 16 05:26:50 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 1EyLx9-0004ok-CT for ged-emacs-devel@m.gmane.org; Mon, 16 Jan 2006 05:26:47 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EyLzP-00069B-U3 for ged-emacs-devel@m.gmane.org; Sun, 15 Jan 2006 23:29:07 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EyLzG-00068u-W8 for emacs-devel@gnu.org; Sun, 15 Jan 2006 23:28:59 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EyLzF-00068Y-1E for emacs-devel@gnu.org; Sun, 15 Jan 2006 23:28:58 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EyLzE-00068U-LO for emacs-devel@gnu.org; Sun, 15 Jan 2006 23:28:56 -0500 Original-Received: from [192.114.186.66] (helo=romy.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EyM2f-0005Id-Ms; Sun, 15 Jan 2006 23:32:29 -0500 Original-Received: from HOME-C4E4A596F7 (IGLD-83-130-244-95.inter.net.il [83.130.244.95]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id DJM24035 (AUTH halo1); Mon, 16 Jan 2006 06:26:30 +0200 (IST) Original-To: karl@freefriends.org (Karl Berry) In-reply-to: <200601152223.k0FMNj227346@f7.net> (karl@freefriends.org) 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:49160 Archived-At: > Date: Sun, 15 Jan 2006 16:23:45 -0600 > From: karl@freefriends.org (Karl Berry) > Cc: rms@gnu.org, bob@rattlesnake.com, emacs-devel@gnu.org > > @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. > > [...] This still doesn't spell out what I think it should: that @key is for keys whose names are more than 1 character long. And the reason for that is to avoid the user confusion, since @kbd{RET} _could_ be interpreted as @kbd{R E T}. There's no such confusion in the single-character key case.