From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/tui] Use more box_width in tui-regs.c
Date: Mon, 18 Dec 2023 07:16:51 -0700 [thread overview]
Message-ID: <87ttof4muk.fsf@tromey.com> (raw)
In-Reply-To: <7e9b02eb-dd08-4419-a11d-953449cedbba@suse.de> (Tom de Vries's message of "Sat, 16 Dec 2023 10:27:05 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> Anyway, looking at one of the PRs you just filed, we may go to a
Tom> hborder/vborder (horizontal/vertical) approach [ or even a
Tom> tborder/bborder/lborder/rborder (top/bottom/left/right) approach ] and
Tom> I suppose that could be a good moment to rectify this misnomer.
If anyone ever implements it, yeah.
I wonder if windows should just have their "inner" size and position and
then the TUI itself draw the boxes; instead of the current model where
the box is part of the window.
Tom
prev parent reply other threads:[~2023-12-18 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 11:37 Tom de Vries
2023-12-15 15:32 ` Tom Tromey
2023-12-16 9:27 ` Tom de Vries
2023-12-18 14:16 ` Tom Tromey [this message]
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=87ttof4muk.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.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).