X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org X-IronPortListener: Outbound_SMTP From: "Buchbinder, Barry (NIH/NIAID) [E]" To: "cygwin AT cygwin DOT com" , "Batson, Chuck" Date: Fri, 22 Jan 2010 09:51:59 -0500 Subject: RE: Design issue with new MS-DOS style path warning? Message-ID: <0105D5C1E0353146B1B222348B0411A208B2636F4F@NIHMLBX02.nih.gov> References: <81D39E818991E549B1F66EB6A7D18422BE8626 AT AVSMOEXCL02 DOT activision DOT com> In-Reply-To: <81D39E818991E549B1F66EB6A7D18422BE8626@AVSMOEXCL02.activision.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Batson, Chuck sent the following at Wednesday, January 20, 2010 8:11 PM >I am aware it is possible to disable the "MS-DOS style path detected" >warning with the 'nodosfilewarning' option. > >But this message raises the question of, "What is the Cygwin ideal?" >That is, how to avoid the warning in a "clean" way without resorting to >the 'nodosfilewarning' option? (1) It seems to me that 'nodosfilewarning' is "clean" and is "the Cygwin ideal". What is the problem using it? (2) Have people set the CYGWIN environmental variable? I would think that anyone who can handle the command line could handle that. (3) Note to the CYGWIN DEVELOPERS: Now that the mount table is has moved from the Registry to a text file, perhaps it would make sense for cygwin1.dll to look at a text file, e.g., /etc/cygwin.env, if the CYGWIN environmental variable is unset. This might also allow one to duplicate a cygwin installation by just copying a directory tree and the appropriate Windows batch files and shortcuts without having to run setup and without having set CYGWIN via the Control Panel | System | Advanced | Environmental Variables. Just a suggestion, not a request. (I don't need it.) >There is a situation in which it is not conceptually "clean" to avoid >the warning: at the interface between the host OS and Cygwin tools. > >Say, for example, you create a Windows batch file containing the line: > touch C:\foo.txt (4) Does the following work if you put it at the beginning of the batch file? set CYGWIN=3D%CYGWIN% nodosfilewarning (Sorry I haven't tested - too much trouble.) (5) Tell people to always run from the current directory? cd C:\ touch foo.txt (6) Don't use cygwin. Compile the utilities of interest under MinGW. http://www.mingw.org/ (While you are there, look into MSYS and mingwPORTs.) Find native utilities. Here are the 2 I know about. http://sourceforge.net/projects/pw32/ http://unxutils.sourceforge.net/ Note that they haven't been updated in a while. (7) Go back to 1.5. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple