Edward Peschko wrote: >> This is your second warning on this subject, btw. > > Chris, > what are your warnings?
The warning is that further mail from you may be automatically kill-filed by most readers of this list, once they get the impression that you have absolutely no idea whatsoever of the goals of the cygwin project, and that you seemingly don't care either. Once again: cygwin (with or without -mno-cygwin, with or without Msys) is *not* attempting (and will *never* attempt) to provide a perfect (or even an imperfect) Windows look and feel using Unix/Linux/Posix commands. It's providing a Unix/Linux look and feel using Unix/Linux/Posix commands. So you won't find a pervasive use of backslashed paths, and the shells will never be modified so that you can do cd c:\windows\temp and have it go to c:/windows/temp (hint: the single-\t becomes a tab). Etc. etc. If you have genuine problems with cygwin not doing *what it is supposed to do*, by all means write to this list, *following the cygwin problem reporting conventions*. Don't, however, get into long arguments about why pwd should be modified to return native windows paths, and why cd should accept native windows paths, and why ls should hide DLLs, and all that. Or you risk being consigned to the dreaded Bin Of Irrelevance (aka the kill file). Hint: if you want a genuine Windows(TM)-like environment, be sure to: * run CMD.EXE as your shell * put c:\cygwin\bin at the end of your %PATH%, so that you always pick up the windows equivalents of the commands that you are familiar with. -- Shankar. -- 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/
