From d505017cec86c000f891b003f5ca3481f5ffae61 Mon Sep 17 00:00:00 2001 From: Berke Güzel Date: Mon, 12 Oct 2026 17:54:48 +0300 Subject: term: fix the two Kitty suite failures and run the suite by default Both failures were stale expectations in our copy of the suite. 8c2464c moved the terminal to xterm behavior and added spec tests for it. The Kitty bridge did not compile then, so nobody updated the suite. - A cursor report with a pending wrap gives the last column (1;5). Kitty gives the start of the next line. - HT only moves the cursor. Kitty writes a tab cell, which erases the text under the tab. REP after the tab then repeats nothing. The suite went weeks without running, because it needed -Dkitty_tests=true. Now every unsanitized Linux build runs it in the unit suite, and the main option only makes it mandatory. The README lists the deliberate differences from Kitty. Co-Authored-By: Claude Opus 5.5 --- meson.options | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'meson.options') diff --git a/meson.options b/meson.options index 27bc018..3a339a3 100644 --- a/meson.options +++ b/meson.options @@ -18,8 +18,8 @@ option( description: 'Seed count for write-fuzz-test', ) option( - 'kitty_tests', - type: 'boolean', - value: false, - description: 'Build the Linux Kitty parser compatibility tests (use an unsanitized build)', + 'kitty', + type: 'feature', + value: 'auto', + description: 'The Kitty parser compatibility tests. auto runs them on an unsanitized Linux build', ) -- cgit v1.2.3