Using ksh set -u breaks xinit script...

[Ed Ravin]

In article <mumble at ibmpa.awdpa.ibm.com> bob at ibmpa.awdpa.ibm.com
(Bob Andrews) writes:
>You might also try changing the first line of the xinit script to:
>
>#! /bin/ksh -p
>
>I haven't tried this, so it may introduce other errors, but it should prevent
>the ksh from looking at your .profile, etc. files...

Hmmm.  This is the first system I've used that uses ksh as its default
shell, so the system scripts are picking up my .kshrc.  Considering the
level of customization possible in ksh, and considering what some people
do to their environments, it's probably wise for all system scripts to insist
upon using only inheriting environment variables and not shell aliases or
option settings.

Since my last posting, I've discovered the "info" script also likes to
reference uninitialized variables.  Then again, the Info Explorer interface
from an ASCII terminal is so dismal that I'm not sure I care...

-- 
----------------------------------------------------------------------------
Ed Ravin            | Even if I could think of a profound, witty, insightful
cmcl2!panix!eravin  | quote to put here noone would bother reading it.
philabs!trintex!elr |