From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: [External] : Re: command mode-specificity [was: scratch/command 064f146 1/2: Change...] Date: Wed, 17 Feb 2021 22:00:47 +0100 Message-ID: <87k0r69zpc.fsf@telefonica.net> 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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8841"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:JGarzc1pijU4q4cQv384c+IxvO0= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Feb 17 22:38:31 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 1lCUWl-0002Ct-42 for ged-emacs-devel@m.gmane-mx.org; Wed, 17 Feb 2021 22:38:31 +0100 Original-Received: from localhost ([::1]:47830 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCUWk-0008IK-6Q for ged-emacs-devel@m.gmane-mx.org; Wed, 17 Feb 2021 16:38:30 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42378) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCTwQ-00054h-JU for emacs-devel@gnu.org; Wed, 17 Feb 2021 16:00:58 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]:48072) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCTwN-0000u1-FH for emacs-devel@gnu.org; Wed, 17 Feb 2021 16:00:56 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1lCTwK-000AQi-9v for emacs-devel@gnu.org; Wed, 17 Feb 2021 22:00:52 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no 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:265087 Archived-At: Eli Zaretskii writes: >> > Wouldn't need constant maintenance, to adjust tagging as things >> > change due to Emacs development? >> >> "Constant" maintenance? No. > > 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? Probably we shall get accustomed to update the tagging, first thing. IMHO it would be a good thing, as its benefits go further than the tagging maintenance.