[Bug testsuite/30451] New: [gdb/testsuite] Implement newline glitch in tuiterm

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

            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=ansi
n=ansi-xenl

f=$n.txt
infocmp -1 $o > $f
echo -e "\txenl," >> $f
description="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=ansi-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 == [expr
$readline_width + 1]
FAIL: gdb.tui/wrap-line.exp: width-auto-detected: $gdb_width == [expr
$readline_width + 1]
...
which is expected, because the test has hardcoded expections about TERM=ansi,
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.

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