From: Pedro Alves <palves@redhat.com>
To: Hannes Domani <ssbssa@yahoo.de>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Improve/fix the TUI's current source line highlight
Date: Mon, 18 Mar 2019 14:45:00 -0000 [thread overview]
Message-ID: <bfed778f-0208-c01a-21bf-034f26d59c5f@redhat.com> (raw)
In-Reply-To: <844158233.10369297.1552841197833@mail.yahoo.com>
On 03/17/2019 04:46 PM, Hannes Domani via gdb-patches wrote:
> Am Sonntag, 17. März 2019, 17:07:46 MEZ hat Eli Zaretskii <eliz@gnu.org> Folgendes geschrieben:
>>> Date: Fri, 15 Mar 2019 16:38:37 +0000 (UTC)> > From: "Hannes Domani via gdb-patches" <gdb-patches@sourceware.org>> > > > Also, I had to add the following to make it work on windows> > (but beware, I'm using pdcurses, not ncurses, and I don't know if ncurses> > for windows needs this as well):>
>> Ncurses doesn't need this.>
>>
>>> --- a/gdb/tui/tui-io.c> > +++ b/gdb/tui/tui-io.c> > @@ -369,6 +386,17 @@ apply_ansi_escape (WINDOW *w, const char *buf)> > > > Â Â if (reverse_mode_p)> > Â Â Â Â {> > +#if defined(__MINGW32__)> > +Â Â Â Â Â if (style.get_foreground ().is_basic ()> > +Â Â Â Â Â Â Â Â && style.get_foreground ().get_value ()> > +Â Â Â Â Â Â Â Â == (ncurses_norm_attr & 15))> > +Â Â Â Â Â Â style.set_fg (ui_file_style::NONE);> > +Â Â Â Â Â if (style.get_background ().is_basic ()> > +Â Â Â Â Â Â Â Â && style.get_background ().get_value ()> > +Â Â Â Â Â Â Â Â == ((ncurses_norm_attr >> 4) & 15))> > +Â Â Â Â Â Â style.set_bg (ui_file_style::NONE);> > +#endif> > +>
>> Could you describe what happens with pdcurses if you don't make this> change? It's strange that pdcurses cannot use explicit color> specification if the color is the default one.
> Actually, you can disregard that.
> Before you added that fix for windows, I found a different workaround,it was to set the "normal" color in esc.style to gray.
> I forgot that I did that, and it backfired now.So I removed that again, and everything is fine now even without that above change.
> Sorry for the noise.
No worries, thanks for following through and for testing.
The patch is in master and 8.3 branch now.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-03-18 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2019-03-15 21:41 ` Tom Tromey
[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
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=bfed778f-0208-c01a-21bf-034f26d59c5f@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
/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