X-Spam-Check-By: sourceware.org Date: Thu, 31 Aug 2006 10:02:23 -0700 From: George To: cygwin AT cygwin DOT com Subject: Re: Color Schemes Message-ID: <20060831170223.GA1392@home> Mail-Followup-To: cygwin AT cygwin DOT com References: <04d201c6cc93$1e0ec0e0$a501a8c0 AT CAM DOT ARTIMI DOT COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Thu, Aug 31, 2006 at 09:44:51AM -0500, mwoehlke wrote: > Dave Korn wrote: >> AFAIUI, the mapping of escape codes to which visual colours they mean >> is utterly fixed by ANSI, and it is, as you say, the termulator's job >> to display the correct visual colour. We could attempt in cygwin's >> console-handling code to look up the current console's current >> palette and attempt some kind of best-fit matching, at least in >> theory, but there's still the old SHTDI problem there.... > > [...] and I am not aware of any way to examine the terminal's > "palette", nor should you need to. If a user wants to fiddle with > these, it is his responsibility to keep things legible. Huh? $ grep color ~/.Xdefaults *color0: #000000 *color1: #D1BFB1 *color2: #99CCCC *color3: #C8B27F *color4: #8DB6CD *color5: #CC99CC *color6: #A8A8D9 *color7: #7697A7 *color8: #000000 *color9: #80A0B0 *color10: #99CCCC *color11: #40677A *color12: #8DB6CD *color13: #CC99CC *color14: *color15: #87CEFF *colorBD: #8DB6CD *colorUL: #C8B27F *cursorColor: #84A9A9 Or am I missing something? -- George -- 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/