From: Phi Debian <phi.debian@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: TUI enhancement suggestion.
Date: Thu, 11 Jun 2020 15:55:42 +0200 [thread overview]
Message-ID: <CAJOr74iDZ6ws=_xLVvP0W9jRkcbBZoR8vH41u20HiYKqxRdQog@mail.gmail.com> (raw)
In-Reply-To: <38b5d874-cdf2-50e7-dc76-aed3fee20334@redhat.com>
Ok I got the big picture, the little patch I made was more a demonstrator
than a final patch, I don't know the review process.
As soon as I can I redo one, with our remarks.
Regarding the underline going up to printf I made it on purpose as I find
it less intrusive, underlinie space is simple, while underlining text
(source) can render less readable again (like colors), so it is something I
can spot quickly but not too intrusive. I use very tall xterm, spotting the
underline in the space part is very easy easier thanjust the little >
before the line number.. That was the reasoning... Yet I admit, when there
is no styling it should works too so I will look again :)
I can't work too much on this unfortunately so it may be a while since I
come black to this.
Cheers
next prev parent reply other threads:[~2020-06-11 13:55 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 [this message]
2020-06-15 14:20 ` Pedro Alves
2020-06-15 15:48 ` Hannes Domani
2020-06-15 16:56 ` Phi Debian
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='CAJOr74iDZ6ws=_xLVvP0W9jRkcbBZoR8vH41u20HiYKqxRdQog@mail.gmail.com' \
--to=phi.debian@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).