Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: "Ross Boulet" To: Subject: RE: "ls" finds file1 but "ls file1" does not Date: Tue, 10 May 2005 10:16:40 -0500 Message-ID: <000c01c55573$4d04b000$6401a8c0@RossLap> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: X-IsSubscribed: yes > >> [etc] Did your ash script go wrong and rename all > those files with > actual > >> asterisks on the end ? > > > The * in the listing just indicates that the file is > executable (an ls > > option that I use by default). > > > Hey, just wondered. It happened to me once.... > > 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 \ * Ross -- 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/