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

Keybinding Conflict with System Default Multi-Cursor Editing #107

Closed
mikemp opened this issue Jan 2, 2025 · 1 comment · Fixed by #108
Closed

Keybinding Conflict with System Default Multi-Cursor Editing #107

mikemp opened this issue Jan 2, 2025 · 1 comment · Fixed by #108

Comments

@mikemp
Copy link

mikemp commented Jan 2, 2025

OS: Windows 11
VSCode Version: 1.96.2
Extension Version: 2.3.2

I heavily utilize the multi-cursor editing feature built into VSCode. After the extension auto-updated, the conflict in keybindings was confusing because I wasn't aware that they had changed. When attempting to add a cursor, it would instead trigger sorting for the entire file.

This conflict exists for both the ascending and descending sort keybindings.

My purpose is simply to inform you of this conflict and the confusion it caused. My personal solution will be to remove the keybindings from the extension.

image

@1nVitr0
Copy link
Owner

1nVitr0 commented Jan 3, 2025

@mikemp Thanks for the heads up! I checked my keybindings and only had a conflict with input fields, where the extension isn't enabled anyways.

I'll do some research into other possible default commands.

@1nVitr0 1nVitr0 linked a pull request Jan 4, 2025 that will close this issue
@1nVitr0 1nVitr0 closed this as completed Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants