Re: // in paths

1998-10-07 Thread E.L. Meijer \(Eric\)
> > When I type (in bash): > >% type foo > > it returns > >foo is /usr/local/bin//foo > > with two /'s before `foo'. (I get the same effect with `csh' and `which'.) > Has anyone else seen this behavior? Anyone know what's causing it? Or how to > fix it? > This is what you get if t

Re: // in paths

1998-10-07 Thread Bedrock LAN Administrator
yes, i've seen it: [EMAIL PROTECTED] /# cd etc/.. [EMAIL PROTECTED] //# cd etc/.. [EMAIL PROTECTED] /# and repeat this ad-nauseum can't explain this, though, as I've only seen this happen with debian! - DeJay. _ / Bedrock \__ | http://bedrock.dyn.ml.org/dejay

Re: // in paths

1998-10-07 Thread Ralph Winslow
When David S. Zelinsky wrote, I replied: I can't help with what causes it, but I can tell you that it's no big deal. /usr/local/bin//foo is equivalent to /usr/local/bin/foo (i.e. the double (or triple or whatever) slashes are the same as one slash). > > When I type (in bash): > >% type foo