Mail Archives: cygwin/2000/01/13/21:42:06
I've got GNU bash, version 2.02.1(2)-release (i586-pc-cygwin32) running
on Micros~1 WinNT 4.0 (service pack 5), on x86 hardware. (Actually, it's
in a computer lab at Dal. I've got Debian GNU/Linux potato on my own
computer :)
(I don't know if this bug still exists in the current version or has
already been reported. Sorry.)
When I invoke bash with c:jdk1.2.2\lib in the DOS %PATH%, it transforms
it into //cjdk1.2.2/lib. (note that having c:jdk... in your DOS path
doesn't actually work unless cwd=\. I'm not the admin of the NT
computers (thank God:) ... )
The bad part about having //cjdk1.2.2/lib in the PATH is that trying to
search it for command completion makes it wait for NT to timeout looking
for the network name, or something. Anyway, bash freezes for 30 seconds
and nothing you can do will unfreeze it sooner (^C, etc.). This also
happens when your run a command that isn't in the PATH before the broken
entry.
It seems to me that a %PATH% entry of c:foo is fundamentally incompatible
with the Unix way of doing things, since c:foo is \foo relative to
whatever the current directory on drive C is. However, Unix doesn't have
a cwd for each drive, so ./foo in your $PATH is different. I don't know
what the entry _should_ be tranformed to, but anything would be better
than //cfoo!
Thanks for the great software, I hope you can make it better :)
#define X(x,y) x##y
Peter Cordes ; e-mail: X(peter AT cordes DOT phys. , dal.ca)
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -