Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [PATCH] Improve/fix the TUI's current source line highlight
Date: Mon, 18 Mar 2019 14:42:00 -0000	[thread overview]
Message-ID: <ccc92ffe-e5d2-1a6d-ecc9-833d16273db5@redhat.com> (raw)
In-Reply-To: <83va0hwl24.fsf@gnu.org>

On 03/17/2019 03:57 PM, Eli Zaretskii wrote:
>> From: Pedro Alves <palves@redhat.com>
>> Date: Thu, 14 Mar 2019 17:35:57 +0000
>>
>> This patch changes that to something that I find much more sensible --
>> only reverse the default foreground/background colors, leave styled
>> text colors alone.  If the foreground color is not the default (because the
>> text was styled), leave the foreground color as is.  If
>> e.g., the terminal is fg=BLACK, and bg=WHITE, and the style wants to
>> print text in RED, reverse the background color (print in BLACK), but
>> still print the text in RED.
>>
>> I've attached screenshots of before/after patch, with both
>> white-on-black (actually, linux-colors / grey-ish-on-black),
>> and black-on-white themes in my console (konsole).  Also attached
>> screenshots with styling disabled, so that you can see how the
>> after-patch versions look more like the unstyled output.
>>
>> Note: The new ui_file_style::set_fg method isn't called set_foreground
>> instead, because set_foreground is a macro in /usr/lib/term.h (ncurses).
>>
>> WDYT?  
>>
>> Eli, could you try this on Windows, see if it behaves as intended there?
> 
> Tested on MS-Windows, works fine.  I think you should push this.

Great, thanks.  I've merged this to master and branch, with the bool fixed.

Pedro Alves


  reply	other threads:[~2019-03-18 14:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <24ebd86d-ac47-bc8d-042a-e29ae2b4301e@redhat.com>
2019-03-14 19:49 ` Eli Zaretskii
2019-03-14 20:14   ` Pedro Alves
2019-03-17 15:57 ` Eli Zaretskii
2019-03-18 14:42   ` Pedro Alves [this message]
2019-03-14 17:47 Pedro Alves
2019-03-14 19:55 ` John Baldwin
2019-03-14 20:10   ` Pedro Alves
2019-03-15 16:39 ` Hannes Domani via gdb-patches
2019-03-15 16:45   ` Pedro Alves
2019-03-17 16:07   ` Eli Zaretskii
2019-03-17 16:46     ` Hannes Domani via gdb-patches
2019-03-17 16:53       ` Eli Zaretskii
2019-03-18 14:45       ` Pedro Alves
2019-03-15 21:41 ` Tom Tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ccc92ffe-e5d2-1a6d-ecc9-833d16273db5@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox