-
-
Notifications
You must be signed in to change notification settings - Fork 335
Add aliases for key bindings #1238
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
Comments
All the weird codes are the peculiarity of terminal key handling. There is no magic mapping of all |
I think this is a viable suggestion, not invalid. For example we could have aliases like F1 -> meta2-11~ & meta-OP. |
Hi @ek4, I'm writing a specification that addresses this issue (but not only): https://specs.weechat.org/specs/2023-002-key-bindings-improvements.html This is still a draft and not complete, but your feedback is welcome on the proposed changes. Note: to be consistent, all new key names (aliases) are lower case, that means |
Hi, For your information I pushed the branch key-bindings-improvements (work in progress):
Please try with many terminals and different keys to ensure all keys are properly converted to the new name. |
All changes are implemented on the branch. As there are many breaking changes, please send feedback before it's merged and available for all testers of development version. |
Feature description
Add aliases for key bindings, for example
F5
onmeta2-15~
andmeta2-[E
, so that the keyF5
can be used directly in a key binding:/key bind F5 /some_command
.The text was updated successfully, but these errors were encountered: