Hi,

I have the need to change my terminal's (text-mode) normal colors
to white text on blue background.  Using "setterm" does the above;
but it's impermanent.  Programs using ncurses upon exit reset the
terminal to normal, which is white-on-black: this is *not* what
I want.

Any and all help will be appreciated.
--
Louis-ljl-{LLaB...@siue.edu | l...@minuet.siue.edu}

Louis J. LaBash Jr. (lo...@LCJones.aclib.siue.edu) wrote:
: Hi,
: I have the need to change my terminal's (text-mode) normal colors
: to white text on blue background.  Using "setterm" does the above;
: but it's impermanent.  Programs using ncurses upon exit reset the
: terminal to normal, which is white-on-black: this is *not* what
: I want.
: Any and all help will be appreciated.

        Well, assuming you're using BASH as your shell, you could set the
colors of your prompt (via the PS1 and PS2 environment variables) using
ANSI color escape characters.

        For example, to have all your text at the shell prompt display in
white on blue, you could do something like this:

        export PS1="\033[0;37;44m"

The "\033" is the octal code for the ESCape character (ASCII 27).  The
"[0;37;44m" part is the ANSI code to change the color to normal attribute
(0), white foreground (37), and blue background (44).  The "m" is the
color command, I suppose.  I have the ANSI codes in the back of my old
MS-DOS manual.

        This is assuming, also, that you have your terminal set to a
terminal that understands ANSI escape sequences.  The default, Linux (in
SlackWare, anyways), supports them.

--
===============================================================================
Arcadio Alivio Sincero, Jr.
Sophomore, Computer Science Major at the University of Maryland at College Park
Amateur competitive bodybuilder
Email: l...@wam.umd.edu, WWW: <coming soon to a web site near you!>

"D.A.R.E. .... to keep cops off donuts."

On 3 Nov 1996 12:10:09 GMT, T.E.Dickey <dic...@clark.net>
wrote:

I am very familiar with this problem.  The next version of slang
(0.99-36) will look for an environment variable called COLORFGBG whose
value is assumed to consist of a foreground color name and a
background color name separated by a semi-colon, e.g.,

    setenv COLORFGBG "green;black"

I am not sure how well this solution will work in practice.
--
John E. Davis                   Center for Space Research/AXAF Science Center
617-258-8119                    MIT 37-662c, Cambridge, MA 02139
http://space.mit.edu/~davis

In article <slrn57nm8p.ec.gjohn...@dream.season.com>,
Reality is a point of view <gjohn...@dream.season.com> wrote:

Try changing op in your terminfo description to match your defaults. It is
set to white-on-black by default.

Zeyd
--
---
Zeyd M. Ben-Halim       zmben...@netcom.com
NCURSES is available from ftp.netcom.com:pub/zm/zmbenhal/ncurses
Current version is 1.9.9e

In article <slrn57n9gc.b4p.lo...@lcjones.aclib.siue.edu>,
Louis J. LaBash Jr. <lo...@LCJones.aclib.siue.edu> wrote:

  There are two things I've changed in terminfo for the console.
  I believe that the rs1 string is incorrect -- I set it to
  rs1=\Ec -- and the op string incorrectly sets the console to
  white on black instead of restoring the original colors. I
  have set this to op=\E[m\017, which from looking at the kernel
  source I believe to be the correct solution.

  I don't run white on blue, but I do run cyan on black, and spent
  a lot of time hacking ncurses to make it work for me before I
  twigged onto the little detail of terminfo being wrong.

                ____
  david parsons \bi/ o...@pell.chi.il.us
                 \/

l...@wam.umd.edu (Arcadio Alivio Sincero) writes:

Here's the solution I discovered, which I believe will address your problem:
use the '-store' flag with setterm when you change colors.  Something like
this

        setterm -foreground white -background blue -store

This makes the settings quite permanent--they'll even last through a logout.

--
Mike Coleman                                  http://ctr.cstp.umkc.edu/~coleman
       "I would rather spend 10 hours reading someone else's source code
       than ten minutes listening to Musak waiting for technical support
         which isn't." --Dr. Greg Wettstein, Roger Maris Cancer Center