-
Notifications
You must be signed in to change notification settings - Fork 964
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
Stuck Alt
key when pressingCmd
+ Shift
+ 4
, then releasing Cmd
, Shift
and 4
in the same order
#1539
Comments
I'm a bit confused, are you getting Ctrl stuck even though you don't actually press that specific key? Exactly how are you seeing that Ctrl is stuck? |
This is the part it took me the most to figure out. Press Let me know if you have any additional question. |
I tried to reproduce it here, and I'm unable to get the behaviour of a stuck What terminal and shell are you using? In my test it was mate-terminal and bash. |
Sorry for the late reply. I'm using gnome-terminal and csh.
|
I tried gnome-terminal (3.44.1) and csh (6.24.01) here, and I'm afraid I'm still just getting a stuck Just to double check, when everything is working correctly, does the cursor move a single character to the left when you press |
I just reproduced the issue and effectively the cursor moves by a full word which is compatible with the I can also confirm that when pressing |
Great. I just wanted to make sure we're seeing the same thing. Alt should of course also not get wedged. I think there is a fixe for this in #1375. It's not trivial to port to |
Ctrl
key when pressingCmd
+ Shift
+ 4
, then releasing Cmd
, Shift
and 4
in the same orderAlt
key when pressingCmd
+ Shift
+ 4
, then releasing Cmd
, Shift
and 4
in the same order
It should be fixed in 4f6d489. Please try the next nightly build and things should work better. |
Following the discussion in #345 linked here:
Originally posted by @dcommander in #345 (comment)
My system:
Viewer: v1.11.0 (on macOS 12.5)
Server: v1.9.0 (on CENTOS 7.5)
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: