Message-ID: <4567B5AA.2E5F1BF9@dessent.net>
Date: Fri, 24 Nov 2006 19:16:58 -0800
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Terminal background color
References: <8CCA05D099E31144ADF2A24010B5A2B2346EB5@MS01.elca.ch> <Pine.GSO.4.63.0611242132050.17454@access1.cims.nyu.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Igor Peshansky wrote:

> Alternatively, use rxvt, which, like xterm, understands special sequences
> to dynamically change the background color of the window, among other
> things).  Rxvt also has the additional advantage that you can specify the
> background color programmatically on the command line, so you can create
> custom scripts/shortcuts for each machine.

The Windows console API also supports this ability of setting/changing
the colors programmatically, so in theory it should be possible to write
a very small launcher type .exe that parses xterm/rxvt-esque command
line parameters for fonts and colors and creates a Windows console to
the given specifications.  That is, if you absolutely had to have a
windows console.  Personally I would just use rxvt without a second
thought.

If you are okay with a really hackish solution you could also fiddle
with the registry, which is where the color settings for consoles are
stored (it's on a per-.exe name basis I think, which lets you set
different font/color settings based on which .exe the console was
launched for.)

But really, as Igor said I think just echoing the desired FG/BG color
change before starting the build or simply using rxvt would be simplest.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/