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] New: [gdb/tui] tui border-kind acs looks weird for TERM=ansi and LANG=en_US.UTF-8
Date: Tue, 18 Apr 2023 15:44:24 +0000	[thread overview]
Message-ID: <bug-30370-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30370

            Bug ID: 30370
           Summary: [gdb/tui] tui border-kind acs looks weird for
                    TERM=ansi and LANG=en_US.UTF-8
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tui
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

When using gdb's TUI with TERM=ansi and LANG=en_US.UTF-8, I get a weird border:
...
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³                                                                            ³
³                                                                            ³
...

This is with the default tui border-kind acs.

I tracked this down to not using NCURSES_NO_UTF8_ACS=1, with which I get
instead:
...
┌────────────────────────────────────────────────────────────────────────────┐
│                                                                            │
...

I wonder if we should consider this an ncurses problem or a gdb problem.

In the latter case, I wonder if GDB can detect this problem, and set
NCURSES_NO_UTF8_ACS=1 before initializing ncurses.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-04-18 15:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 15:44 vries at gcc dot gnu.org [this message]
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
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@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).