X-Spam-Check-By: sourceware.org Message-ID: <4567B5AA.2E5F1BF9@dessent.net> Date: Fri, 24 Nov 2006 19:16:58 -0800 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Terminal background color References: <8CCA05D099E31144ADF2A24010B5A2B2346EB5 AT MS01 DOT elca DOT ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT 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/