I met this issue several months ago, I thought some update may solve it, but is still there.
TAB directly in bash gives a
bad array subscript exception. This is a known issue with bash-completion, can be fixed by
:710s/-eq/-le/g according to https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1289597
some executables can not be completed. For example, I have some small programs (foo, bar, baz) in a folder, say
C:\bin\, and is added to the
PATH variable. I can call those programs by their name both in cmd and bash, but in bash, some of them can not be completed by TAB after some letter (f<TAB> list foo, but b<TAB> gives nothing. ba<TAB> is empty, too).
Let's say, for example, there's a
foo.sh in the current folder. Because
. is not in
PATH, we need to type
./foo.sh to run it. Normally, after
./, <TAB> should show something. But now <TAB> after
./ complete to the subfolder (if any) but not
./f then <TAB> still gives nothing, sometimes
./foo or even
./foo.sh can not be completed.