public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/30451] [gdb/testsuite] Implement newline glitch in tuiterm
Date: Thu, 18 May 2023 22:43:39 +0000 [thread overview]
Message-ID: <bug-30451-4717-I1fFpMbfhT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30451-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30451
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Tom de Vries from comment #1)
> OTOH, if we implement the glitch in tuiterm but keep using TERM=ansi, we
> might be able to reproduce some of the problems we see with TERM=ansi on
> xterm-native terminal emulators.
IIUC it seems to me that the glitches must be the result of having
TERM disagree with the capabilities of the actual terminal. Is that
correct? If so I think we probably don't want to try to support that.
Instead the idea would be to implement the glitch and whatever else
is needed, and then run the TUI tests with TERM=xterm.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-18 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 11:39 [Bug testsuite/30451] New: " vries at gcc dot gnu.org
2023-05-16 13:54 ` [Bug testsuite/30451] " vries at gcc dot gnu.org
2023-05-18 22:43 ` tromey at sourceware dot org [this message]
2023-05-22 13:16 ` vries at gcc dot gnu.org
2023-05-22 13:27 ` vries at gcc dot gnu.org
2023-05-22 13:56 ` 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-30451-4717-I1fFpMbfhT@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).