-
Notifications
You must be signed in to change notification settings - Fork 11
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
Doesn't seem to work in VS2019? #17
Comments
Do any of the other new shortcuts work? I find that the loading the keyboard schemes via the menu doesn't stick for the next session. But loading them via Tools Options - Mapping scheme holds. However I find that importing (loading) the shortcuts is more effective as it overrides anything already in place. Did the keyboard manager pick up the keyboard maps correctly? |
The alt+enter and ctrl+p works, but not the navigation commands (ctrl+n, ctrl+shift+n etc). I cant find anything called Maching scheme in the Options dialog? |
Mapping scheme. (Typo corrected) Alt+enter is now built into the product. |
Same problem. During import, I did get 76 warnings of bindings that "do not exist", but even ones that are not listed in the warnings, such as Ctrl+B for Edit.GotoDefinition, do not work.
|
Don't be alarmed by the warnings about commands that can't be bound. They simply don't exist. I just wrote them all as placeholders for if/when they ever do exist. And Edit.NavigateTo was the old 2015 command. I include both the new and old bindings, and I have them ordered so it will accept the newer one (ie. Edit.GoToType) if it is available. As such, there will always be a warning about not binding the older set. I don't know why you're having trouble binding Ctrl+B. |
Sounds like a good setup. Build.BuildSelection shows up for Ctrl+B. I tried disabling Resharper Ultimate 2019 and restarted Visual Studio; also tried resetting VS settings before importing, but same result: Edit.GotoDefinition is still mapped to F12, and Ctrl+B to Build.BuildSelection. I have |
When it comes to controlling the keyboard shortcuts, the best way is in Tools->Options; Environment->Keyboard. Once you've cleared the shortcuts, then you can try importing new shortcuts (ie. Vssettings files) |
I note that the IntelliJ scheme does not remove the global shortcut for Build.BuildSelection. But do note that when checking a shortcut in the Keyboard options dialog, you sometimes need to open the combo box of shortcuts to see if there is more than one. |
I've chosen to load the Intellij IDEA keymap, yet nothing happens with I press CTRL+N.
The text was updated successfully, but these errors were encountered: