From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [RFC 0/3] Some TUI fixes
Date: Mon, 03 Sep 2018 18:43:00 -0000 [thread overview]
Message-ID: <20180903184300.9961-1-tom@tromey.com> (raw)
I looked at the TUI code for the first time this weekend and came up
with a few patches. Here are the ones that seem ready.
The first is just a simple cleanup.
The second adds ANSI terminal escape sequence parsing, so that colors
work in extend prompts.
The third deprecates and replaces the tabset command.
I didn't know how to test the major patch here. TUI testing seems
tricky without writing some gigantic Tcl package to parse escape
sequences and render a terminal.
Let me know what you think.
Tom
next reply other threads:[~2018-09-03 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 18:43 Tom Tromey [this message]
2018-09-03 18:43 ` [RFC 3/3] Deprecate and replace the "tabset" command Tom Tromey
2018-09-03 18:58 ` Eli Zaretskii
2018-09-03 18:43 ` [RFC 1/3] Minor cleanups in tui-io.c Tom Tromey
2018-09-03 18:43 ` [RFC 2/3] Making ANSI terminal escape sequences work in TUI Tom Tromey
2018-10-11 23:04 ` Tom Tromey
2018-10-18 21:42 ` [RFC 0/3] Some TUI fixes Tom Tromey
2018-10-18 22:04 ` Tom Tromey
2018-10-19 23:20 ` 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=20180903184300.9961-1-tom@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/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).