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

[Alan Mackenzie <acm@muc.de>]

Hello, Lars.

On Thu, Feb 18, 2021 at 12:33:45 +0100, Lars Ingebrigtsen wrote:
> 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.
> (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.)

What about commands used by a small number of modes, but that set of
modes is only known at runtime?

Are we supposed to amend a command's interactive spec at runtime?

> -- 
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no

-- 
Alan Mackenzie (Nuremberg, Germany).