X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 8 Aug 2008 12:28:40 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Bizarre Cygwin/Explorer/paths problem half-solved Message-ID: <20080808162840.GA31347@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20080808064144 DOT 94C9485E51 AT pessard DOT research DOT canon DOT com DOT au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) 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, Aug 08, 2008 at 10:16:57AM -0500, Tim McDaniel wrote: > On Fri, 8 Aug 2008, Luke Kendall wrote: >> On 4 Aug, Gary R. Van Sickle wrote: >>> explorer /e,$XPATH & disown %- >> >> Don't try this variant, though, since it doesn't work: >> >> explorer /e,"$XPATH" & disown %- >> >> What happens if you try that innocuous-looking variant is that >> Cygwin (or bash?) normalises the path /e,... to a windows path >> first, producing \e,... > > I'm an utter fanatic about quoting to make sure that what I have in > variables isn't munged. So I'm dismayed to learn that quoting can > *cause* munging and that something munges values in new and exciting > ways. > > Is there any documentation on who rewrites arguments, under what > conditions, and how they're altered? I missed this when it was first mentioned. Cygwin doesn't munge command line arguments. Why would it assume that /e,something was a windows path? That makes no sense. 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/