Re: scratch/command 064f146 1/2: Change command to interactive ... modes

[Juri Linkov]

>>> To my mind, if two forms of writing the same thing are equally clear and
>>> easy to understand, the less verbose one is often the better choice.
>>> But I would claim that the more verbose form in this case is less clear
>>> and harder to understand.
>>
>> The question is how this form is less clear and harder to understand:
>
> That's fair enough.  But it also seems like a pathological case.

I see nothing pathological here - this is a quite common case,
maybe a little longer than others.  But such valid cases
should not be dismissed lightly.  It would be more hassle
and error-prone to support such long interactive specs with
a mode name dangling at the end.

> (If we support both forms, you could choose the one that is more clear.)

I see no need to support both.