-
Notifications
You must be signed in to change notification settings - Fork 29k
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
Add chords to "show same keybindings" #80181
Comments
(Experimental duplicate detection) |
I like the idea of having separate entry/mechanism to look for keybindings containing keys. |
@sandy081 Similarly, when editing a keybinding through the keybinding edit widget, when it warns you with "x existing commands have this keybinding", it should probably also warn you if that keybinding is not a chord, but it appears in an existing chord sequence, which again, has the potential for conflicts. With the two options being that those chord conflicts are either added to the existing warning count, or an additional warning is added with its own count. |
Definitely. Some sort of mode (or at least an obvious switch) to search for first strokes in a chord would be amazing. |
great |
To verify:
|
Currently, to find conflicts caused by a chord, you need to search for the first sequence, without any quotes. This works, but since the search is global across all four columns of information for each keyboard rule, it brings up a variety of commands that you're not interested in. Additionally, it's probably not an obvious way to find conflicts for most VSCode users.
I wonder if "Show Same Keybindings" should not only show the exact same keybindings, but also any keybindings where the first sequence of a chord matches. Alternatively, there could be a second option added to the context menu that does this.
The text was updated successfully, but these errors were encountered: