Date: Mon, 30 Apr 2018 16:47:10 +0200
From: Joerg Sonnenberger <jo...@bec.de>
Message-ID: <20180430144710.gc29...@britannica.bec.de>
| touch 'foo bar'
| ls foo<TAB>
That one seems to be handled already
.[jinx]$ ls -l foo\ bar
-rw-r--r-- 1 kre wheel 0 Apr 30 22:57 foo bar
(which came from typing the two lines you gave, plus a \n to
end the command - the \ appeared all by itself....) Roy indicated
that this worked for him as well.
| Similar for * or other special characters.
That one not so much, unless the user enters a " (in which case
tabcomplete seems to fill in the closing "). That happens for the
space case as well, typing
ls "foo<tab>
ends up producing
ls "foo bar"
(with a trailing space)
I'm not sure what is correct (or perhaps "wanted") here, if you do
ls foo*bar
you expect to get all files with names starting foo and ending bar
Is it really to be different just because the command line was built
using tabcomplete rather that simply typed?
I have no particular opinion, I don't use tabcomplete (or whatever its
readline equivalent is) so I don't know what the real expectation is
here.
kre
