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

[Eli Zaretskii]

> Date: Thu, 18 Feb 2021 17:35:44 +0000
> From: Alan Mackenzie <acm@muc.de>
> 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.