From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH 8/8] [gdb/tui] Fix TUI for TERM=ansi
Date: Sun, 30 Apr 2023 13:08:51 +0200 [thread overview]
Message-ID: <a0facf3e-e3de-7958-4fb4-5b19ad85915b@suse.de> (raw)
In-Reply-To: <b79b9fd1-3c1e-8c32-c2f7-0dfc574471fa@suse.de>
On 4/25/23 09:09, Tom de Vries via Gdb-patches wrote:
> On 4/18/23 08:10, Tom de Vries via Gdb-patches wrote:
>> So, this patch could be simplified by just using _rl_term_autowrap.
>
> This version uses _rl_term_autowrap.
This (
https://sourceware.org/pipermail/gdb-patches/2023-April/199229.html ) is
the version I've ended up pushing.
It propagates the same change to tui_async_resize_screen, and adds a
test-case for that.
Thanks,
- Tom
next prev parent reply other threads:[~2023-04-30 11:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 14:08 [PATCH 0/8] [gdb/testsuite] Fix timeouts in TUI tests Tom de Vries
2023-04-13 14:08 ` [PATCH 1/8] [gdb/testsuite] Add warning for timeout in accept_gdb_output Tom de Vries
2023-04-13 14:08 ` [PATCH 2/8] [gdb/testsuite] Add debug prints in Term::wait_for Tom de Vries
2023-04-13 14:08 ` [PATCH 3/8] [gdb/testsuite] Fix timeout in gdb.tui/corefile-run.exp Tom de Vries
2023-04-13 14:08 ` [PATCH 4/8] [gdb/testsuite] Fix timeout in gdb.tui/main.exp Tom de Vries
2023-04-13 14:08 ` [PATCH 5/8] [gdb/testsuite] Fix timeout in gdb.tui/new-layout.exp Tom de Vries
2023-04-13 14:08 ` [PATCH 6/8] [gdb/testsuite] Fix timeout in gdb.tui/completion.exp Tom de Vries
2023-04-13 14:08 ` [PATCH 7/8] [gdb/testsuite] Fix timeout in gdb.tui/empty.exp Tom de Vries
2023-04-13 14:08 ` [PATCH 8/8] [gdb/tui] Fix TUI for TERM=ansi Tom de Vries
2023-04-13 14:17 ` Tom de Vries
2023-04-14 11:02 ` Tom de Vries
2023-04-18 6:10 ` Tom de Vries
2023-04-25 7:09 ` Tom de Vries
2023-04-30 11:08 ` Tom de Vries [this message]
2023-04-25 6:35 ` [PATCH 0/8] [gdb/testsuite] Fix timeouts in TUI tests Tom de Vries
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=a0facf3e-e3de-7958-4fb4-5b19ad85915b@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).