Non-login config files

[Steven Rezsutek <S.Rezsutek@baloo.gsfc.nasa.gov>]

In our last episode, Harald said:

> I would like to restart an old discussion about whether or not a 
> non-login es should read a config file upon startup. 

I've never missed this (non-login configs), and in fact, as a sysadmin
who sometimes has to help csh users along, it has sometimes shown itself
to be a pain when people "fix" something in the "wrong" file and then don't
get consistant behavior in all their shells.

As far as es goes, I've found the current way of doing things, coupled
with the autoloaded functions to be more than adequate.  Multiple config
files is just one more thing to bother with, IMHO. To illustrate:

The first line of my .xsession is "#!/bin/es -lop", so everything is set 
up in the environment before any apps/shells are started.  "Pure" stuff
goes in .esrc, and "X-only" stuff, like my rxterm function, go in autoload
functions.  Things work fine, be it from an Xterminal, an rsh, or a dialup.

If I happen to have created a sub environment by loading in various functions,
and start off an emacs, it's all right there.  If I have to make adjustments 
to path, or whatever, I only need change one file.  Of course, the goodies 
don't go along if I rxterm to another machine, but that's Unix's fault, not
es's. ;-) 

This being said, I humbly submit my "Nay" vote.

Oh, and welcome back Paul. :-)


Steve

...................................................................
Steven Rezsutek			      Steven.M.Rezsutek.1@gsfc.nasa.gov
Nyma / NASA GSFC Code 735.2	      Vox: +1 301 286 0897