Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <008a01c1062a$b9911250$6464648a@ca.boeing.com> From: "Michael A. Chase" To: "Jeffrey Twu" , References: <20010705205744.A73395@csua.berkeley.edu> Subject: Re: /usr/bin tools and directories with backslashes Date: Fri, 6 Jul 2001 07:45:22 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 That would certainly be a start, but you can also use '/' instead of '\' in those strings. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. ----- Original Message ----- From: "Jeffrey Twu" To: Sent: Thursday, July 05, 2001 20:57 Subject: /usr/bin tools and directories with backslashes > I like to use Cygwin in a Win2K cmd.exe shell, and I have > C:\cygwin\bin in my PATH. I've noticed, though, that commands that I > use very frequently (mv, cp, rm, unzip) don't handle backslash ('\') > directory strings very well. For example, I tried to unzip foo.zip -d > \, and no files could be created. > > I presume this is normal behavior? And the advice is: "Stop > using cmd.exe and use {bash,tcsh}"? Please confirm. Thanks, much! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/