Re: cygwin bash groks PATH wrong

Re: cygwin bash groks PATH wrong

[Earnie Boyd]

The pathing routines have been rewritten.  Either download a snapshot or buy
the CD version to get these changes.  //c/ is nolonger what happens.  Report
your bug against what is current please.

Earnie.

--- Peter Cordes <peter@Cordes.Phys.Dal.Ca> wrote:
> On Fri, 14 Jan 2000, Bob McGowan wrote:
> 
> > Peter,
> > 
> > I don't think this can qualify as a bug.  Though relative paths don't
> > really make sense in either the DOS/Windows world or the UNIX world, you
> > can change your path to include them.  I think this is true also on
> > DOS/Windows, with the added issue of drives and their current directory
> > concepts.  This means for DOS I could have a directory with no drive
> > letter, so it is only valid when the drive it is on is current.
> 
>  I'd agree with that, except that I think it is a bug because there
> is no way //cfoo can be considered correct.  Maybe cygwin (or bash,
> whichever one is doing the dos->unix style path translation) should
> translate c:foo to a simple relative PATH of foo, dropping the drive
> letter.  This is right sometimes, and avoids putting a bogus UNC name in
> the PATH.  Even better would be to print a warning before doing this, so
> the user could fix their (probably typo'd) DOS path.
>  
> > Do you have any control over the local computer you are running bash
> > on?  You may be able to effect some repair in the Control
> > Panel->System's environment tab.  If not, you should have complete
> > control over your personal setup of Cygwin and should be able to either
> > set the PATH exactly as you like in your .profile or .bashrc (i.e. don't
> > put a $PATH on the right side), or even run the existing DOS/Windows
> > path through sed or awk to munge it up the way you need it.
> 
>  Luckily, the CS help desk listens to bug reports, and fixed their typo in
> the DOS path.  :)
> 
>  Thanks,
> 
> #define X(x,y) x##y
> DUPS Secretary ; http://is2.dal.ca/~dups/
> Peter Cordes ;  e-mail: X(peter@cordes.phys. , dal.ca)
> 
> "The gods confound the man who first found out how to distinguish the hours!
>  Confound him, too, who in this place set up a sundial, to cut and hack
>  my day so wretchedly into small pieces!" -- Plautus, 200 BCE
> 
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 
> 
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: cygwin bash groks PATH wrong

[Peter Cordes]

On Fri, 14 Jan 2000, Bob McGowan wrote:

> Peter,
> 
> I don't think this can qualify as a bug.  Though relative paths don't
> really make sense in either the DOS/Windows world or the UNIX world, you
> can change your path to include them.  I think this is true also on
> DOS/Windows, with the added issue of drives and their current directory
> concepts.  This means for DOS I could have a directory with no drive
> letter, so it is only valid when the drive it is on is current.

 I'd agree with that, except that I think it is a bug because there
is no way //cfoo can be considered correct.  Maybe cygwin (or bash,
whichever one is doing the dos->unix style path translation) should
translate c:foo to a simple relative PATH of foo, dropping the drive
letter.  This is right sometimes, and avoids putting a bogus UNC name in
the PATH.  Even better would be to print a warning before doing this, so
the user could fix their (probably typo'd) DOS path.
 
> Do you have any control over the local computer you are running bash
> on?  You may be able to effect some repair in the Control
> Panel->System's environment tab.  If not, you should have complete
> control over your personal setup of Cygwin and should be able to either
> set the PATH exactly as you like in your .profile or .bashrc (i.e. don't
> put a $PATH on the right side), or even run the existing DOS/Windows
> path through sed or awk to munge it up the way you need it.

 Luckily, the CS help desk listens to bug reports, and fixed their typo in
the DOS path.  :)

 Thanks,

#define X(x,y) x##y
DUPS Secretary ; http://is2.dal.ca/~dups/
Peter Cordes ;  e-mail: X(peter@cordes.phys. , dal.ca)

"The gods confound the man who first found out how to distinguish the hours!
 Confound him, too, who in this place set up a sundial, to cut and hack
 my day so wretchedly into small pieces!" -- Plautus, 200 BCE


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: cygwin bash groks PATH wrong

[Bob McGowan]

Peter,

I don't think this can qualify as a bug.  Though relative paths don't
really make sense in either the DOS/Windows world or the UNIX world, you
can change your path to include them.  I think this is true also on
DOS/Windows, with the added issue of drives and their current directory
concepts.  This means for DOS I could have a directory with no drive
letter, so it is only valid when the drive it is on is current.

Do you have any control over the local computer you are running bash
on?  You may be able to effect some repair in the Control
Panel->System's environment tab.  If not, you should have complete
control over your personal setup of Cygwin and should be able to either
set the PATH exactly as you like in your .profile or .bashrc (i.e. don't
put a $PATH on the right side), or even run the existing DOS/Windows
path through sed or awk to munge it up the way you need it.

Bob

PETER JOHN CORDES wrote:
> 
>  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@cordes.phys. , dal.ca)
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan@veritas.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

cygwin bash groks PATH wrong

[PETER JOHN CORDES]

 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@cordes.phys. , dal.ca)


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com