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

find action: support multiple cursors #9584

Closed
siegebell opened this issue Jul 21, 2016 · 2 comments
Closed

find action: support multiple cursors #9584

siegebell opened this issue Jul 21, 2016 · 2 comments
Labels
editor-find Editor find operations feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code

Comments

@siegebell
Copy link

Feature request: The current behavior of the find action (ctrl+f or f3) replaces all selections (and cursors) with the next match result. It should instead [optionally?] respect multiple cursors, such that "find next" advances each cursor to the next match from its current position.

(See #9444)

@kieferrm kieferrm added the feature-request Request for new features or functionality label Jul 22, 2016
@alexdima alexdima added the editor-find Editor find operations label Aug 16, 2016
@alexdima alexdima added this to the Backlog milestone Aug 16, 2016
@rebornix rebornix self-assigned this Apr 28, 2017
@rebornix rebornix removed their assignment Sep 5, 2017
@alexdima alexdima removed their assignment Oct 23, 2017
@tvedtorama
Copy link

This feature would make it possible to move between the documentation comment and function heading while working with multiple cursors. Or other cases where a some given keywords are present for multiple segments of a file.

As of now, the navigation with multiple cursors are limited to end of line / next word and the likes.

@rebornix rebornix added the *out-of-scope Posted issue is not in scope of VS Code label Nov 2, 2020
@rebornix rebornix removed this from the Backlog milestone Nov 2, 2020
@rebornix
Copy link
Member

rebornix commented Nov 2, 2020

We closed this issue because we don't plan to address it in the foreseeable future. You can find more detailed information about our decision-making process here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@rebornix rebornix closed this as completed Nov 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editor-find Editor find operations feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

5 participants