On 2/2/18 6:18 AM, Odne Hellebø wrote:
> Damn :) my email is in a changelog :D Thanks :)
Credit where credit's due.
> One thing though, is it possible to stop the cursor at the point it
> gets ambiguous? As in I have function
> foobar and fooBar if I do
> foo<tab> I will get foobar and if my intent was to execute fooBar I
> will have to go back and uppercase it. I think it would be better if
> you stopped at foo and gave the completion options there, then if I
> wrote b<tab> I'd get foobar or B<tab> I'd get fooBar.
That's a kind of hybrid case-insensitivity that Readline has never
supported. If you want completions to be treated without regard to
case, Readline will take that all the way to considering multiple
possible completions that differ only in case as identical.
This is one of the things that would be helped by allowing programmable
completion for command names, but we're not there yet. You could get
some approximation of what you want by binding TAB to menu-complete, but
that might be too disruptive to the rest of your environment.
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/