On Wed 18 Nov 2015 at 08:49:13 +0100, [email protected] wrote: > On Tue, Nov 17, 2015 at 11:08:24PM +0000, Brian wrote: > > On Tue 17 Nov 2015 at 21:18:57 +0100, [email protected] wrote: > > > > > On Tue, Nov 17, 2015 at 06:56:40PM +0000, Brian wrote: > > > > > > [...] > > > > > > > My example: gv does not recognise the PDF file 'test' as something it is > > > > *capable of opening*. With 'test' as the only file in a directory the > > > > command gv plus TAB completion doesn't produce 'gv test'. But 'gv test' > > > > opens the file, which is all that matters. > > > > > > The TAB thing is your shell's autocompletion talking, gv isn't involved. > > > And yes, shell's autocompletion usually relies on the file name pattern > > > (dot-ending, aka "extension" is but a special case of that). > > > > David Wright said something similar. > > > > https://lists.debian.org/debian-user/2015/11/msg00631.html > > > > The file "example" is a PDF. > > > > 'gs exa' and 'mupdf exa' TAB complete the file name. gv and xpdf do > > not. Is the shell being discriminatory? > > Just your shell's autocompletion patterns. Fix them if you don't like > them :-)
To be precise, the bash-completion package causes this behaviour. gv and xpdf have lines in /usr/share/bash-completion/bash_completion; mupdf and gs do not.
