From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/6] Handle UTF-8 in TUI source windows
Date: Sun, 27 Sep 2020 20:29:42 -0600 [thread overview]
Message-ID: <87ft72my5l.fsf@tromey.com> (raw)
In-Reply-To: <87mu47f69s.fsf@tromey.com> (Tom Tromey's message of "Fri, 10 Jul 2020 14:45:51 -0600")
Tom> This series implements support for displaying UTF-8 sources in TUI
Tom> windows. This implementation properly handles horizontal scrolling,
Tom> which was an issue in earlier attempts.
Tom> No new test case -- I tried to write one, but I could not get it to
Tom> work. It's unclear if this is due to a bug in my test, a bug in
Tom> tuiterm.exp, or a bug in curses; and I got irritated trying to find
Tom> out.
[... later ...]
Tom> Just FYI, I'm planning to hold this series until after the release
Tom> branch is made. This introduces the first use of curses pads into gdb,
Tom> which makes me a bit nervous.
I'm going to check this in now.
Let me know if you encounter any problems.
Tom
prev parent reply other threads:[~2020-09-28 2:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 21:20 Tom Tromey
2020-06-27 21:20 ` [PATCH 1/6] Remove test duplicate from gdb.tui Tom Tromey
2020-06-27 21:20 ` [PATCH 2/6] Use an inner window in tui_py_window Tom Tromey
2020-06-27 21:20 ` [PATCH 3/6] Remove a call to show_source_line from TUI Tom Tromey
2020-06-27 21:20 ` [PATCH 4/6] Use a curses pad for source and disassembly windows Tom Tromey
2020-06-27 21:20 ` [PATCH 5/6] Use ISCNTRL in tui_copy_source_line Tom Tromey
2020-06-27 21:20 ` [PATCH 6/6] Rewrite tui_puts Tom Tromey
2020-07-10 20:45 ` [PATCH 0/6] Handle UTF-8 in TUI source windows Tom Tromey
2020-09-28 2:29 ` 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=87ft72my5l.fsf@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).