Re: Tabs

[Juri Linkov]

>>> > 2. None of these interactive commands work when run with M-x:
>>> >
>>> > command-execute: tab-line-add-tab must be bound to an event with 
>>> > parameters
>>> > command-execute: tab-line-close-tab must be bound to an event with 
>>> > parameters
>>> > command-execute: tab-line-select-tab must be bound to an event with 
>>> > parameters
>>> > command-execute: tab-line-switch-to-next-tab must be bound to an event
>>> > with parameters
>>> > command-execute: tab-line-switch-to-prev-tab must be bound to an event
>>> > with parameters
>>>
>>> Mouse commands don't work with M-x.  For example, try M-x 
>>> Buffer-menu-mouse-select
>>
>> True.
>>
>>> but we could declare the EVENT arg optional for these commands,
>>> and perform non-mouse logic when it's nil.
>>
>> This is what I would prefer.  I think users will naturally try to use
>> these commands and be surprised when they don't work.
>
> But the EVENT arg in these commands already is optional.
> And executing them with M-x fails because interactive spec is
> (interactive "e").  Do you know what interactive spec to use
> to not raise the error "must be bound to an event with parameters"
> when executing with M-x?

I realized this is possible to do by replacing ‘(interactive "e")’
with ‘(interactive (list last-nonmenu-event))’, implemented.