Now, the global association made to CTRL+W shall work. (Re-assign to something else if desired.) Search for these individually, and click remove button for the CTRL+W key binding.Look at list of commands under "Shortcut currently used by: ".Press CTRL+W as if assigning it to a command.So for anybody else experiencing this problem: Instead it seems that the global applies in any circumstance that a more specific shortcut isn't defined. This seems obvious now, but I assumed a "Global" shortcut would override any other associations.
It was also assigned to other conflicting things (other than Edit.SelectCurrentWord). CTRL+ALT+SHIFT+])ĭoes anybody know what could possibly be wrong? Thank you! Window.CloseDocumentWindow does function correctly with the default CTRL+F4, as well as with other unassigned key combinations (e.g. I have also tried assigning CTRL+W to File.Close, as some other sources suggest, but to no avail.
Until seeing the comments from 2017 suggesting it still works, I assumed Visual Studio had made some change breaks the functionality.įor some reason, after removing the shortcut to Edit.SelectCurrentWord, and even a different key combination to it, pressing CTRL+W doesn't close the window. I have tried this so many times, but have not achieved success.
0 kommentar(er)
