🚀 go-pugleaf

In article <1991Jan25.050215.10623@csn.org>, rademach@tramp.Colorado.EDU
(Simon Rademacher) writes:
|> In article <9101241631.AA17699@acf4.NYU.EDU> lixj@acf4.NYU.EDU
(Xiaojian Li) writes:
|> >I recently compiled Xemasc18.56.1 on IBM/RS6000 320. It works well
under
|> >ksh, but seems to have trouble under csh: the starting dir is always
~/
|> >no matter which directory I invoke xemacs from. Does anybody have
the
|> >same problem?
|> 
|> 
|> Isn't that funny, I just made a similar post.  For me the problem
occurs with
|> tcsh and sh.  Don't have ksh to try it with.
|> -- 

I have observed a problem (on SunOS 4.*) where if you are in csh, and
you
start a tcsh, then emacs will behave as described above (basically, it
thinks
you are in the directory that was the current directory when the tcsh
was
started).  I eventually determined that csh maintains a PWD environment
variable
which is always set to the path of the current directory; tcsh does not
do
anything with PWD (it neither changes it nor creates one if one does not
exist).
However, emacs apparently believes this variable if it is there.  My
solution
(besides not using csh when I can avoid it) was to add "unsetenv PWD" to
my
.cshrc.

I suspect your problem may be related, if not identical.  I hope this
helps...

							chris