I got the file by running some code using procees substitution with set +o posix. I don't think the drectory was empty but what you say make sense and I didn't think to checkt it at the time.
Thanks JOhn Gesendet: Sonntag, 18. August 2013 um 20:42 Uhr Von: "Chet Ramey" <chet.ra...@case.edu> An: dethrop...@web.de Cc: bug-bash@gnu.org, b...@packages.debian.org, chet.ra...@case.edu Betreff: Re: autocomplete error doesn't look to be in bash-complete so I'm reporting it here. On 8/16/13 5:28 AM, dethrop...@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 c...@case.edu [1]http://cnswww.cns.cwru.edu/~chet/ References 1. http://cnswww.cns.cwru.edu/~chet/
