From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 9A449385783F; Tue, 16 May 2023 11:39:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9A449385783F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1684237154;
	bh=qK7RzNVEDgKA4COBzZgm1qZeDF9ux7eOEjpvoUKixW0=;
	h=From:To:Subject:Date:From;
	b=y5HevLQbTYJuirFUnIydAPSikIEzVx4MpkFYEuYbplbNg9WfnQ38U3Y1R6KMjcvGH
	 GbHUExj0oauwGHfkGx3eDaaceyKyCCPXrill1mnrKKnGCK2N+CeAARZB+M5Td3avyv
	 XH14iobLoiYcrpz6GA403NxQoeJi6kOGJu4X3SGk=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/30451] New: [gdb/testsuite] Implement newline glitch
 in tuiterm
Date: Tue, 16 May 2023 11:39:14 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: enhancement
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: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-30451-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30451

            Bug ID: 30451
           Summary: [gdb/testsuite] Implement newline glitch in tuiterm
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

An idea suggested here (
https://sourceware.org/pipermail/gdb-patches/2023-May/199478.html ) is to
implement the newline glitch in tuiterm.

I wrote a script:
...
$ cat gen-ansi-xenl.sh
#!/bin/sh

o=3Dansi
n=3Dansi-xenl

f=3D$n.txt
infocmp -1 $o > $f
echo -e "\txenl," >> $f
description=3D"ansi/pc-term compatible with color and newline glitch"

sed -i "s%^$o|%$n|%" $f

sed -i "s%|.*,$%|$description,%" $f

tic $f
...
that generates:
...
$ find ~/.terminfo/ -type f
/home/vries/.terminfo/a/ansi-xenl
...
and allows us to use TERM=3Dansi-xenl.

I changed this in with_tuiterm:
...
-           setenv TERM ansi
+           setenv TERM ansi-xenl
...
and ran the TUI tests (gdb.tui/*.exp and gdb.python/tui*.exp).

The only fall-out of this was:
...
FAIL: gdb.tui/wrap-line.exp: width-hard-coded: $gdb_width =3D=3D [expr
$readline_width + 1]
FAIL: gdb.tui/wrap-line.exp: width-auto-detected: $gdb_width =3D=3D [expr
$readline_width + 1]
...
which is expected, because the test has hardcoded expections about TERM=3Da=
nsi,
so without xenl, and can trivially be fixed by updating the assert.

Surprisingly, this doesn't seem to be causing problems with any of the other
test-cases (we'd expect problems because we tell curses that tuiterm has the
glitch, but we haven't implemented it yet).

Apparently curses/gdb doesn't care too much about this.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=