Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<15024.62910.662998.88543@jupiter.akutech-local.de>
Date:	Thu, 15 Mar 2001 18:02:54 +0100
MIME-Version:	1.0
From:	Ralf Fassel <ralf AT akutech DOT de>
To:	cygwin <cygwin AT cygwin DOT com>
Subject:	Re: bash: difference between //c/ and c:/
In-Reply-To:	<71171405@toto.iv>

* Corinna Vinschen
| Bash is a UNIX shell. Why not using UNIX paths?

Because we use non-Cygwin programs which don't grok /cygwin pathnames.
Unfortunately, there is a world besides cygwin.

$ cl     t.c   -o t
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 11.00.7022 for 80x86
...
$ ./t /cygdrive/c/autoexec.bat c:/autoexec.bat
1: /cygdrive/c/autoexec.bat: fopen failed
2: c:/autoexec.bat: fopen succeeded

| Actually not C:/ is deprictaed but //c! The syntax is ambiguous
| since that could also address a SMB server. We may decide to
| eliminate that syntax for local drives completely in the future.

Uh, please don't... :-/ Aren't single letter SMB servers rather rare?

| Use the /cygdrive/c syntax instead.

As I described in another mail, this currently breaks my openssh
installation, so I stick with //c for now.

Plus, I surely don't want to clutter up my shell scripts with
`cygpath -w' when calling non-cygwin programs...

R, undecided

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -