public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/30388] [gdb/tui, TERM=ansi] first char of prompt in status line Date: Thu, 04 May 2023 07:37:34 +0000 [thread overview] Message-ID: <bug-30388-4717-VHFMNETLyZ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30388-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30388 --- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> --- I'm close to giving up on this, I've played around quite a bit changing how the status line is rendered, but the problem keeps reoccuring in different forms and scenarios. I'm starting to suspect that we're running into the problem that setting TERM to something changes the capabilities reported to the application, but not the behaviour of the terminal emulator itself. More specifically with xterm we have the am and xn capabilities set, with ansi just am, but the terminal will behave the same regardless. I've a filed a new PR30419 - [gdb/tui] Support tui safe-mode on/off, to work around this in a more generic fashion, with the idea of avoiding to run into this by hiding the last column, as readline does. But it's possible that we have to classify this PR as not-a-bug: If you lie to your application about the capabilities or your terminal, you may run into trouble. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-04 7:37 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-25 9:45 [Bug tui/30388] New: " vries at gcc dot gnu.org 2023-04-25 10:08 ` [Bug tui/30388] " vries at gcc dot gnu.org 2023-04-25 10:19 ` vries at gcc dot gnu.org 2023-04-25 10:52 ` vries at gcc dot gnu.org 2023-04-25 10:53 ` vries at gcc dot gnu.org 2023-04-25 11:30 ` vries at gcc dot gnu.org 2023-04-25 13:07 ` vries at gcc dot gnu.org 2023-05-04 7:37 ` vries at gcc dot gnu.org [this message] 2023-05-09 13:22 ` 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-30388-4717-VHFMNETLyZ@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: linkBe 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).