-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Alt arrow keys do nothing; key unbinding broken? #3729
Comments
This behavior is due to #3585. Proper expected behavior is restored with the following:
|
I also have the same issue. Do we have to unbind the keys for tmux to work? And what about mouse-focus? Prior to this release, in |
thanks for that. I could be mistaken, as I use versions of tmux in wsl & cygwin using And the key unbounding didn't work. I'm still not able to use the alt keys to switch panes |
@sivaramn what exactly do you have in your |
that's in in
|
Just want do confirm that unbinding the alt key bindings worked for me. tmux resizing is now working as expected. |
Thank you so much for this! |
Thanks for the example keybindings. Adding the unbound entries helped with behaviour in micro, which uses "alt+direction" by default for moving word at a time. |
Reopening issue because my alt-arrow buttons stopped working after upgrading Terminal to 0.10.761.0. Windows build number: 10.0.18363.720 Any other software?
|
Yep, fair enough. Bet we broke this with VT input tunneling. |
Actually, no, I think we broke unbinding. /cc @zadjii-msft. |
Same issue :) |
looking now |
## Summary of the Pull Request We (the royal "we") broke key unbinding in #4746. We didn't run the local tests after this, which actually would have caught this. The comment even suggests what we should have done here. We need to make sure that when we bail, it's because there's a parsing function that returned nothing. `null`, `"unbound"`, etc actually don't even have a parsing function at all, so they should just keep on keepin' on. ## References Source of this regression: #4746 ## PR Checklist * [x] Closes #3729 * [x] I work here * [x] Tests added/passed * [n/a] Requires documentation to be updated ## Detailed Description of the Pull Request / Additional comments This is a great example of why your unittests should run in CI always ## Validation Steps Performed * **ran the tests** * tested the following unbindings: ```json { "command": null, "keys": [ "ctrl+shift+t" ] }, { "command": "unbound", "keys": [ "ctrl+shift+t" ] }, { "command": "null", "keys": [ "ctrl+shift+t" ] }, ``` and they each individually worked.
## Summary of the Pull Request We (the royal "we") broke key unbinding in #4746. We didn't run the local tests after this, which actually would have caught this. The comment even suggests what we should have done here. We need to make sure that when we bail, it's because there's a parsing function that returned nothing. `null`, `"unbound"`, etc actually don't even have a parsing function at all, so they should just keep on keepin' on. ## References Source of this regression: #4746 ## PR Checklist * [x] Closes #3729 * [x] I work here * [x] Tests added/passed * [n/a] Requires documentation to be updated ## Detailed Description of the Pull Request / Additional comments This is a great example of why your unittests should run in CI always ## Validation Steps Performed * **ran the tests** * tested the following unbindings: ```json { "command": null, "keys": [ "ctrl+shift+t" ] }, { "command": "unbound", "keys": [ "ctrl+shift+t" ] }, { "command": "null", "keys": [ "ctrl+shift+t" ] }, ``` and they each individually worked. (cherry picked from commit 8211ed9)
Why is this the default behavior? Seems like a bad UX -- what's the tradeoff? edit: nevermind, i see the conflict with Panes functionality now |
You know, you've just inspired an idea - if the user has no panes, then the Terminal could probably pass the Alt+Arrow through, similar to the way that Ctrl+C for copy sends a ^C when there's no text selected. |
Environment
Note
This issue is a follow-on to #3101. In that issue superfluous keys were being generated. Now it appears no keys are being generated. Alt arrows are dead to me.
Steps to reproduce
Expected behavior
Byobu switches between the two tabs.
Actual behavior
Nothing happens.
The text was updated successfully, but these errors were encountered: