From 37e3111069bdd386e4854012124a122351ee351d Mon Sep 17 00:00:00 2001
From: Fabian Boehm <FHomborg@gmail.com>
Date: Thu, 16 Jan 2025 16:37:04 +0100
Subject: [PATCH] Don't send modifyOtherKeys if kitty protocol is supported

No use in doing this and it would trigger an ugly log message from kitty.
---
 src/input_common.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/input_common.rs b/src/input_common.rs
index 1b36a5e80..04578a1a6 100644
--- a/src/input_common.rs
+++ b/src/input_common.rs
@@ -518,7 +518,7 @@ pub fn terminal_protocols_enable_ifn() {
     } else {
         concat!(
             "\x1b[?2004h", // Bracketed paste
-            "\x1b[>4;1m",  // XTerm's modifyOtherKeys
+            // "\x1b[>4;1m",  // XTerm's modifyOtherKeys - no use in doing this with kitty protocol
             kitty_progressive_enhancements!(),
             "\x1b=", // set application keypad mode, so the keypad keys send unique codes
         )
@@ -540,7 +540,7 @@ pub(crate) fn terminal_protocols_disable_ifn() {
     } else {
         concat!(
             "\x1b[?2004l", // Bracketed paste
-            "\x1b[>4;0m",  // XTerm's modifyOtherKeys
+            // "\x1b[>4;0m",  // XTerm's modifyOtherKeys
             "\x1b[=0u",    // CSI u with kitty progressive enhancement
             "\x1b>",       // application keypad mode
         )