public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 0/6] [gdb/tui] Introduce ansi-for-tui
Date: Mon, 22 May 2023 15:15:38 +0200	[thread overview]
Message-ID: <20230522131545.12291-1-tdevries@suse.de> (raw)

For TUI testing, we'd like to use an xterm to replay scenario's that are
exercised in the testsuite, and vice versa create scenario's on an xterm and
be able to reproduce those in the testsuite.  In order to ensure identical
behaviour, we'd need identical TERM settings.

This series:
- introduces a new termcap entry ansi-for-tui that can be used with TUI in
  an xterm,
- adds the newline_glitch capability to ansiterm, and
- makes the TUI testsuite use ansi-for-tui.

Tested by re-running the TUI test-cases (gdb.tui/*.exp and gdb.python/tui*.exp)
on x86_64-linux.

Tom de Vries (6):
  [gdb/testsuite] Use TERM=dummy in gdb.tui/tuiterm.exp
  [gdb/testsuite] Factor out Term::_wrap_cursor
  [gdb/contrib] Add ansi-for-tui.sh
  [gdb/testsuite] Make ansi-for-tui available in with_tuiterm
  [gdb/testsuite] Implement the newline glitch in tuiterm
  [gdb/testsuite] Use ansi-for-tui in tuiterm

 gdb/contrib/ansi-for-tui.sh         |  66 +++++++++++++++
 gdb/testsuite/gdb.tui/tuiterm.exp   |  34 +++++++-
 gdb/testsuite/gdb.tui/wrap-line.exp |   4 +-
 gdb/testsuite/lib/gdb.exp           |  16 ++++
 gdb/testsuite/lib/tuiterm.exp       | 123 ++++++++++++++++++++++++++--
 5 files changed, 231 insertions(+), 12 deletions(-)
 create mode 100755 gdb/contrib/ansi-for-tui.sh


base-commit: 7b67409b99edca33b76961179286fb43a1714dd2
-- 
2.35.3


             reply	other threads:[~2023-05-22 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 13:15 Tom de Vries [this message]
2023-05-22 13:15 ` [PATCH 1/6] [gdb/testsuite] Use TERM=dummy in gdb.tui/tuiterm.exp Tom de Vries
2023-05-22 13:15 ` [PATCH] [gdb/tui] Add set style tui-status-window Tom de Vries
2023-05-22 13:47   ` Eli Zaretskii
2023-05-22 14:22     ` Tom de Vries
2023-05-22 15:50       ` Eli Zaretskii
2023-05-22 13:15 ` [PATCH 2/6] [gdb/testsuite] Factor out Term::_wrap_cursor Tom de Vries
2023-05-22 13:15 ` [PATCH 3/6] [gdb/contrib] Add ansi-for-tui.sh Tom de Vries
2023-05-22 13:15 ` [PATCH 4/6] [gdb/testsuite] Make ansi-for-tui available in with_tuiterm Tom de Vries
2023-05-22 13:15 ` [PATCH 5/6] [gdb/testsuite] Implement the newline glitch in tuiterm Tom de Vries
2023-05-22 13:15 ` [PATCH 6/6] [gdb/testsuite] Use ansi-for-tui " 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=20230522131545.12291-1-tdevries@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).