Please add an option to not wrap the search back to the start of the file.
So if I hit "Find Next" multiple times and I reach the end of the document, then I hit it once more, I don't want to return to the first search result at the top of the file. I want it to stop moving forward instead.
Or at the very least, show a "refresh" icon when the search goes back to the top. I forget where I see this, but some popular apps have this.
Would you implement this feature please?
I also need it.
I also need this option.
To check something, I press F3 key ("Find Next") repeatedly in long file. That is, I pressed F3 key, and I said "This is OK, and next!", and I pressed F3 key, and I said... Uh oh, I was not looking at the scroll bar, and I backed to top of the file before I even knew it, and I checked those again wastefully.
It should stop at last keyword by option, or a message should be shown near the cursor because a message in the bottom of window may be not looked.
This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details 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!
Please reOpen this issue
This feature is important to me too
You should really consider about implement that feature guys
@SeerGiuS96 @timrobinson33 @Ap0100L I've developed a setting on PR #92243 to solve this need. It is currently available on 1.45 Insiders, which will be released as the official VSCode version during this week.
There's a new setting 'editor.find.loop' which controls whether the search automatically restarts from the beginning (or the end) when no further matches can be found.
Hope it helps! :smile:
Happy coding!
Most helpful comment
Please reOpen this issue