Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: "ls" finds file1 but "ls file1" does not
Date:	Tue, 10 May 2005 16:28:07 +0100
MIME-Version:	1.0
In-Reply-To:	<000c01c55573$4d04b000$6401a8c0@RossLap>
Message-ID:	<SERRANOFjIcbU8TlGJM000002df@SERRANO.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	10 May 2005 15:28:12.0054 (UTC) FILETIME=[E0794B60:01C55574]

----Original Message----
>From: Ross b
>Sent: 10 May 2005 16:17

> 
> I'm wondering if something else happened in the renaming
> script.  Is it possible there is a space (or some other
> non-printable character) as the first character of the file
> names?  The output on a couple of messages leads me to
> believe so.  When I do an "ls -l", there is only one space
> between the date and the file name, in Charles's output,
> there are two.  I'd be interested to see the output of:
> 
> ls \ *


"ls -q" is the way to detect non-printing chars in filenames.  But I'm not
convinced it's very likely.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -