Re: [rr13@mail.inf.tu-dresden.de: Bug#276187: zsh: Ineractive menu completion with tab doesnt work.]

[Bart Schaefer <schaefer@brasslantern.com>]

On Wed, 13 Oct 2004 pws@pwstephenson.fsnet.co.uk wrote:

> I can see the part of the code which is causing this: modline in the 
> function domenuselect is inconsistently handled.  At one point it gets 
> assigned just the combined prefix and suffix from the last completion, 
> but everywhere else it's assumed it's the whole line.

There's only one other assignment to it that I can see.

> However, I'm not quite sure what this is supposed to do.  Evidently it's 
> supposed to something special, not simply normal menu completion, but I 
> don't really know what.

I think what's supposed to happen is this:

You enter interactive completion (this may e.g. require two presses of TAB 
depending on your other menu completion/listing settings).  At this point, 
if you start typing the disambiguating characters, the menu list changes 
on the fly to show the changing subset (or superset, for corrections) of 
the possible completions that match, and backspace widens the list again.

This part all works fine.

If you type TAB again in this mode, though, it's not clear what should 
happen.  If you've already begun to disambiguate, typing TAB does nothing.  
The bug happens when you type TAB immediately after entering interactive 
completion, before any disambiguation has occurred.  I suspect in this 
case it's fine just to drop straight back into normal menulist completion 
and cancel interactive mode.  (Ideally that would happen even after the 
disambiguation has begun, too, rather than have TAB be a no-op there.)

> After fixing or blocking out the problem, it just does normal 
> menucompletion, i.e. the fact you're in ineractive completion doesn't 
> make a difference.

Fixing how?