X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 8 Aug 2008 20:32:25 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Bizarre Cygwin/Explorer/paths problem half-solved Message-ID: <20080809003225.GA32456@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20080808064144.94C9485E51@pessard.research.canon.com.au> <20080808162840.GA31347@ednor.casa.cgf.cx> <20080808192948.GB31846@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080808192948.GB31846@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Fri, Aug 08, 2008 at 03:29:48PM -0400, 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. But, no, we're not >going to implement a complicated scheme to turn that off for random >programs. If you don't like the behavior, right a C program to fix write >things up. Right. cgf -- 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/