Closed unxed closed 5 months ago
Theoretically possible solutions include using technique like in this Wayland keylogger: https://github.com/Aishou/wayland-keylogger or creating some kind of "proxy" between terminal app and Wayland server that could intercept keypress info and send to far2l.
Upstream issue: https://gitlab.gnome.org/GNOME/vte/-/issues/2601
Reproduces in KDE's Konsole as well. Upstream issue: https://bugs.kde.org/show_bug.cgi?id=435975
https://gitlab.gnome.org/GNOME/vte/-/issues/2764 https://bugs.kde.org/show_bug.cgi?id=484044
Maybe it would be a bit easier to implement win32-input-mode then kitty's protocol in popular terminals?
dup #2040, closing
Due to Wayland security model, this is probably can not be easily fixed. See also: https://github.com/elfmz/far2l/issues/2040
Using a terminal emulator with some extended input mode, supported by far2l, like kitty, is one of the possible workarounds. You can also switch back to X11 sessions or use wx (GUI) far2l backend.