On Tue, Jun 16, 2020 at 9:48 PM David Wright <deb...@lionunicorn.co.uk> wrote: > Where bash-completion does get in the way for me is, for example, > where you download a file that's, say, a PDF but it arrives via wget > called, say, index_0001.3872359.html, for whatever reason. > So you type xpdf inde [TAB] and bash-completion refuses to > complete the name any further. If you're lucky, typing * [RETURN] > will work, if there aren't any disruptive filenames which match > inde*, but in other cases the fastest workaround I know is to type > [HOME]less[SPACE][END] whereupon bash-completion is happy to match > any old filename for the less command, which you then rub out. > > That's just one example, but it represents a whole class where it > seems that a bunch of files have disappeared because bash won't match them.
First time this happened to me (it also happens with buggy completion-scripts where the author doesn't know all the ways to use the tool) I found that bash maps M-/ to "complete-filename" by default. This can be used in all contexts. The only problem is that I always forget the combo.
