Xref: utzoo comp.emacs:5207 comp.windows.x:7673
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ulowell!bbn!jr@bbn.com
From: jr@bbn.com (John Robinson)
Newsgroups: comp.emacs,comp.windows.x
Subject: Re: GNU Emacs shell mode and DISPLAY env variable
Message-ID: <35534@bbn.COM>
Date: 2 Feb 89 15:43:54 GMT
References: <35945@think.UUCP> <3195@xyzzy.UUCP>
Sender: news@bbn.COM
Reply-To: jr@bbn.com (John Robinson)
Followup-To: comp.emacs
Distribution: na
Organization: BBN Systems and Technologies Corporation, Cambridge MA
Lines: 14
In-reply-to: meissner@tiktok.dg.com (Michael Meissner)

In article <3195@xyzzy.UUCP>, meissner@tiktok (Michael Meissner) writes:
>Go into the source directory for emacs, and add a define to config.h
>for MAINTAIN_ENVIRONMENT, do a make clean, followed by a make.  If
>this is defined, emacs passes the entire environment to subprocesses.
>You can also do (setenv "variable" "value") then from within emacs.
>Note, the documentation for setenv is messed up....

I don't believe this is quite right.  Emacs always passes its
environment to its children.  MAINTAIN_ENVIRONMENT adds (setenv) so
that you can manipulate it.  (getenv) is there regardless.  I (and
others) have never understood why setenv is not always built-in.
--
/jr
jr@bbn.com or bbn!jr