RE: accept-and-infer-next-history in path completion

["Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>]

>
> I'm a bit (er, a lot) behind on patches ... what's the difference between
> this and accept-and-menu-complete?  And if there is a difference, maybe
> accept-and-hold would be a better widget to co-opt than a-a-i-n-h?
>

a-a-m-c accepts finishes the completion of current word and adds _new_ word with
next possible match. a-a-i-n-h in menu select accepts currently selected match
and continues to complete _the_current_word_. In case of multipart ambiguous
completion it makes a big difference:

bor@itsrm2:~%> l /a/p/u/z/*<TAB>
bor@itsrm2:~%> l /archive/pub/unix/z<TAB>
zip/     zmodem/  zsh/
bor@itsrm2:~%> l /archive/pub/unix/zip
zip/     zmodem/  zsh/

If you now press a-a-m-c you get:

bor@itsrm2:~%> l /archive/pub/unix/zip /archive/pub/unix/zmodem
zip/     zmodem/  zsh/

and if you press a-a-i-n-h

bor@itsrm2:~%> l /archive/pub/unix/zip/unzip532.tar.gz
unzip532.tar.gz   zcrypt27.zip      zip22.tar.gz
unzip540.tar.gz   zcrypt28.zip

it assumes, that SELCTMINis set to 0 or 1, so that menu selection is started
immediately.

/andrej