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:54:00 +0000 [thread overview]
Message-ID: <bug-30370-4717-XHj3yfnzEm@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 #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #2)
> IIUC this env var is a workaround for buggy terminals and/or
> incorrect termcap entries. I tend to doubt gdb should unilaterally set it.
I understand the reasoning.
It's just that TERM=ansi is used in the TUI testsuite, so I'm using that all
the time when debugging TUI test-cases on an actual terminal (rather than the
ansi terminal emulator in the testsuite), and each time I run into this PR
(both on openSUSE Leap 15.4 and Ubuntu 22.04) I end up using "set tui
border-kind ascii" to work around it (but as I've just learned, I could also
use NCURSES_NO_UTF8_ACS=1).
So, my attempt at a rationale for fixing this PR would be that if we use
TERM=ansi in the testsuite, we should try to make that work as expected on the
average terminal emulator.
--
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:54 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 ` [Bug tui/30370] " vries at gcc dot gnu.org
2023-04-18 22:24 ` 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 [this message]
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-XHj3yfnzEm@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).