Hi, Christoph, On 08 Mar 2018, Christoph Anton Mitterer wrote:
>Actually I think, it would be even better to just have * not expand by >completion per default (which would often just clutter up the readline >with countless of possible matches)... A bit of good news on this bug... An upstream commit changed the behavior of wildcard completion. Now, completion of wildcards behaves just as you mentioned you would prefer, i.e.: they don't expand to anything. I have backported this patch to Debian's bash-completion and I have just uploaded a new version, which should show up in sid soon. >the best (if that was possible) >would perhaps be if it just *shows* the possible completions, but does >not actually expand to it. That is possible, but it would require a change that has not yet been accepted upstream [1]. I have added this information to Debian's bash-completion git repository [2], but I'm not yet confident that this is the right thing to do, so I will not apply this to Debian. Thanks! [1] https://superuser.com/questions/823257/unexpected-bash-glob-completion-uses-first-match-even-if-ambiguous/1022284#1022284 [2] https://salsa.debian.org/debian/bash-completion/commit/bab51728186237e4204f30860387c2f7511f291c
