bug-bash
[Top][All Lists]
Advanced

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

Re: autocomplete error doesn't look to be in bash-complete so I'm report


From: Chet Ramey
Subject: Re: autocomplete error doesn't look to be in bash-complete so I'm reporting it here.
Date: Sun, 18 Aug 2013 14:42:48 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5

On 8/16/13 5:28 AM, dethrophes@web.de wrote:

> Bash Version: 4.2
> Patch Level: 25
> Release Status: release
> 
> Description:
>       autocomplete error doesn't look to be in bash-complete so I'm reporting 
> it here.
> 
> Repeat-By:
>   touch  '>(pygmentize -l text -f html )'
>   rm >[Press tab]
> 
>   rm >\>\(pygmentize\ -l\ text\ -f\ html\ \)
>      ^ Note leading >

I'm going to assume you did this in a directory with no other files, so
tab-completing nothing results in the filename that strangely resembles
process substitution.

If you don't quote the `>', bash interprets it as a redirection operator,
as the parser would, and performs filename completion.  The tab results in
the single filename.  If you were to backslash-quote the `>', you'd get
the filename as you intended.

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]