From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 0/3] [gdb/tui] Add tui border-kind active-ascii
Date: Mon, 8 May 2023 16:10:33 +0200 [thread overview]
Message-ID: <20230508141036.22723-1-tdevries@suse.de> (raw)
I wrote a patch that adds a new tui border-kind: active-ascii.
That patch makes changes in function tui_update_variables, and I ended up
writing a patch that simplifies it by factoring out some functions, to make
subsequent changes in the function easier.
While factoring out one of the functions, I noticed a pre-existing buglet in
one of them, so I wrote a separate patch to fix this.
Tested on x86_64-linux, by rebuilding and running test-cases gdb.tui/*.exp and
gdb.python/tui*.exp for each patch.
Tom de Vries (3):
[gdb/tui] Make tui_update_variables more readable
[gdb/tui] Fix buglet in set_border_kind_item
[gdb/tui] Add tui border-kind active-ascii
gdb/doc/gdb.texinfo | 4 +
gdb/testsuite/gdb.tui/tui-focus.exp | 7 +-
gdb/testsuite/lib/tuiterm.exp | 49 +++++-----
gdb/tui/tui-win.c | 139 +++++++++++++++++++++-------
gdb/tui/tui-win.h | 6 ++
gdb/tui/tui-wingeneral.c | 17 +++-
6 files changed, 163 insertions(+), 59 deletions(-)
base-commit: c239019c9f649867c686204d1ac8947a963784d8
--
2.35.3
next reply other threads:[~2023-05-08 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 14:10 Tom de Vries via Gdb-patches [this message]
2023-05-08 14:10 ` [PATCH 1/3] [gdb/tui] Make tui_update_variables more readable Tom de Vries via Gdb-patches
2023-12-15 19:48 ` Tom Tromey
2023-05-08 14:10 ` [PATCH 2/3] [gdb/tui] Fix buglet in set_border_kind_item Tom de Vries via Gdb-patches
2023-05-22 14:47 ` [pushed] [gdb/tui] Fix buglet in tui_update_variables Tom de Vries via Gdb-patches
2023-05-08 14:10 ` [PATCH 3/3] [gdb/tui] Add tui border-kind active-ascii Tom de Vries via Gdb-patches
2023-12-15 19:50 ` Tom Tromey
2023-12-15 20:04 ` Eli Zaretskii
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=20230508141036.22723-1-tdevries@suse.de \
--to=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
--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