From: dbe@wgn.net ("$Bill Luebkert") Subject: Re: cygnus bugs 15 Jul 1997 22:22:10 -0700 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <33CC3B24.364F.cygnus.gnu-win32@wgn.net> References: <199707121921.JAA02783@haleakala.aloha.net> <199707130728.RAA03575@murlibobo.cs.mu.OZ.AU> <33c8f0a3.1384462@world.std.com> <199707140254.MAA02915@mundook.cs.mu.OZ.AU> <33C9D7BB.6D8F@wgn.net> <199707150754.RAA05897@murlibobo.cs.mu.OZ.AU> Reply-To: dbe@wgn.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01Gold (Win95; I) Original-To: gnu-win32@cygnus.com Original-Sender: owner-gnu-win32@cygnus.com Fergus Henderson wrote: > > You still didn't answer the question: how can cygwin know which > arguments are pathnames? Finding a correct solution to this > problem is entirely non-trivial. If you mean that cygwin should > treat everything that looks like it might be a pathname as a pathname, > then that is not a correct solution, and I think an incorrect > solution is going to cause more problems than it solves. Quote the ones you don't want converted. > For example, consider the command `sed /usr/p /usr/p'. > In that command, the first argument is a sed command, meaning > "print all lines containing `usr'", while the second argument > is a file name. sed '/usr/p' /usr/p -- ,-/- __ _ _ $Bill Luebkert (_/ / ) // // DBE Collectibles / ) /--< o // // http://www.wgn.net/~dbe/ -/-' /___/_<_