[Flightgear-devel] [OT] CygWierdness
Does anyone know why this might be happening: $ ls -al *.exe ls: invalid option -- Try `ls --help' for more information. I've already checked alias - I don't have anything for ls. ls --version gives: $ ls --version ls (fileutils) 4.1 Written by Richard Stallman and David MacKenzie. Copyright (C) 2001 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [OT] CygWierdness
Jon Berndt wrote: Does anyone know why this might be happening: $ ls -al *.exe ls: invalid option -- Try `ls --help' for more information. I've already checked alias - I don't have anything for ls. ls --version gives: $ ls --version ls (fileutils) 4.1 Jon, The only thing that comes to mind is to check if you have a .exe filename that starts with a -. This will confuse ls's command line parser. There are a few ways around that, such as ls -al ./*.exe Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [OT] CygWierdness
Jon Berndt wrote: Does anyone know why this might be happening: $ ls -al *.exe ls: invalid option -- Try `ls --help' for more information. I've already checked alias - I don't have anything for ls. ls --version gives: $ ls --version ls (fileutils) 4.1 Written by Richard Stallman and David MacKenzie. Copyright (C) 2001 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel It might be that Win/Dos expands * before it hands the command line to the program. so if there is a file in the directory called --getstuffed.txt then the ls command would get a command line of ls -al --getstuffed.txt If you run under it in a bash shell this should not happen I will test this on my laptop when I get a chance. A co worker had this happen at work yesterday cd v4.0.7 not valid directory was only happening on his laptop and nobody else I tried running cmd instead of command.com and the cd v4.0.7 worked . Sometimes the choice of shell matters. Charles Puffer ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] [OT] CygWierdness
Curt wrote: The only thing that comes to mind is to check if you have a .exe filename that starts with a -. This will confuse ls's command line parser. There are a few ways around that, such as ls -al ./*.exe Heh. You're good. I had a file named -o parseDatcom.exe. Removing that fixed it. Thanks. [I wonder how that file got there ...] Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
