Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ctrl+1,2,3..0 do not work in ttyxi in GNome Terminal on Wayland systems #2042

Closed
unxed opened this issue Mar 5, 2024 · 4 comments
Closed

Comments

@unxed
Copy link
Contributor

unxed commented Mar 5, 2024

Due to Wayland security model, this is probably can not be easily fixed.
See also: #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.

@unxed
Copy link
Contributor Author

unxed commented Mar 18, 2024

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.

@unxed
Copy link
Contributor Author

unxed commented Mar 18, 2024

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

See also:
#2041

@unxed
Copy link
Contributor Author

unxed commented Mar 20, 2024

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?

@unxed
Copy link
Contributor Author

unxed commented May 19, 2024

dup #2040, closing

@unxed unxed closed this as completed May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant