X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 8 Aug 2008 10:16:57 -0500 (CDT) From: Tim McDaniel cc: cygwin@cygwin.com Subject: RE: Bizarre Cygwin/Explorer/paths problem half-solved In-Reply-To: <20080808064144.94C9485E51@pessard.research.canon.com.au> Message-ID: References: <20080808064144.94C9485E51@pessard.research.canon.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-IsSubscribed: yes 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, 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? -- Tim McDaniel, tmcd@panix.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/