public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "wuzy01 at qq dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/28800] New: non-ascii character cannot display correctly in tui-mode's extended-prompt Date: Thu, 20 Jan 2022 16:03:26 +0000 [thread overview] Message-ID: <bug-28800-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28800 Bug ID: 28800 Summary: non-ascii character cannot display correctly in tui-mode's extended-prompt Product: gdb Version: 11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: wuzy01 at qq dot com Target Milestone: --- ## Reproduce Procedures ``` gdb -tui main ``` Then `set extended-prompt \w \f:\t\n❯ ` After inputting each character, the prompt string will be messed. it looks non-ascii character cannot display correctly in tui-mode. OS: 5.15.11 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-01-20 16:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-20 16:03 wuzy01 at qq dot com [this message] 2022-01-20 16:11 ` [Bug tui/28800] " schwab@linux-m68k.org 2022-01-27 12:26 ` aburgess at redhat dot com 2023-05-24 15:40 ` vries at gcc dot gnu.org 2023-05-24 17:56 ` vries at gcc dot gnu.org 2023-05-26 13:26 ` vries at gcc dot gnu.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-28800-4717@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).