This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: /usr/bin tools and directories with backslashes
- To: "Jeffrey Twu" <jctwu at CSUA dot Berkeley dot EDU>, <cygwin at cygwin dot com>
- Subject: Re: /usr/bin tools and directories with backslashes
- From: "Michael A. Chase" <mchase at ix dot netcom dot com>
- Date: Fri, 6 Jul 2001 07:45:22 -0700
- References: <20010705205744.A73395@csua.berkeley.edu>
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" <jctwu@CSUA.Berkeley.EDU>
To: <cygwin@cygwin.com>
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/