Re: bash behaves improperly with colons in programmable completion

[Paul Jarc]

jeremy-bash@batray.net wrote:
>       c) if you have typed up to the colon and stopped, bash will display all
>          entries with <TAB><TAB>, whether matching or not.
>       d) if you have typed past the colon, bash will not complete at all.

Unquoted colon is intentionally treated like whitespace for
convenience with PATH-like values.

>       b) if you have not yet typed the colon, bash will correctly comple the
>          common prefix of the entries in the wordlist, but this leads to
>          the c) & d) situation.

I've only tried with path completion, but for me, a colon supplied by
completion is \-escaped, so it won't be treated as whitespace, and it
won't lead to those situations.  Are you sure the same doesn't happen
for you?


paul