Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<200204191543.VAA04230@sentry-lan.unibase.com>
To:	cygwin AT cygwin DOT com
From:	Milton Calnek <milton AT calnek DOT com>
Subject:	Double back slash. Was: Re: Why did you guys break EVERYTHING...
In-reply-to:	"Sat, 20 Apr 2002 12:58:28 +1000." "Robert Collins" <robert.collins@itdomain.com.au>
Date:	Fri, 19 Apr 2002 21:43:38 +0600

I was wondering if anyone else thinks d:\\foo is too complicated...
or rather that it could be simplifed to d:/foo.  Or if you made the
shell read :\ as :\ then we would have a more uniform interface...

Hmmm... I'm sure that this issue is more complicated than I understand
at this point.

I'm just remembering how much I appreciated it when samba made their
commands parse //host/share as well as \\\\host\\share.

In message <FC169E059D1A0442A04C40F86D9BA7600C5E90 AT itdomain003 DOT itdomain DOT net DOT au>, "Robert Collins" writes:
> As for the tools, by and large they all support d:\foo syntax as well -
> but remember, if you run them within bash, the \ becomes an escape
> character, so you need d:\\foo for the tool to see the backslash.
> 
> Rob
> 
> --
> 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/

--
Milton Calnek
milton AT calnek DOT com

Everything should be as simple as possible - but no simpler.
-- Albert Einstein as quoted by Peter G. Neumann in CHATS Principles

--
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/

- Raw text -