X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 8 Aug 2008 14:38:26 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Bizarre Cygwin/Explorer/paths problem half-solved Message-ID: <20080808183826.GA31740@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> 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@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 01:39:49PM -0400, Lev Bishop wrote: >On Fri, Aug 8, 2008 at 12:28, Christopher Faylor wrote: > >>> 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. > >Nobody is munging anything. > >What's going on here is as simple as the difference: > >bash-3.2$ cmd /c echo "a b c" >"a b c" >bash-3.2$ cmd /c echo a b c >a b c > >There's really no more to it than that. Yes. I understand. There was one message which indicated that cygwin was converting paths on the command line which is, of course, nonsense. 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/