I'd prefer a more general fix, then. Would an `unset CDPATH' near the beginning of the script do the trick?
Index: src/sanity.sh =================================================================== RCS file: /cvsroot/cvs/ccvs/src/sanity.sh,v retrieving revision 1.1198 diff -u -p -r1.1198 sanity.sh --- src/sanity.sh 10 Sep 2008 17:53:46 -0000 1.1198 +++ src/sanity.sh 11 Sep 2008 13:55:27 -0000 @@ -98,6 +98,9 @@ checklongoptarg() # required to make this script work properly. unset CVSREAD +# Bash sometimes echoes the path when CDPATH is set. +unset CDPATH + # This will cause malloc to run slower but should also catch some common errors # when CVS is linked with glibc 2.x. MALLOC_CHECK_=2; export MALLOC_CHECK_ Paul Edwards wrote: >> This is an easy enough fix to install, but why in the world would `cd >> dir' echo and yet `cd ./dir' does not? > > I think that is bash's behaviour. If you do a "cd xyz" then it could > either search your CDPATH and find any directory that has "xyz" > in it, or it could go to ./xyz. It echoes regardless to let you know > where you ended up. > > If you put an explicit path, it doesn't echo, because you know > that your CDPATH wasn't searched. > > It probably has something to do with the fact that that bit of > sanity.sh is executing a shell within a shell, so probably reads > my .bashrc or something like that. > > BFN. Paul. Regards, Derek -- Derek R. Price Solutions Architect Ximbiot, LLC <http://ximbiot.com> Get CVS and Subversion Support from Ximbiot! v: +1 248.835.1260 f: +1 248.246.1176 _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
