browning@nas.nasa.gov (David S. Browning) (10/17/90)
Using: IRIS 4D/60, IRIX 3.2 (4Sight 1.4, if that's significant)
I'm confused about the path used for forkunix or seqfork NeWS
commands. I was doing the "exercise" in the _4Sight Programmer's
Guide_, Section 3 ("Programming the IRIS Window Manager"), Chapter 4
("Customizing the IRIS Window Manager"). Copy /usr/sbin/toolchest
into your home directory and modify it, and the "Tools" toolchest menu
has your modification in it. But put it in ~/bin, and it won't work
(the default /usr/sbin/toolchest gets used instead). How can I fix
the path used by forkunix/seqfork? I tried to put ~/bin in my path in
both .cshrc and .profile, but no luck. Am I trying the right thing,
and just not doing it correctly? There must be some way to put these
customized psh scripts somewhere other than my home directory!
Thanks.
-- David
|============================================================================|
| Internet: browning@wilbur.nas.nasa.gov Phone: (415) 604-4321 |
| UUCP: {hplabs, mailrus, ucbvax, etc.}!ames!amelia!browning |
|----------------------------------------------------------------------------|
|"the nice thing about true hopelessness is that you don't have to try again"|
| -- jules shear |
|============================================================================|scotth@harlie.corp.sgi.com (Scott Henry) (10/17/90)
In article <1990Oct17.015814.26771@nas.nasa.gov>, browning@nas.nasa.gov (David S. Browning) writes: |> |> I'm confused about the path used for forkunix or seqfork NeWS |> commands. I was doing the "exercise" in the _4Sight Programmer's |> Guide_, Section 3 ("Programming the IRIS Window Manager"), Chapter 4 |> ("Customizing the IRIS Window Manager"). Copy /usr/sbin/toolchest |> into your home directory and modify it, and the "Tools" toolchest menu |> has your modification in it. But put it in ~/bin, and it won't work |> (the default /usr/sbin/toolchest gets used instead). How can I fix |> the path used by forkunix/seqfork? I tried to put ~/bin in my path in |> both .cshrc and .profile, but no luck. Am I trying the right thing, |> and just not doing it correctly? There must be some way to put these |> customized psh scripts somewhere other than my home directory! |> Thanks. There are two ways to fix this. One of them involves modifying your ~/user.ps, the other is modifications to ~/.cshrc and ~/.login. ~/user.ps: add to the top of your user.ps a line like: (PATH) getenv dup (/usr/people/browning/bin:/usr/local/bin:/usr/bin/X11:) exch append (PATH) exch putenv or (PATH) ( *the PATH you want NeWS commands to have* ) putenv NeWS reads in your ~/.cshrc and ~/.login when it starts up, but aborts processing if it detects any errors, such as terminal I/O (stty, cat, echo, tset(?), etc). If you surround all of these with the lines: if ( ! $?ENVONLY ) then .... endif 4sight (NeWS) will use the path defined in your ~/.cshrc for the forkunix, etc commands. -- Scott Henry <scotth@sgi.com> / Traveller on Dragon Wings Information Services, / Help! My disclaimer is missing! Silicon Graphics, Inc / 'Under-achiever and proud of it!' -- Bart Simpson
blbates@AERO4.LARC.NASA.GOV ("Brent L. Bates AAD/TAB MS361 x42854") (10/19/90)
All the "chests" are executed from init.ps. I have made a directory
~/NeWS and in this directory I have the following files:
init.ps litewin.ps systemchest toolchest toolchest.ps user.ps
The system will check for init.ps in ~/NeWS first. I changed
init.ps so that references to the above files have a NeWS/ in front
of them. I don't think .cshrc is executed until after all the 4Sight
stuff is finish, so putting a directory in you path wont have any effect
on NeWS items.
Hope this helps.
P.S. *.ps files are in /usr/NeWS/lib/NeWS and the chests are in
/usr/sbin
--
Brent L. Bates
NASA-Langley Research Center
M.S. 361
Hampton, Virginia 23665-5225
(804) 864-2854
E-mail: blbates@aero4.larc.nasa.gov or blbates@aero2.larc.nasa.gov