public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/30370] [gdb/tui] tui border-kind acs looks weird for TERM=ansi and LANG=en_US.UTF-8
Date: Tue, 18 Apr 2023 22:09:53 +0000 [thread overview]
Message-ID: <bug-30370-4717-0YLXSGu3kz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30370-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30370
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> and set
> NCURSES_NO_UTF8_ACS=1 before initializing ncurses.
That seems to be possible, this has the desired effect:
...
diff --git a/gdb/tui/tui.c b/gdb/tui/tui.c
index 3604194a760..9bb9b1e73ef 100644
--- a/gdb/tui/tui.c
+++ b/gdb/tui/tui.c
@@ -402,6 +402,7 @@ tui_enable (void)
if (!gdb_stderr->isatty ())
error (_("Cannot enable the TUI when output is not a terminal"));
+ putenv (strdup ("NCURSES_NO_UTF8_ACS=1"));
s = newterm (NULL, stdout, stdin);
#ifdef __MINGW32__
/* The MinGW port of ncurses requires $TERM to be unset in order
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-18 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 15:44 [Bug tui/30370] New: " vries at gcc dot gnu.org
2023-04-18 22:09 ` vries at gcc dot gnu.org [this message]
2023-04-18 22:24 ` [Bug tui/30370] " tromey at sourceware dot org
2023-04-18 22:40 ` vries at gcc dot gnu.org
2023-04-18 22:54 ` vries at gcc dot gnu.org
2023-04-19 13:38 ` vries at gcc dot gnu.org
2023-05-04 7:41 ` 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-30370-4717-0YLXSGu3kz@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: 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).