public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug tui/30526] New: [gdb/tui, TERM=ansi] Exiting tui doesn't clear screen
@ 2023-06-07 7:10 vries at gcc dot gnu.org
2023-06-07 9:36 ` [Bug tui/30526] " cvs-commit at gcc dot gnu.org
0 siblings, 1 reply; 2+ messages in thread
From: vries at gcc dot gnu.org @ 2023-06-07 7:10 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30526
Bug ID: 30526
Summary: [gdb/tui, TERM=ansi] Exiting tui doesn't clear screen
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: ---
Say we run TUI with TERM=ansi in an xterm:
...
TERM=ansi gdb -q -tui -iex "set tui border-kind ascii"
...
and press ^L to fix the slightly broken screen.
Now, type "echo \n" and press enter until the prompt is at the bottom of the
screen.
Now type tui disable<enter>.
The only thing that changed in the screen is that the cursor moved to the start
of tui disable. We have in fact left TUI, which we can see by doing ^L which
will clear the entire screen, rather than refresh as it does in TUI.
The fact that we see "tui disable" is the TERM=ansi version of PR30523.
But even if we fix that, there's still no clear sign that we left TUI.
I think we should clear all windows, except the cmd window.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-06-07 9:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-07 7:10 [Bug tui/30526] New: [gdb/tui, TERM=ansi] Exiting tui doesn't clear screen vries at gcc dot gnu.org
2023-06-07 9:36 ` [Bug tui/30526] " cvs-commit at gcc dot gnu.org
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).