public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "phi.debian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/29789] New: tui enable trash terminal color palette
Date: Wed, 16 Nov 2022 05:31:56 +0000 [thread overview]
Message-ID: <bug-29789-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29789
Bug ID: 29789
Summary: tui enable trash terminal color palette
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: phi.debian at gmail dot com
Target Milestone: ---
Hi,
On latest build (and since the epoch I guess) "tui enable" trash the terminal
color palette.
My terminals (xterm, mate-terminal, terminator, etc..) all have their color
setup to my liking (theme)
When entering GDB in TUI mode, curses don't temper with colors, so all is fine,
notably, the src-win rendering with color is super.
(gdb) tui disable
Color still ok
(gdb) list 1
Still ok
(gdb) tui enable
xterm color palette trashed, a reset escape sequence is sent to xterm, src_win
color ugly (barely readable in my case, contrast)
To restore this without exiting GDB, while in tui enable mode
(gdb) shell setup-terminal-palette
(gdb) ^L
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-11-16 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 5:31 phi.debian at gmail dot com [this message]
2022-11-16 16:30 ` [Bug tui/29789] " ssbssa at sourceware dot org
2022-11-16 16:38 ` phi.debian at gmail dot com
2022-11-17 5:47 ` phi.debian at gmail dot com
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-29789-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).