On Mon, Apr 30, 2018 at 11:11:06PM +0700, Robert Elz wrote:
> | 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 "fo
On Tue, May 1, 2018 at 6:01 AM, Christos Zoulas wrote:
> In article ,
> Michael van Elst wrote:
>>jo...@bec.de (Joerg Sonnenberger) writes:
>>
>>>touch 'foo bar'
>>>ls foo
>>
>>Pressing TAB after foo yields:
>>
>>$ touch 'foo bar'
>>$ ls foo\ bar
>>foo bar
>>
>>But
>>
>>$ touch 'foo*bar'
>>$ ls f
In article ,
Michael van Elst wrote:
>jo...@bec.de (Joerg Sonnenberger) writes:
>
>>touch 'foo bar'
>>ls foo
>
>Pressing TAB after foo yields:
>
>$ touch 'foo bar'
>$ ls foo\ bar
>foo bar
>
>But
>
>$ touch 'foo*bar'
>$ ls foo
>foo bar foo*bar
>$ ls foo*bar
>foo bar foo*bar
>
>Somewhere sh knows
Date:Mon, 30 Apr 2018 21:23:05 +0530
From:Abhinav Upadhyay
Message-ID:
| I believe this is happening in libedit.
I assumed that would be related. sh itself as almost
nothing to do with it.
| Few months back I added
| escaping of special characters when doi
Date:Mon, 30 Apr 2018 16:47:10 +0200
From:Joerg Sonnenberger
Message-ID: <20180430144710.gc29...@britannica.bec.de>
| touch 'foo bar'
| ls foo
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
On Mon, Apr 30, 2018 at 8:56 PM, Michael van Elst wrote:
> jo...@bec.de (Joerg Sonnenberger) writes:
>
>>touch 'foo bar'
>>ls foo
>
> Pressing TAB after foo yields:
>
> $ touch 'foo bar'
> $ ls foo\ bar
> foo bar
>
> But
>
> $ touch 'foo*bar'
> $ ls foo
> foo bar foo*bar
> $ ls foo*bar
> foo bar
jo...@bec.de (Joerg Sonnenberger) writes:
>touch 'foo bar'
>ls foo
Pressing TAB after foo yields:
$ touch 'foo bar'
$ ls foo\ bar
foo bar
But
$ touch 'foo*bar'
$ ls foo
foo bar foo*bar
$ ls foo*bar
foo bar foo*bar
Somewhere sh knows that a space needs quoting but not a '*'. It
also doesn't
On Mon, Apr 30, 2018 at 08:48:11AM +0700, Robert Elz wrote:
> Back in May 2005. dsl@ added this in the BUGS section of sh(1):
>
> The characters generated by filename completion should probably be quoted
> to ensure that the filename is still valid after the input line has been
> pr
On 30/04/2018 02:48, Robert Elz wrote:
Back in May 2005. dsl@ added this in the BUGS section of sh(1):
The characters generated by filename completion should probably be quoted
to ensure that the filename is still valid after the input line has been
processed.
Does anyone (inc
