🚀 go-pugleaf

This really belongs in comp.windows.news...

gaudreau@juggler.East.Sun.COM (Joe Gaudreau (Dances with PostScript)) writes:

|> scairns@citib.com (Scott Cairns) writes:
|> =We're running SunOS 4.1 with OpenLook 2.0 window manager.
|> =
|> =I want to modify the OpenLook init.ps file so that I can
|> =check the value of an environment variable (in postscript
|> =language of course) and take appropriate action. 
|> =
|> =Something along the lines of:
|> =
|> =(1) get value of env variable (e.g. LOGO)
|> =
|> =(2) if (LOGO == 1) 
|> =
|> =        run some post-script file
|> =
|> =    else
|> =    
|> =        continue on
|> =
|> =Not knowing post-script and not finding any sample post-script
|> =code in the ~openwin directory that does something like this, I
|> =was hoping for some suggestions...

|> Piece of PS (actually NeWS):
|> 
|> (LOGO) getenv  1 eq {%ifelse
|> 	(somefilename) run
|> } if
|> 
|> %continue on...
|> 
|> Is this what you wanted?

Since the getenv operator returns an error if the environment
variable doesn't exist, ?getenv should be used instead to provide
a default.  Also, getenv returns a string, so a cvi should be
performed or a string compare should be done:

	(LOGO) (0) ?getenv (1) eq {
		(somefilename) run
	} if

should work.

				...jim