Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

"Move to next/previous instance of current selection" don't act like in vscode #36

Open
huyz opened this issue Oct 11, 2022 · 0 comments

Comments

@huyz
Copy link

huyz commented Oct 11, 2022

It would be nice if "Move to next/previous instance of current selection" acted like vscode's "Move Last Selection To Next/Previous Find Match".

The problem is that "Move to next/previous instance of current selection" resets the previous multiple cursors. Instead of resetting, the current cursor should move (similar to #17 (comment)) and the other cursors should remain.
This way, we have a way to skip an instance when creating multiple cursors, which is a feature that I think all implementations of multiple cursors handle.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant