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/30580] New: [gdb/tui] !HAVE_WBORDER and border-kind ascii and space
Date: Fri, 23 Jun 2023 06:47:35 +0000	[thread overview]
Message-ID: <bug-30580-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30580
           Summary: [gdb/tui] !HAVE_WBORDER and border-kind ascii and
                    space
           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: ---

The TUI sources contain a HAVE_WBORDER ifdef:
...
$ find gdb* -type f | xargs grep HAVE_WBORDER
gdb/config.in:#undef HAVE_WBORDER
gdb/tui/tui-wingeneral.c:#ifdef HAVE_WBORDER
...

I simulated the !HAVE_WBORDER case using:
...
-#ifdef HAVE_WBORDER
+#if 0
...
and realized that border-kind ascii and space still use the acs corners, which
looks funny.

With space border-kind:
...
┌                                  ┐

 [ No Source Available ]            

└                                  ┘
...

With ascii border-kind:
...
┌----------------------------------┐
|                                  |
|[ No Source Available ]           |
|                                  |
└----------------------------------┘
...

With the space border-kind there's a clear style break.

With the ascii border-kind, things look funny because the top corner elements
do not connect to the neighboring hline and vline elements, while the bottom
corner elements do connect to the neighboring vline elements, but not the hline
ones (at least, in my xterm).

Maybe the ascii and space border-kind values should be eliminated for the
!HAVE_WBORDER case.

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

             reply	other threads:[~2023-06-23  6:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23  6:47 vries at gcc dot gnu.org [this message]
2023-06-23 12:42 ` [Bug tui/30580] " tromey at sourceware dot org
2023-06-23 13:37 ` vries at gcc dot gnu.org
2023-06-23 20:32 ` tromey at sourceware dot org
2023-07-12 13:35 ` vries at gcc dot gnu.org
2023-07-12 14:27 ` cvs-commit at gcc dot gnu.org
2023-07-12 14:28 ` 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-30580-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).