public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/30580] [gdb/tui] !HAVE_WBORDER and border-kind ascii and space
Date: Wed, 12 Jul 2023 14:27:52 +0000 [thread overview]
Message-ID: <bug-30580-4717-8WDnC4UJH7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30580-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30580
--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a839dbdce5d923dd28027ae2dba01f88104b7926
commit a839dbdce5d923dd28027ae2dba01f88104b7926
Author: Tom de Vries <tdevries@suse.de>
Date: Wed Jul 12 16:27:40 2023 +0200
[gdb/tui] Assume HAVE_WBORDER
The tui border-kind setting allows values acs, ascii and space.
The values ascii and space however don't work well with !HAVE_WBORDER.
Fix this by removing the !HAVE_WBORDER case, which was introduced for
Ultrix
support, which is now obsolete.
Tested on x86_64-linux.
PR tui/30580
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30580
Approved-By: Tom Tromey <tom@tromey.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-12 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 6:47 [Bug tui/30580] New: " vries at gcc dot gnu.org
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 [this message]
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-8WDnC4UJH7@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).