From: papresco@calum.csclub.uwaterloo.ca (Paul Prescod)
Subject: Re: Absolute file-path under bash (cygwin32)
17 Apr 1997 15:00:40 -0700
Approved: cygnus.gnu-win32@cygnus.com
Distribution: cygnus
Message-ID: <3356597A.BC767D7.cygnus.gnu-win32@calum.csclub.uwaterloo.ca>
References: <Pine.LNX.3.91.970417092755.263B-100000@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.0b3 [en] (Win95; I)
Original-To: gnu-win32@cygnus.com
X-Priority: 3 (Normal)
Original-Sender: owner-gnu-win32@cygnus.com

John D. Robertson wrote:
> 
> This is a perplexing problem because:
> 1) Pathname manipulating shell scripts will break if DOS conventions are
>    used.
> 2) Most of us hate DOS conventions.
> 3) DOS & Windows programs will not run without DOS conventions.

The above are all true.

> 4) Bash cannot know which way to translate for all cases.

Why not? If executables are marked (with ld) and pathnames are marked
(with $// or something), what's the problem?
 
> The optimal solution is to provide a Windows95/NT runtime environment under
> Linux, or Free BSD, etc.  

That doesn't really help us figure out what to do with gnu-win32 tools.
Even if such a thing were available, not everyone can choose their
operating system.

 Paul Prescod
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
