Handle Kitty return in enter detection

Author: jahooma

cli/src/utils/__tests__/terminal-enter-detection.test.ts

@@ -26,6 +26,16 @@ describe('terminal enter detection', () => {
     expect(isLinefeedActingAsEnter()).toBe(false)
   })
 
+  test('marks Kitty CSI-u Return as return seen', () => {
+    expect(
+      shouldMarkReturnKeySeen({ name: 'return', sequence: '\x1b[13u' }),
+    ).toBe(true)
+
+    markReturnKeySeenForKey({ name: 'return', sequence: '\x1b[13u' })
+
+    expect(isLinefeedActingAsEnter()).toBe(false)
+  })
+
   test('does not mark keypad Enter escape sequences as return seen', () => {
     expect(
       shouldMarkReturnKeySeen({ name: 'kpenter', sequence: '\x1b[57414u' }),

cli/src/utils/terminal-enter-detection.ts

@@ -1,3 +1,5 @@
+import { isKeypadEnter } from './keypad-keys'
+
 /**
  * Most terminals send \r for Enter and \n for Ctrl+J. A few niche Linux
  * terminal emulators send \n for Enter instead, making the two
@@ -15,9 +17,7 @@ const defaultHasSeenReturnKey = process.platform === 'darwin'
 let hasSeenReturnKey = defaultHasSeenReturnKey
 
 export function shouldMarkReturnKeySeen(key: EnterDetectionKey): boolean {
-  return (
-    (key.name === 'return' || key.name === 'enter') && key.sequence === '\r'
-  )
+  return (key.name === 'return' || key.name === 'enter') && !isKeypadEnter(key)
 }
 
 export function markReturnKeySeen(): void {