From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] [gdb/tui] Assume HAVE_WBORDER
Date: Wed, 12 Jul 2023 07:55:07 -0600 [thread overview]
Message-ID: <87wmz5p744.fsf@tromey.com> (raw)
In-Reply-To: <20230712132743.25382-1-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Wed, 12 Jul 2023 15:27:43 +0200")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> The tui border-kind setting allows values acs, ascii and space.
Tom> The values ascii and space however don't work well with !HAVE_WBORDER.
Tom> Fix this by removing the !HAVE_WBORDER case, which was introduced for Ultrix
Tom> support, which is now obsolete.
Tom> Tested on x86_64-linux.
Tom> PR tui/30580
Tom> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30580
Thank you.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2023-07-12 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 13:27 Tom de Vries via Gdb-patches
2023-07-12 13:55 ` Tom Tromey [this message]
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=87wmz5p744.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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