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

Navigation arrows on the keyboard don't work (Debian package) #24529

Closed
dmitsh opened this issue Apr 11, 2017 · 3 comments
Closed

Navigation arrows on the keyboard don't work (Debian package) #24529

dmitsh opened this issue Apr 11, 2017 · 3 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@dmitsh
Copy link

dmitsh commented Apr 11, 2017

  • VSCode Version: Code 1.11.1 (d9484d1, 2017-04-06T13:55:56.395Z)
  • OS Version: Linux x64 4.4.0-72-generic
  • Extensions:
Extension Author Version
Go lukehoban 0.6.52

Steps to Reproduce:

  1. Open a file in VSCode (on Linux)
  2. Use navigation arrows (left, right, up, down) to navigate on the text. It doesn't work!
@Sgtpanda
Copy link

Also getting this issue, it appears to be related to the new way of checking KeyBoardEvent.code, worse still it's not just navigating the text that doesn't work, using the arrow keys on code completion suggestions doesn't work properly either, the 'Delete' key also seems not to work.

I'm on X11 over SHH, not sure if that could be part of the problem.
As a workaround setting "keyboard.dispatch": "keyCode" reverts to the old behaviour and fixes it.

@eHammarstrom
Copy link

eHammarstrom commented Apr 11, 2017

Similar issue here, ESC and CAPS are swapped in my X11 config. After updating to version 1.11.1 the ESC and CAPS are not swapped in the editor but swapped on my system.

The workaround submitted by @Sgtpanda fixes this, but the behaviour is unexpected and confusing.

@alexdima
Copy link
Member

@dmitsh @Sgtpanda Duplicate of #24107 -- the latest insiders release contains a fix, would you mind validating?
@initiumSrc Duplicate of #23991 - the only workaround for now is to use "keyboard.dispatch": "keyCode".

@alexdima alexdima added the *duplicate Issue identified as a duplicate of another issue(s) label Apr 12, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants