X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <796377.93249.qm@web30205.mail.mud.yahoo.com> References: <796377 DOT 93249 DOT qm AT web30205 DOT mail DOT mud DOT yahoo DOT com> Date: Wed, 9 Sep 2009 11:56:54 -0400 Message-ID: Subject: Re: syntax for Cygwin bash invoking Win apps From: "Mark J. Reed" To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes 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 Wed, Sep 9, 2009 at 11:27 AM, Ziser, Jesse wrote: >>> $ cmd /c echo "\"abc\"" >>> "\"abc\"" >>> >>> # Wahhh?! >>> >>> Anyone who knows the explanation would make me very grateful. I've tried >>> this with other Windows apps too, and the same weirdness seems to occur. Larry Hall: >>All of the above is consistent with bash shell quoting. No, it's really not. Those backslashes should be long gone by the time cmd.exe gets its arguments, yet it echoes them. It seems that the Cygwin version of bash stops short before doing some of the work it normally does itself on other systems, assuming the executed command will have its command line run through the preprocessor in the Cygwin DLL. -- Mark J. Reed -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple