From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Matt Armstrong Newsgroups: gmane.emacs.devel Subject: Re: Current mode command discovery Date: Wed, 17 Feb 2021 14:26:43 -0800 Message-ID: References: <87blci35r2.fsf@gnus.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34453"; mail-complaints-to="usenet@ciao.gmane.io" Cc: =?utf-8?Q?=C3=93scar?= Fuentes , emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Feb 17 23:29:03 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lCVJd-0008of-UQ for ged-emacs-devel@m.gmane-mx.org; Wed, 17 Feb 2021 23:29:01 +0100 Original-Received: from localhost ([::1]:46740 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCVJd-0000eL-0c for ged-emacs-devel@m.gmane-mx.org; Wed, 17 Feb 2021 17:29:01 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34732) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCVHb-0007J8-VA for emacs-devel@gnu.org; Wed, 17 Feb 2021 17:26:57 -0500 Original-Received: from relay8-d.mail.gandi.net ([217.70.183.201]:42431) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCVHX-00006M-94 for emacs-devel@gnu.org; Wed, 17 Feb 2021 17:26:55 -0500 X-Originating-IP: 24.113.169.116 Original-Received: from matts-mbp-2016.lan (24-113-169-116.wavecable.com [24.113.169.116]) (Authenticated sender: matt@rfc20.org) by relay8-d.mail.gandi.net (Postfix) with ESMTPSA id 9E8731BF204; Wed, 17 Feb 2021 22:26:46 +0000 (UTC) In-Reply-To: <87blci35r2.fsf@gnus.org> Received-SPF: pass client-ip=217.70.183.201; envelope-from=matt@rfc20.org; helo=relay8-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:265102 Archived-At: --=-=-= Content-Type: text/plain Lars Ingebrigtsen writes: >> Could the (declare (modes ...)) and the new (interactive ... modes) >> be unified? I understand that they do different things today, but >> they're both called "modes" and the difference is pretty subtle. If >> they stay separate, perhaps rename to (declare (completion-modes >> ...))? > > I think I've argued enough against "(declare (modes" as the only > tagging mechanism now? I was just confused. I didn't realize they were the same thing. Your recent commit to commands.texi fixed my conception, thanks. P.S. typo in that commit, fixup patch attached. --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=0001-doc-lispref-commands.texi-Command-Modes-Fix-typo.patch Content-Description: fix typo >From 470910f58ffb151cd5221dbe3b30dc16a59b2063 Mon Sep 17 00:00:00 2001 From: Matt Armstrong Date: Wed, 17 Feb 2021 14:23:23 -0800 Subject: [PATCH] * doc/lispref/commands.texi (Command Modes): Fix typo. --- doc/lispref/commands.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi index 85376cc459..e171c3e168 100644 --- a/doc/lispref/commands.texi +++ b/doc/lispref/commands.texi @@ -597,8 +597,8 @@ Command Modes @subsection Specifying Modes For Commands Many commands in Emacs are general, and not tied to any specific mode. -For instance, @kbd{M-x kill-region} can be used pretty in pretty much -any mode that has editable text, and commands that display information +For instance, @kbd{M-x kill-region} can be used in pretty much any +mode that has editable text, and commands that display information (like @kbd{M-x list-buffers}) can be used in pretty much any context. Many other commands, however, are specifically tied to a mode, and -- 2.30.0 --=-=-=--