🚀 go-pugleaf

From article <CMOORE.92Jul24092902@zenobia.mit.edu>, by cmoore@zenobia.mit.edu (Christopher B. Moore):
> 
> I've noticed (while installing the Auc-TeX package) that evaluation of
> (getenv "HOSTTYPE") in an Emacs2.1 window started by clicking on the
> Emacs2.1 icon in the workspace returns nil.  However, in an Emacs2.1
> window started from the commandline it returns "next".  What gives?
> 
> Christopher B. Moore
> cmoore@maggie.mit.edu


	Well, the problem is that the  workspace does not  run your .login or
your .cshrc.   So programs  started from it  will not  have access  to   your
favorite environment variables. One fix is to add the following lines to your
.emacs file:

(setq process-environment (append
        process-environment
	'("HOSTTYPE=next" "OTHERVAR=othervalue" [more of these])))


-- 
/***************************************************************************\
|* Patrice Belleville 					 patrice@cs.sfu.ca *|
|*   --- Simon Fraser University is not responsible for my mistakes. ---   *|
\***************************************************************************/

Christopher B. Moore writes
> I've noticed (while installing the Auc-TeX package)
> that evaluation of (getenv "HOSTTYPE") in an Emacs2.1
> window started by clicking on the Emacs2.1 icon in the
> workspace returns nil.  However, in an Emacs2.1 window
> started from the commandline it returns "next".  What
> gives? 

Why, environment variables aren't global - they are inherited. And the parent  
of all programs started by the Workspace is (surprise !) Workspace. And  
Workspace does not have any environment variables set. If you start a NeXTstep  
program directly from the commandline its parent is the shell so your  
application inherits all the shell environment variables. (BTW, the better way  
to do this is not to start applications directly from the command line but  
instead to tell Workspace to do it from the command line, see man page on  
open(1)).

EPS wrote a hack to get enviroment variables for the Workspace which involved  
installing a shell script as Workspace replacement. This shell script then sets  
the environment variables and execs the real Workspace.

	Carl Edman