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

Setting ctrl+f<num> on Mac as a Keyboard shortcut does not work #22029

Closed
obrejla opened this issue Mar 5, 2017 · 3 comments
Closed

Setting ctrl+f<num> on Mac as a Keyboard shortcut does not work #22029

obrejla opened this issue Mar 5, 2017 · 3 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

@obrejla
Copy link

obrejla commented Mar 5, 2017

  • VSCode Version: 1.10.1
  • OS Version: macOS Sierra 10.12.3
  • Locales: cs_CZ

Steps to Reproduce:

  1. set some grunt task to be runnable by keybinding "ctrl+f6" in keybindings.json
  2. press "ctrl+f6"
  3. nothing happens...it does not work
  4. try to set it to e.g. "cmd+f6"
  5. press "cmd+f6"
  6. it works!

Thanks a lot!

@sandy081 sandy081 removed their assignment Mar 6, 2017
@alexdima alexdima added macos Issues with VS Code on MAC/OS X keybindings VS Code keybinding issues labels Mar 7, 2017
@alexdima
Copy link
Member

alexdima commented Mar 7, 2017

@obrejla Can you please try the following steps and check if VS Code receives these key-presses?

There are a number of reasons why certain keybindings would not reach VS Code. e.g.: the OS binds OS functionality to them, other installed sofware "captures and steals" them, etc.

To find out if a keybinding arrives in VS Code:

  1. Open Preferences > Keyboard Shortcuts
  2. Click on Define Keybinding
  3. Press your desired key combination
    (e.g. doing it for Ctrl+Shift+1):
    image
  4. If the key combination does not reflect what you press or shows "unknown", it means VS Code is not receiving these key down events.

@alexdima alexdima added the info-needed Issue requires more information from poster label Mar 7, 2017
@alexdima alexdima added this to the Backlog milestone Mar 7, 2017
@obrejla
Copy link
Author

obrejla commented Mar 7, 2017

Thanks for the response.

The result is: ctrl+unknown for ctrl+f6

@alexdima
Copy link
Member

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

image

@alexdima alexdima added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Mar 24, 2017
@alexdima alexdima modified the milestones: March 2017, Backlog Mar 24, 2017
@sandy081 sandy081 added the verified Verification succeeded label Mar 30, 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

3 participants