Article View: comp.sys.next.misc
Article #953How to give a program launched by Workspace an environment?.
From: Graham Stoney
Date: Wed, 08 Apr 1992 04:19
Date: Wed, 08 Apr 1992 04:19
33 lines
1656 bytes
1656 bytes
Can anyone give me an idea of a clean way to set environment variables in
programs launched from the workspace?. I'd like to do things like add
/usr/local/man to the MANPATH used by utilities->manual in Edit, and set
variables for use by Emacs.
I say "a clean way" because one of the local gurus has come up with this
neat, elegant, minimal, concise, ...... well, it is a solution I guess:
i. Create a file, say .workspacerc, that contains the
following....
#!/bin/sh
var=value export var
... (do other environment variables)
exec /usr/lib/NextStep/Workspace.app/Workspace $@
ii. Make sure the above file is executable...
chmod +x $HOME/.workspacerc
iii. Tell the Next login program what to run as Workspace...
dwrite loginwindow Workspace $HOME/.workspacerc
Any clues?
thanks,
Graham.
--
10 REM My Greatest Ever Programming Achievement, by Graham Stoney.
15 REM "The single most important environmental thing an Australian can do is
20 REM to not own a cat" (Serious comment included in .sig on a trial basis.)
30 FORK = 1 TO 100: PRINT "Well, I AM a Hardware Engineer!": NEXT SPOON
Technical Details
Message-ID:
<1992Apr8.041912.8116@research.canon.oz.au>Path:
arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!metro!mama!greyhamShow Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.misc Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!metro!mama!greyham From: greyham@research.canon.oz.au (Graham Stoney) Subject: How to give a program launched by Workspace an environment?. Message-ID: <1992Apr8.041912.8116@research.canon.oz.au> Organization: Canon Information Systems Research Australia Date: Wed, 8 Apr 1992 04:19:12 GMT Lines: 33