From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2474D3857009; Thu, 4 May 2023 07:37:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2474D3857009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1683185855; bh=vLuWnz+RyAA3B8dTMeKQZT3De2YGZQs7kpUHTP4qVL0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uEYBFepQjFOaH7PDxRfZF5WAaOyCO3zx2LrG7Hb+rsKc4N/FGvE9lMfCEa+MyB+br 2kqnBU9zgZtbseq+3aiBxPzLxanAxY1PE0NqIkBk8K1BYhzIqmfJ4Iu9jkwG9CXbdx ThFgurkf6AdL32ZdJAiqVTo5VCNMOO25+5sRje3g= From: "vries at gcc dot gnu.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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30388 --- Comment #7 from Tom de Vries --- 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 TE= RM 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 wi= ll 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=