This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Strange ls -CF problem
- To: "'Gnu Win32'" <gnu-win32 at cygnus dot com>
- Subject: Strange ls -CF problem
- From: "Moore, Paul" <Paul dot Moore at uk dot origin-it dot com>
- Date: Wed, 23 Dec 1998 10:53:53 -0000
Hi,
I've got a strange problem with ls -CF. I'm running ls on Windows 95,
from the COMMAND.COM prompt, not bash. My CYGWIN variable is unset.
If I do ls -CF C:/, then I get exactly the results I expect. However, if
I do ls -CF C:\, then ls runs VERY slowly, and produces a series of
lines
/CYGNUS/CYGWIN~1/H-I586~1/BIN/LS.EXE: C:\/IO.SYS: No such device or
address
/CYGNUS/CYGWIN~1/H-I586~1/BIN/LS.EXE: C:\/DRVSPACE.BIN: No such device
or address
/CYGNUS/CYGWIN~1/H-I586~1/BIN/LS.EXE: C:\/WINDOWS: No such device or
address
/CYGNUS/CYGWIN~1/H-I586~1/BIN/LS.EXE: C:\/CONFIG.OLD: No such device or
address
/CYGNUS/CYGWIN~1/H-I586~1/BIN/LS.EXE: C:\/CONFIG.SYS: No such device or
address
/CYGNUS/CYGWIN~1/H-I586~1/BIN/LS.EXE: C:\/LOGO.SYS: No such device or
address
/CYGNUS/CYGWIN~1/H-I586~1/BIN/LS.EXE: C:\/Program Files: No such device
or address
Obviously, something is wrong here - but what, exactly?
Presumably support for backslashes in filenames is broken somehow. Is
this a known bug? It only appears when the directory name ends with a \
- ls -CF C:\WINDOWS works fine.
Paul Moore.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".