On 09/24/2010 07:43 AM, mel...@orangepalantir.org wrote:
This probably isn't a backtic problem, but using backtics causes it.
ls `ls`
results in file not found errors. ie:
bash-3.2$ ls
35ms 40ms 80ms
bash-3.2$ ls `ls`
ls: cannot access 35ms: No such file or directory
ls: cannot access 40ms: No such file or directory
ls: cannot access 80ms: No such file or directory
bash-3.2$
WJFFM:
$ mkdir abc && cd abc && touch 35ms 40ms 80ms
$ ls
35ms 40ms 80ms
$ ls `ls`
35ms 40ms 80ms
In trying to think of things that might be interfering, do you have a
problematic alias or shell function named ls? For example, if ls is
aliased to 'ls --color=always', and those particular files would be
colored by your dircolors settings, then I could see that causing a
failure (hint, use --color=auto, not --color=always, when aliasing ls).
Also, running under 'set -vx' may be informative.
--
Eric Blake ebl...@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple