Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 20 Jan 2005 10:26:13 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: cygwin programs called from non-cygwin programs mauling \" in args Message-ID: <20050120092613.GB4951@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20050113064248 DOT GA2416 AT efn DOT org> <20050119233410 DOT GA2888 AT efn DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050119233410.GA2888@efn.org> User-Agent: Mutt/1.4.2i Yitzchak, On Jan 19 15:34, Yitzchak Scott-Thoennes wrote: > > $ ./nocygparent cygchild > > [a\b"c] > > Can anybody else confirm this? I can. I already had a look into this. The command line handling in Cygwin is different from the command line handling in MingW or, FWIW, VC++ CLI applications. The question is if we really should align the rules how a native command line is evaluated by a Cygwin process should be aligned to Windows rules or not. There are three arguments to consider: - Using Windows/MingW rules lowers the surprise. - Changing the rules at all breaks backward compatibility. - Why shouldn't Cygwin applications use their own rules which seem more appropriate for a POSIX application? Btw., if you want the same result as for the noncygchild, just quote: $ cygchild "a\"b\"c" Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/