From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 114994 invoked by alias); 4 Mar 2019 16:04:20 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 114978 invoked by uid 89); 4 Mar 2019 16:04:19 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=avail, pairs, consoles, Hx-languages-length:1354 X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 04 Mar 2019 16:04:18 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:57746) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h0q4e-0004bc-RM; Mon, 04 Mar 2019 11:04:16 -0500 Received: from [176.228.60.248] (port=4682 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1h0q4e-0005GP-F4; Mon, 04 Mar 2019 11:04:16 -0500 Date: Mon, 04 Mar 2019 16:04:00 -0000 Message-Id: <83tvgieidf.fsf@gnu.org> From: Eli Zaretskii To: tom@tromey.com CC: gdb-patches@sourceware.org In-reply-to: <83r2brhw8k.fsf@gnu.org> (message from Eli Zaretskii on Fri, 01 Mar 2019 09:47:23 +0200) Subject: Re: [PATCH 00/16] Add styling to the gdb CLI and TUI References: <20181128001435.12703-1-tom@tromey.com> <83k1kxfzwo.fsf@gnu.org> <8736rja4i8.fsf@tromey.com> <83r2brhw8k.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00034.txt.bz2 > Date: Fri, 01 Mar 2019 09:47:23 +0200 > From: Eli Zaretskii > CC: gdb-patches@sourceware.org > > > Eli> Will the Windows TUI build support styling out of the box? It uses > > Eli> ncurses. > > > > I think it should work, but you'd have to "set style enabled on" first. > > For the record, it doesn't work in GDB 8.2.90, even after I disabled > the test for $TERM being defined in the environment. I will try to > find out why at some point. OK, I now know why. The colors do work, but only if the style specifies both the foreground and the background colors explicitly; specifying just one of them causes no colors at all (but other attributes, like intensity, do still work). I think this means that the MS-Windows console belongs to the devices which don't support resetting to the default colors. I even tried to add the call to assume_default_colors, per the ncurses docs, to no avail. Are there any other consoles out there with such an issue? In any case, I think we should at least tell in the manual that on some systems the color pairs need to be specified completely, even if only one of the two colors changes from the default. Does anyone have ideas how to do better than just documenting this? Let the user define the default fore- and back-ground colors, perhaps?