public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Phi Debian <phi.debian@gmail.com>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: Pedro Alves <palves@redhat.com>,
	 "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: TUI enhancement suggestion.
Date: Mon, 15 Jun 2020 18:56:10 +0200	[thread overview]
Message-ID: <CAJOr74iA-BJv24LoD5jJykMh_Kb6TH+U7kykpSPgia9WVF8Mtw@mail.gmail.com> (raw)
In-Reply-To: <314644177.1902979.1592236099059@mail.yahoo.com>

Hi Pedro and all,

I am really sorry but I lost my bandwith, I am starting a new job tomorow
leaving little room for investigation etc.

Regarding the point line, used to be inverse video on monochrome, i thought
it was kind of bizare with highlighted text because we don't have a uniform
background color (before patch) then an attempt was made to have a uniform
background  color but then it monopolized one color that can't be used with
foreground. The underline suffer the same problem as the inverse video, I.e
its color change as we highlight text. That's why the little demo only
underlined the front part of the line, that could be be reverse video too
but just the whitespace on the front of the line are by definition
monochrome.  I reckon my demo is bugged as you noticed, when disabling
syntax highlight then my underline goes all the way through the point line.

May be an idea could be set the whole point line with un-highlited,
monochrome,  then with the new range thing use reverse or underline for the
sub part only

My little underline on leading whitespace was just a way to find the >
quicker as I got long win on 4k display with 100++ Line so spotting the
point line quickly is a plus.

I'll try my best to review try a monochrome highlight to see the visual
aspect

Anyway keep going the TUI it is real good.

  reply	other threads:[~2020-06-15 16:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09  7:55 Phi Debian
2020-06-09 13:04 ` Pedro Alves
2020-06-09 14:32   ` Phi Debian
2020-06-09 15:03     ` Phi Debian
2020-06-11 10:34       ` Pedro Alves
2020-06-11 13:55         ` Phi Debian
2020-06-15 14:20           ` Pedro Alves
2020-06-15 15:48             ` Hannes Domani
2020-06-15 16:56               ` Phi Debian [this message]
2020-06-15 19:30                 ` Pedro Alves
2020-06-15 19:47                   ` Phi Debian
2020-06-15 20:12                   ` Tom Tromey
2020-06-15 20:45                     ` Pedro Alves
2020-06-16  3:38                       ` Phi Debian
2020-06-16 11:02                         ` [PATCH] Add "set style tui-current-position on|off" default to off Pedro Alves
2020-06-16 14:33                           ` Eli Zaretskii
2022-11-15 10:09                           ` Andrew Burgess
2022-11-15 12:15                             ` Pedro Alves
2022-11-16 10:41                               ` Andrew Burgess
2022-11-17  6:30                                 ` Phi Debian
     [not found]   ` <CAJOr74jg==A7NM4qtWEq6neXqxpxxtUEVdDgsahfvRobW+Q0wA@mail.gmail.com>
     [not found]     ` <CAJOr74hQdi6Y4MpGy=J-3CTRA2PP08OebTO2hBFN5NyDRokb3Q@mail.gmail.com>
     [not found]       ` <CAJOr74gyyw4hJm9j0fzKQdzkJKzq=yiAXyZx_c2Q=RA8GTSN7Q@mail.gmail.com>
     [not found]         ` <ed9ea9c6-3d4d-6ba7-4672-bff2b2617012@redhat.com>
2020-06-10 20:25           ` TUI enhancement suggestion Phi Debian
2020-06-11 10:17             ` 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=CAJOr74iA-BJv24LoD5jJykMh_Kb6TH+U7kykpSPgia9WVF8Mtw@mail.gmail.com \
    --to=phi.debian@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).