Chet Ramey wrote:
> This might be the result of changes to the bash readline support function
> that dequotes filenames. That function was changed as the result of bug
> reports against bash-3.2 to better implement shell quoting. That means:
>
> 1. Backslashes should not be stripped within sing
Krzysiek Pawlik wrote:
> Chet Ramey wrote:
>> I can't reproduce this. I get a\ (escaped space), and then listing of
>> possible completions with subsequent TABs. This is the correct behavior.
>> Could it have something to do with any completion functions you have
>> defined?
>
> Yes, it does. Wh
Chet Ramey wrote:
> I can't reproduce this. I get a\ (escaped space), and then listing of
> possible completions with subsequent TABs. This is the correct behavior.
> Could it have something to do with any completion functions you have
> defined?
Yes, it does. When I tested without any completio
Krzysiek Pawlik wrote:
> Hello,
>
> With bash-4.0-10 I get following behavior:
>
> $ touch 'a file with spaces'
> $ touch 'a File with spaces'
> $ touch 'a File With spaces'
> $ cat a
>
> After pressing TAB completion seems to stop working, pressing Ctrl-i (another
> bind for `complete') also do
Hello,
With bash-4.0-10 I get following behavior:
$ touch 'a file with spaces'
$ touch 'a File with spaces'
$ touch 'a File With spaces'
$ cat a
After pressing TAB completion seems to stop working, pressing Ctrl-i (another
bind for `complete') also doesn't work, using Alt+/ (bind for complete-f
