Different colors per user

Joe Chasan joe at magnatechonline.com
Wed Feb 20 19:36:28 PST 2008


On Wed, Feb 20, 2008 at 06:48:34PM -0500, Brian K. White wrote:
> 
> ----- Original Message ----- 
> From: "Kenneth Brody" <kenbrody at bestweb.net>
> To: <joe at magnatechonline.com>
> Cc: <filepro-list at lists.celestial.com>
> Sent: Wednesday, February 20, 2008 6:22 PM
> Subject: Re: Different colors per user
> 
> 
> > Quoting Joe Chasan (Wed, 20 Feb 2008 18:14:24 -0500):
> > 
> >> On Wed, Feb 20, 2008 at 05:32:24PM -0500, Brian K. White wrote:
> > [...]
> >>> Just TEXTNORMAL=0x... export TEXTNORMAL in the environment by any   
> >>> scheme you want before calling the top level menu. ie: ~/.profile ,
> > [...]
> >> no such luck, that was the first thing i tried (though checked runmenu and
> >> clerk, not dscreen) - colors in enviroment got overriden by those in
> >> ../fp/lib/config.
> > 
> > Environment variables override config file settings.  Double-check your
> > settings.
> 
> You know, it's weird, in reaction to this, which I _know_ works because we do it all the time as I said, I tried it again manualy, using p and runmenu instead of dscreen just to be sure, and I'll be dipped if it didn't work for me either the first few times.
> 
> I think it was the semicolon. I didn't put one in my example, and I have some scripts that do work that don't have a semicolon in that spot, but I think they must all happen to be bash, vs sco's stock plain sh or even ksh.
> 
> But after nailing it down without any possibility of guessing, unsetting everything so I don't have any possible duplicate variables with different cases so I don't have both a MENUNORMAL and a MenuNormal, and verifying with:
> # sh    # become a child to prove we exported not just set
> 
> # set |egrep -i "(normal|inverse)"
> 
> MenuNormal=0x40
> 
> # runmenu
> 
> I definitly does work.
> 
> I change that number and get the appropriate color every time.
> 
> Same for other variables. Haven't tried nailing down what case conflicts do, other things to do...

That was it, it was the case!  Thanks Brian!

If I have the variables in ALL CAPS as they are in the config file, 
it does not work.  The config overrides the shell/environment variables.

If, however, I have them mixed case e.g. TextNormal=0x40 - even though
config has it as TEXTNORMAL=0x86, it does work.

Ken?
 
--
-Joe Chasan-                           Magnatech Business Systems, Inc.
joe - at - magnatechonline -dot- com   Hicksville, NY - USA
http://www.MagnatechOnline.com         Tel.(516) 931-4444/Fax.(516) 931-1264


More information about the Filepro-list mailing list