From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] [gdb/tui] Handle unicode chars in prompt
Date: Fri, 26 May 2023 17:44:29 +0200 [thread overview]
Message-ID: <0c1512d8-0912-044d-6c12-ec93de068b87@suse.de> (raw)
In-Reply-To: <20230526132512.29496-1-tdevries@suse.de>
On 5/26/23 15:25, Tom de Vries via Gdb-patches wrote:
> In TUI, the prompt is written out by tui_puts_internal, which outputs one byte
> at a time using waddch, which apparantly breaks multi-byte char support.
>
> Fix this by detecting multi-byte chars in tui_puts_internal, and printing them using
> waddnstr.
FWIW, I just came across this commit, which seems relevant:
...
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.
...
This patch uses mbrtowc rather than mbsrtowcs, but I suppose the idea is
the same.
Thanks,
- Tom
next prev parent reply other threads:[~2023-05-26 15:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 13:25 Tom de Vries
2023-05-26 13:56 ` Eli Zaretskii
2023-05-30 16:51 ` Tom Tromey
2023-06-09 9:34 ` Tom de Vries
2023-06-09 10:21 ` Eli Zaretskii
2023-05-26 15:44 ` Tom de Vries [this message]
2023-05-30 17:03 ` Tom Tromey
2023-05-30 18:07 ` DJ Delorie
2023-05-31 0:02 ` Tom Tromey
2023-05-31 11:29 ` Tom de Vries
2023-06-08 22:44 ` Tom de Vries
2023-06-09 15:13 ` Tom Tromey
2023-06-09 9:48 ` Tom de Vries
2023-06-09 15:15 ` 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=0c1512d8-0912-044d-6c12-ec93de068b87@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).