public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/25342] Unicode data in strings conflicts with TUI Date: Mon, 28 Sep 2020 02:36:00 +0000 [thread overview] Message-ID: <bug-25342-4717-sWGl2kNjki@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25342-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25342 --- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2c72d5e58a55d3e0f867ffd9421184852f051cb7 commit 2c72d5e58a55d3e0f867ffd9421184852f051cb7 Author: Tom Tromey <tom@tromey.com> Date: Sun Sep 27 20:30:30 2020 -0600 Rewrite tui_puts This rewrites tui_puts. It now writes as many bytes as possible in a call to waddnstr, letting curses handle multi-byte sequences properly. Note that tui_puts_internal remains. It is needed to handle computing the start line of the readline prompt, which is difficult to do properly in the case where redisplaying can also cause the command window to scroll. This might be possible to implement by reverting to single "character" output, by using mbsrtowcs for its side effects to find character boundaries in the input. I have not attempted this. gdb/ChangeLog 2020-09-27 Tom Tromey <tom@tromey.com> PR tui/25342: * tui/tui-io.c (tui_puts): Rewrite. Move earlier. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-28 2:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25342-4717@http.sourceware.org/bugzilla/> 2020-06-27 19:04 ` tromey at sourceware dot org 2020-08-09 14:37 ` tromey at sourceware dot org 2020-09-28 2:35 ` cvs-commit at gcc dot gnu.org 2020-09-28 2:36 ` cvs-commit at gcc dot gnu.org [this message] 2020-09-28 2:38 ` tromey at sourceware dot org 2020-10-08 17:54 ` tromey at sourceware dot org
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=bug-25342-4717-sWGl2kNjki@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).