This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: "ls" finds file1 but "ls file1" does not
- From: "Ross Boulet" <ross at rossb dot com>
- To: <cygwin at cygwin dot com>
- Date: Tue, 10 May 2005 10:16:40 -0500
- Subject: RE: "ls" finds file1 but "ls file1" does not
> >> [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/