When using bash completion on files within local folder, ie. "$ ls f<tab>" showing results for files starting with char "f" -- or any char(s) you may specify, results are not provided in color when bash, terminal and ls are configured for using color. I do believe, results for bash completion on files were at one time in color. To further troubleshoot, I removed /etc/bash/bashrc and $HOME/.bashrc and only enabling related color commands. Reproducible: Always I have tracked this down to the call: compgen -d -- "$quoted" (Give or take some commands as I found this by using strace/ltrace or grepping the files belonging to bash/bash-completion packages.) Doing something like "compgen -d |ls --color" does provide color, but is likely not proper. I believe compgen is provided by bash and not bash-completion. Using the following packages: =app-shells/bash-4.1_p9 =app-shells/bash-completion-1.2 =app-shells/gentoo-bashcomp-20101217 Using both rxvt-unicode and framebuffer console. Grepping around, I can see no references to anything color related when dealing with compgen or $COMPREPLY. I did trace the "ls" (core-utils) to "/usr/share/bash-completion/base" of bash-completion. Any ideas?
I posted this to the Bash mailing list on Saturday February 5 and have only received one response so far. If I don't hear anything else by the end of the week, I'll just close this. I know so far, I can modify one of the files (/usr/share/bash-completion/base?) and pipe the compgen result to ls --color, but am unsure if this would be correct.
I've never seen colourised output myself, so I'll set this as an enhancement.
Thanks for filing the request. I'll /consider/ backporting a patch for this if the results are worth it. But, if upstream doesn't accept it, it won't land in Gentoo either as the maintenance burden for non-upstream patches is too great.
