Re: [External] : Re: command mode-specificity [was: scratch/command 064f146 1/2: Change...]

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: monnier@iro.umontreal.ca,  ofv@wanadoo.es,  emacs-devel@gnu.org
> Date: Thu, 18 Feb 2021 12:33:45 +0100
> 
> Eli Zaretskii <eliz@gnu.org> 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.