On 1/14/15 10:52 AM, Dave Rutherford wrote:
> On Wed, Jan 14, 2015 at 10:14 AM, Eduardo A. Bustamante López
> wrote:
>> Can you test with:
>> bash --norc --noprofile -i
>
> It is working in this case. The difference seems to be in direxpand.
Thanks, that was the key. This will be fixed in the
On Wed, Jan 14, 2015 at 10:14 AM, Eduardo A. Bustamante López
wrote:
> Can you test with:
> bash --norc --noprofile -i
It is working in this case. The difference seems to be in direxpand.
$ shopt -s direxpand; shopt direxpand
direxpand on
$ vi ~/a/a\ [nothing]
$ shopt -u direxpand
Dave Rutherford writes:
> On Wed, Jan 14, 2015 at 9:45 AM, Eduardo A. Bustamante López
> wrote:
>> Are you using any supplementary programs, like bash-completion?
>
> I don't think so, unless Debian turned it on for me.
Run complete -p to find out.
Andreas.
--
Andreas Schwab, SUSE Labs, sch.
On 1/14/15 9:33 AM, d...@evilpettingzoo.com wrote:
> Bash Version: 4.2
> Patch Level: 37
> Release Status: release
>
> Description:
> Pathnames starting with tilde, combined with filenames containing
> space, only partially tab-complete.
I can't reproduce this using bash-4.2.53 or bash-4.
On Wed, Jan 14, 2015 at 09:55:33AM -0500, Dave Rutherford wrote:
[...]
> I don't think so, unless Debian turned it on for me.
Can you test with:
bash --norc --noprofile -i
> Note that without a\ a.odt there,
> $ ls ~/a/a[completes to a\ a.txt]
> but
> $ ls ~/a/a\ [do
On Wed, Jan 14, 2015 at 9:45 AM, Eduardo A. Bustamante López
wrote:
> On Wed, Jan 14, 2015 at 09:33:31AM -0500, d...@evilpettingzoo.com wrote:
> [...]
>> Bash Version: 4.2
>> Patch Level: 37
Also tested on 4.3.30
> [dualbus@dualbus ~]$ mkdir a; >a/a\ a.txt
You didn't create any ambiguity there.
On Wed, Jan 14, 2015 at 09:33:31AM -0500, d...@evilpettingzoo.com wrote:
[...]
> Bash Version: 4.2
> Patch Level: 37
[dualbus@dualbus ~]$ mkdir a; >a/a\ a.txt
[dualbus@dualbus ~]$ echo ~/a/a [completes]
[dualbus@dualbus ~]$ echo ~/a/a\ a.txt
/home/dualbus/a/a a.txt
[dualbus@dualbus ~]$ echo ~/a/a\
