Message-ID: <4C9CB819.9010308@redhat.com>
Date: Fri, 24 Sep 2010 08:39:21 -0600
From: Eric Blake <eblake@redhat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100907 Fedora/3.1.3-1.fc13 Mnenhy/0.8.3 Thunderbird/3.1.3
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: backtics
References: <79eb8d2be6552119c923d635791104be.squirrel@orangepalantir.org>
In-Reply-To: <79eb8d2be6552119c923d635791104be.squirrel@orangepalantir.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 09/24/2010 07:43 AM, melkor@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   eblake@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