https://bugs.kde.org/show_bug.cgi?id=435975
--- Comment #10 from Ivan Sorokin <[email protected]> --- Here's a more detailed list of kitty protocol features not supported in far2l. Perhaps implementing this protocol in Konsole in the same scope could be a good start, reducing the implementation complexity to a reasonable level while still covering a significant portion, if not all, of real-world application needs: 1. The keyboard flags stack operations (`push`/`pop`) and independent state maintenance for the alternate screen are not implemented. 2. The bitwise flag manipulation modes (set, OR, AND-NOT) for the `CSI =` command are not supported. 3. Key repeat events (event type 2) are not supported. 4. `Super`, `Hyper`, and `Meta` modifiers are not supported. 5. PUA code mappings are missing for Keypad keys, extended function keys (`F13`-`F35`) and Multimedia keys. 6. Keys pressed with `Shift` report the shifted keycode instead of the unshifted keycode. 7. The "associated text" field contain the same value as shifted keycode. 8. UTF-16 surrogate pairs (e.g., Emoji) are transmitted as two separate events rather than a single UTF-32 codepoint. 9. IME input bypass the escape sequence generation even in full reporting mode (Mode 8). 10. The implementation ignores the Application Cursor Keys mode (`DECCKM`) state when encoding arrow keys. -- You are receiving this mail because: You are watching all bug changes.
