Re: Leaving out non-applicable commands on Mx

[Óscar Fuentes]

Lars Magne Ingebrigtsen <address@hidden> writes:

> John Wiegley <address@hidden> writes:
>
>>>>>>> Óscar Fuentes <address@hidden> writes:
>>
>>>> We've discussed before adding mechanisms for leaving mode-specific commands
>>>> out, but I was apparently the only one enthusiastic about it...
>>
>>> You sketched a possible implementation. If you are interested on completing
>>> the part that requires a smart hacker, I'll do the part that requires a dumb
>>> one :-)
>>
>> What is this feature suggestion again?
>
> Marking commands as applicable to a mode (or a set of modes) so that
> completion doesn't list them outside of those modes.

I envision a somewhat more generic system, where the command can state
that it operates only on read-only buffers, or on buffers that are
visiting a file, or on buffers that are visiting a versioned file. Using
the syntax proposed by Lars:

(declare (type versioned))

or

(command 'versioned "p")

[snip]