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 21:42:57 +0200 Message-ID: <83wnv540xq.fsf@gnu.org> References: <87v9aqn5eq.fsf@gnus.org> <83h7ma7k5y.fsf@gnu.org> <87tuqa1ogn.fsf@gnus.org> <83tuqa5ug7.fsf@gnu.org> <87eehdy5ie.fsf@gnus.org> <87tuq98gdl.fsf@telefonica.net> <87pn0x8f8l.fsf@telefonica.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1693"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ofv@wanadoo.es, emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Feb 18 20:44:58 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 1lCpEP-0000GV-Gd for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Feb 2021 20:44:57 +0100 Original-Received: from localhost ([::1]:34440 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCpEO-0001S4-FA for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Feb 2021 14:44:56 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37714) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCpCI-0008Fd-HZ for emacs-devel@gnu.org; Thu, 18 Feb 2021 14:42:46 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49047) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCpCH-0001Yg-0J; Thu, 18 Feb 2021 14:42:45 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3903 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lCpCG-0007H9-Cz; Thu, 18 Feb 2021 14:42:44 -0500 In-Reply-To: (message from Alan Mackenzie on Thu, 18 Feb 2021 17:35:44 +0000) 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:265181 Archived-At: > Date: Thu, 18 Feb 2021 17:35:44 +0000 > From: Alan Mackenzie > Cc: emacs-devel@gnu.org > > > It would be nice to update the info at runtime, but IMO it is beyond > > what is reasonable to ask. > > In other words, this is a flaw in the idea of abusing the interactive > spec for miscellaneous information. No, this issue is common to _any_ implementation of tagging commands with relevant mode, not just the implementation via the interactive spec. > > In the future the system can be expanded so a mode can declare that it > > uses specific commands (or all of them) from some other mode, but that > > is not required now for the filtering to be effective. > > No, not from some other mode. We're talking about commands shared by a > set of modes known only at runtime. If the list of modes cannot be > updated at runtime, this is a deficiency in the design. I don't think this problem is real, because the idea is that commands which are relevant only to a _single_ mode will be tagged by that mode. Commands which are useful in several modes will remain untagged.