NeWS environment

Dan Wallach dwallach at soda.berkeley.edu
Mon May 13 06:59:41 AEST 1991


In article <1991May10.162810.14296 at cid.aes.doe.CA> psilva at cid.aes.doe.ca writes:
>wow!  It's timing related!  If I put a sleep in the .login
>the problem occurs in the good .login as well!
>
>How can you get NeWS to wait for the .login to finish?

It sounds to me like you're mixing apples and oranges.  You usually
want to do windowing things in your user.ps and specifically within-a-window
things in your .login/.cshrc.

For example, in a typical X setup, you treat your .login/.cshrc as if
you were just dialing in from home on your dumb terminal, and then you
have the .xsession or .xinitrc file which says what X programs you want.

In my environment, I have the .cshrc file from hell, which always gets
run, no matter what (especially true in X...) and a really tiny .login
file that I don't usually need run (does things like checks if I have mail
waiting for me...).

For things like popping up windows, I've edited my user.ps file to do the
stuff I want.  Here's an excerpt.
%%
%% User customization file.
%%

/RestartActions [ 
	{ (gamma 1.7) seqfork }		% 1.7 is a good first guess
	{ (demochest) seqfork }
% init_my_windows is really a shell script in my bin directory
% that way, I can check environment variables and have more
% customization of window titles...
	{ (init_my_windows) seqfork }
] def


If I were more of a PostScript whiz, I could probably do everything here,
but it was easier in a shell script.

This should solve your problem.

Dan Wallach
dwallach at soda.berkeley.edu



More information about the Comp.sys.sgi mailing list