Using ksh set -u breaks xinit script...

[Bob Andrews]

In article <1991Mar28.153242.8791 at panix.uucp>, eravin at panix.uucp (Ed Ravin) writes:
|> In article <mumble at arnor.uucp> prener at prener.watson.ibm.com (Dan Prener) writes:
|> >If all uses of undefined shell variables are to be considered errors,
|> >then it becomes very difficult to get first-time switches and to
|> >keep other state.
|> 
|> It's not at all difficult.  The first time you reference any shell variable,
|> you can specify a value to be used instead if the variable is not set or a
|> value to assign it to if the variable is not set.  For example:
|> 

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...

-- 
---

Bob Andrews         UNIX: bob at ibmpa.awdpa.ibm.com
                    VNET: BANDREWS at AUSTIN (if you must)