X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=3.4 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT X-Spam-Check-By: sourceware.org Date: Mon, 12 Dec 2011 21:09:48 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <986778300.20111212210948@mtu-net.ru> To: Dmitry Bolshakov , cygwin AT cygwin DOT com Subject: Re: it seems a bug inside cygwin in parsing command line with double quotes and backslashes In-Reply-To: <4EE60569.8040609@bridge-quest.com> References: <4EE60569 DOT 8040609 AT bridge-quest DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Greetings, Dmitry Bolshakov! > when launching cygwin's programs from within windows's cmd > if the command line parameter has two backslashes and is double quoted (e.g. a path to local network drive) > then inside cygwin's program the corresponding ARGV element has single backslash only > but without double quotes all is ok - both backslashes are kept You can start right there: http://sourceware.org/ml/cygwin/2011-06/msg00246.html > simple testcase Mine's simpler. -- WBR, Andrey Repin (anrdaemon AT freemail DOT ru) 12.12.2011, <21:08> Sorry for my terrible english... -- 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