Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!killer!elg
From: elg@killer.UUCP (Eric Green)
Newsgroups: comp.sources.bugs
Subject: Re: Jove bug
Message-ID: <4071@killer.UUCP>
Date: 13 May 88 06:09:55 GMT
References: <321@syntron.UUCP>
Organization: The Unix(R) Connection, Dallas, Texas
Lines: 29

> In article <4022@killer.UUCP> elg@killer.UUCP (Eric Green) writes:
> <System: AT&T 3b2, running Sys V.3
> <Software: Jove 4.9, as recently posted to comp.unix.sources
> <problem: The PWD environment variable is read to find out what
> <the current working directory is. Unfortunately, the version of csh
> <that I am using does not maintain the PWD environment variable. Since csh was

I "solved" the problem simply by commenting out the getenv("CWD") and
getenv("PWD") calls, and falling through into the getcwd() call. But that's no
permenant solution. Perhaps we need an #ifdef NOENV or something like that
(gawd, yet another variable in tune.h!). 

It's not a bug in csh. csh doesn't need fixing (though Sys V does :-).  csh
isn't supposed to maintain the "PWD" environment variable.  If csh was my
login shell, that would be no problem -- there would be no "PWD" environment
variable, and Jove would fall through into the getcwd().  Unfortunately, I am
constrained by events beyond my control to log in using sh or ksh as my
initial login shell -- which creates a PWD environment variable, which is
passed to csh, which is passed to Jove, which does the wrong thing.

Perhaps this cute attempt to be efficient should be excised completely from
the Jove code? Too bad I can't reach jpayne (unless he didn't graduate, after
all -- last I heard, he should be walking down that aisle in Rochester, funny
cap on head, tripping over a silly gown). 

---
    Eric Lee Green                     {cuae2,ihnp4}!killer!elg
         Snail Mail P.O. Box 92191 Lafayette, LA 70509              
"Is a dream a lie that don't come true, or is it something worse?"