From:	fjh AT cs DOT mu DOT OZ DOT AU (Fergus Henderson)
Subject:	Re: cygnus bugs
13 Jul 1997 21:42:38 -0700 :
Sender:	mail AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199707140254.MAA02915.cygnus.gnu-win32@mundook.cs.mu.OZ.AU>
References:	<199707121921 DOT JAA02783 AT haleakala DOT aloha DOT net> <199707130728 DOT RAA03575 AT murlibobo DOT cs DOT mu DOT OZ DOT AU> <33c8f0a3 DOT 1384462 AT world DOT std DOT com>
Original-To:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

franl AT world DOT std DOT omit-this DOT com (Francis Litterio) writes:

>[Fergus Henderson wrote:]
>
>> Tim Newsham <newsham AT aloha DOT net> writes:
>> 
>> >- cygwin does not properly transform command line path names across
>> >  mount points.  If I am on drive "D:" and type "vi /tmp/foo",
>> >  I end up editing "D:\tmp\foo" and not "C:\tmp\foo" even though
>> >  "/tmp" is on "C:".  (vi is not compiled with cygwin).
>> >  Cygwin should transform the path to "C:\tmp\foo" for the benefit
>> >  of non-cygwin applications.
>> 
>> How can cygwin know which arguments are pathnames and which are
>> just ordinary strings that should not be transformed in this manner?
>
>Cygwin can know because the strings that are pathnames are passed to
>open(), [...]

No, in the case that Tim Newsham was referring to, "vi is not compiled
with cygwin", and so the strings that are pathnames are not passed
to cygwin's open().

--
Fergus Henderson <fjh AT cs DOT mu DOT oz DOT au>   |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>   |  of excellence is a lethal habit"
PGP: finger fjh AT 128 DOT 250 DOT 37 DOT 3         |     -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -