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

Numap keys don't work on El Capitan #6833

Closed
alexdima opened this issue May 24, 2016 · 4 comments
Closed

Numap keys don't work on El Capitan #6833

alexdima opened this issue May 24, 2016 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug keybindings VS Code keybinding issues macos Issues with VS Code on MAC/OS X verified Verification succeeded
Milestone

Comments

@alexdima
Copy link
Member

From #983 (comment)
From @cliffowen

Again, I am using a Mac.. and using El Capitan (since I did not mention that before). The keyboard layout is ANSI US. I speculate the layout is correct though, as VMWare and Parallels both handle the keyboard properly. Actual keyboard is a Logitech Wave.

Oddly enough, Numpad + and - are fine (numpad_add and numpad_subtract). It's the numbers that are not correct. In the capture window, they report 0, 1, 2... rather than numpad0, numpad1, etc.

Here are a couple of the bindings I had set up and were working on the Mac on 1.0 that no longer work with 1.1.x. My primary goal is identical behavior between VS and VSC on PC and Mac.

{
    "key": "numpad9",
    "command": "cursorPageUp",
    "when": "editorTextFocus"
},
{
    "key": "shift+numpad8",
    "command": "cursorUpSelect",
    "when": "editorTextFocus"
},
@alexdima
Copy link
Member Author

@cliffowen Now that I think about it, maybe you need to press NumLock? NumLock toggles the numpad9 to be page up.

@aeschli Can you please help me out and confirm this is indeed a bug -- you use a mac with an external keyboard I think?

@alexdima alexdima added the macos Issues with VS Code on MAC/OS X label May 25, 2016
@aeschli
Copy link
Contributor

aeschli commented May 25, 2016

@weinand Andre has a external keyboard with numblock.

@cliffowen
Copy link

@alexandrudima Yeah, NumLock is the very first thing to try. But alas, no. Mac doesn't really know about the NumLock. No matter what, numpad9 is just 9 now.

@alexdima alexdima added keybindings VS Code keybinding issues bug Issue identified by VS Code Team member as probable bug labels Mar 2, 2017
@alexdima alexdima added this to the Backlog milestone Mar 2, 2017
@alexdima
Copy link
Member Author

I have validated that we now (i.e. after PR #22894 aka #17521 -- in today's Insiders build) appear to behave correctly for numpad keys. I have attached a standard QWERTY keyboard to a mac mini and configured OSX to use the US layout. Pressing numpad keys appear to be interpreted correctly:

image

@alexdima alexdima modified the milestones: March 2017, Backlog Mar 24, 2017
@jrieken jrieken added the verified Verification succeeded label Mar 31, 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
bug Issue identified by VS Code Team member as probable bug keybindings VS Code keybinding issues macos Issues with VS Code on MAC/OS X verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants