X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 8 Aug 2008 14:47:43 -0500 (CDT) From: Tim McDaniel To: cygwin AT cygwin DOT com Subject: Re: Bizarre Cygwin/Explorer/paths problem half-solved In-Reply-To: <20080808192948.GB31846@ednor.casa.cgf.cx> Message-ID: References: <20080808064144 DOT 94C9485E51 AT pessard DOT research DOT canon DOT com DOT au> <20080808162840 DOT GA31347 AT ednor DOT casa DOT cgf DOT cx> <20080808192948 DOT GB31846 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Fri, 8 Aug 2008, Christopher Faylor wrote: > On Fri, Aug 08, 2008 at 01:58:12PM -0500, Tim McDaniel wrote: >> That's most unpleasant. I don't suppose there's any way to control >> Cygwin's bash in re where to put double quotes around arguments >> being passed to a Windows command (since getting Microsoft to make >> explorer.exe be sane is hopeless)? Except by not using characters >> that bash thinks need quoting. > > I'd be very surprised if bash was doing anything different for > Windows than it does for linux. cygwin1.dll does do some quoting of > arguments to non-cygwin programs if it thinks it is required. Well, *something* had to be adding the double-quotes. It's execve() and such adding them, then? > But, no, we're not going to implement a complicated scheme to turn > that off for random programs. -- Tim McDaniel, tmcd AT panix DOT com -- 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/