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 v2] [gdb/tui] Show regs when switching to regs layout
Date: Fri, 15 Dec 2023 18:40:39 -0700 [thread overview]
Message-ID: <87edfm6i20.fsf@tromey.com> (raw)
In-Reply-To: <a1b766c1-1bba-4719-85e0-04a1d52e126d@suse.de> (Tom de Vries's message of "Sat, 9 Dec 2023 11:01:50 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> How about this approach?
Tom> Rather than adding global state, it adds a function parameter.
Tom> It's currently called toplevel, though I've also consider "active".
This is fine by me.
Really I suspect the register window refresh code can be untangled and
not need any of this, but it's fine to just fix the bug and move on.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2023-12-16 1:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 7:52 Tom de Vries
2023-11-27 12:27 ` Alexandra Petlanova Hajkova
2023-12-08 15:29 ` Tom Tromey
2023-12-09 8:30 ` Tom de Vries
2023-12-09 10:01 ` Tom de Vries
2023-12-16 1:40 ` Tom Tromey [this message]
2023-12-16 8:34 ` Tom de Vries
2023-12-17 17:31 ` Tom Tromey
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=87edfm6i20.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).