cello
Registered
This is a very strange problem that I'm having (this is running Jaguar). It seems as though when using bash, environment variable bindings are simply not recognized by any other command. For example, if you use cvs, and want to set the CVSROOT variable, typing CVSROOT=:ext:user@foo.com:/foo/bar will allow you to see the variable when you echo $CVSROOT, but for some reason the cvs command doesn't recognize that it's there:
cvs update: No CVSROOT specified! Please use the `-d' option
cvs [update aborted]: or set the CVSROOT environment variable.
This doesn't only apply to cvs, it also applies to every other program that uses environment variables _for example, setting the DISPLAY variable doesn't get recognized when you try to run something on an XServer. There are other examples, but I'm sure you can just trust me that it's not an issue with these commands and instead an issue with, well, something else.
Anyhow, running tcsh will resolve these problems, but tcsh sucks. On another note, perhaps I would run tcsh if it did command completions and directory completions correctly on Darwin. Does anyone know of a patch that makes that stuff work properly?
cvs update: No CVSROOT specified! Please use the `-d' option
cvs [update aborted]: or set the CVSROOT environment variable.
This doesn't only apply to cvs, it also applies to every other program that uses environment variables _for example, setting the DISPLAY variable doesn't get recognized when you try to run something on an XServer. There are other examples, but I'm sure you can just trust me that it's not an issue with these commands and instead an issue with, well, something else.
Anyhow, running tcsh will resolve these problems, but tcsh sucks. On another note, perhaps I would run tcsh if it did command completions and directory completions correctly on Darwin. Does anyone know of a patch that makes that stuff work properly?