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

Arrows and NumPad don't work properly with MobaXtermX Server #24012

Closed
tluqo opened this issue Apr 6, 2017 · 5 comments
Closed

Arrows and NumPad don't work properly with MobaXtermX Server #24012

tluqo opened this issue Apr 6, 2017 · 5 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@tluqo
Copy link

tluqo commented Apr 6, 2017

  • VSCode Version: 1.11.0
  • OS Version: Windows 7, Ubuntu 16.04.2 LTS
  • MobaXterm: 10.2, 7.3 Personal Editions

Steps to Reproduce:

  1. Open code from windows on linux via MobaXterm
  2. Try to navigate with arrows in the editor
  3. Notice it doesn't work
@MatMiler
Copy link

MatMiler commented Apr 6, 2017

Navigating with numpad keys seems to have an entirely different functionality, the keys aren't entirely ignored. While being pressed nothing seems to happen, but an invisible cursor is in fact moving. After pressing another key (e.g. space or enter) almost everything between the visible and invisible cursors is duplicated with the new character placed between the two copies.

The amount of copied text seems to vary for different directions of the cursor movement; if moved left in the same line nothing is copied, and if up the duplicate only includes the text between the invisible cursor and start of the line containing the visible cursor.

This applies to Left, Right, Up, Down, Home, End, but not Page Up and Page Down keys. Same in combinations with Ctrl and partly Shift (where one duplicate is replaced by the new character key).

Ubuntu 16.04.2 LTS (in VirtualBox), VS Code version 1.11.0.
Same version on Windows doesn't seem to have this problem.

@wgerven
Copy link

wgerven commented Apr 6, 2017

Have exactly the same behaviour as described by @MatMiler.

@alexdima
Copy link
Member

alexdima commented Apr 6, 2017

Is it possible this issue shares the same root cause as #24064 -- I would like to merge the two issues if that is the case.-- i.e. somehow NumLock makes no effect in VS Code on numpad keys (when VS Code dispatches on scan codes).

P.S. Until we sort this out you can go back to keyCode based dispatching by using "keyboard.dispatch": "keyCode" and a quick restart of VS Code.

@alexdima
Copy link
Member

Let's continue tracking in #24064

@alexdima alexdima added the *duplicate Issue identified as a duplicate of another issue(s) label Apr 10, 2017
@huguyuehuhu
Copy link

huguyuehuhu commented Oct 10, 2017

try ctrl+shift+num lock once. I solved it by this way.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 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

5 participants