bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Filename completion broken on single quote


From: Chet Ramey
Subject: Re: Filename completion broken on single quote
Date: Fri, 14 Oct 2011 13:30:18 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1

On 10/13/11 10:37 AM, lolilolicon wrote:
> Inside an empty directory:
> 
>   touch 1 1\'1
>   complete -r ls
>   ls 1\'<TAB>       # ls 1\'1
>   complete -f ls
>   ls 1\'<TAB>       # ls 1
>   ls 1\\\'<TAB>     # ls 1\'1
> 
> (Note: the comment on the right is the result after pressing <TAB>)
> 
> Is this broken behavior?
> Why on earth does the user have to double-escape at all?
> Is there any benefit of this?

Thanks for the report.  This looks like a problem, or an omission, with
the effects of the `-f' option to complete, since it works as expected
without using programmable completion or when using `-o default'.  I
will take a look.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]