From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [External] : Re: command mode-specificity [was: scratch/command 064f146 1/2: Change...] Date: Thu, 18 Feb 2021 16:37:18 +0200 Message-ID: <83ft1t5tnl.fsf@gnu.org> References: <87tuqbft57.fsf@telefonica.net> <87im6rndo0.fsf@gnus.org> <87v9aqn5eq.fsf@gnus.org> <83h7ma7k5y.fsf@gnu.org> <87tuqa1ogn.fsf@gnus.org> <83tuqa5ug7.fsf@gnu.org> <87eehdy5ie.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23132"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ofv@wanadoo.es, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Feb 18 15:37:40 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 1lCkR1-0005tS-1o for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Feb 2021 15:37:39 +0100 Original-Received: from localhost ([::1]:50108 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCkR0-0006zB-3F for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Feb 2021 09:37:38 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59210) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCkQU-0006ZI-B8 for emacs-devel@gnu.org; Thu, 18 Feb 2021 09:37:06 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:42636) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCkQT-0007u0-00; Thu, 18 Feb 2021 09:37:05 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1028 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lCkQS-0000aY-BN; Thu, 18 Feb 2021 09:37:04 -0500 In-Reply-To: <87eehdy5ie.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 18 Feb 2021 12:33:45 +0100) 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:265152 Archived-At: > From: Lars Ingebrigtsen > Cc: monnier@iro.umontreal.ca, ofv@wanadoo.es, emacs-devel@gnu.org > Date: Thu, 18 Feb 2021 12:33:45 +0100 > > Eli Zaretskii writes: > > > What happens when a command that was only relevant to a single mode is > > extended to become more widely used? Wouldn't we need to remove the > > tagging? And if we do need to do it, how will we manage not to forget > > updating the tagging? > > The tagging is right there in the `interactive' spec (and not somewhere > else (in a plist, for instance)), which is one of the reasons that I > want the syntax to be easy and clear -- it makes it much less likely > that somebody will forget to change the tagging in cases like this. When a command changes, it doesn't necessarily mean its interactive spec or the list of arguments changes. In fact, we try very hard not to make such changes, for compatibility's sake. > (But I don't think that we will, in practice, see all that much of this. > Nobody is going to suddenly use commands from 5x5.el in dired.el.) Who said I had 5x5.el in mind? That's a classic strawman.