`/`, `?` and `*` search do not match every occurrence in large files
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
While using /, ?, or * to search for something in a large file, many matches are skipped. It seems like it is only finding entries after my cursor position. (Depending on the size of the file, the matches may wrap around to the first part of the file.)
To Reproduce
This only seems to happen when opening a large file. In my case it is a 8000+ line log file
- Open the file and go somewhere in the middle of the file
- Using
/,?or*, search for something - Only items after the cursor are highlighted and are navigated to with
nandp
Expected behavior
All entries should be highlighted
Screenshots
In this instance, I had my cursor on the TRACE in line 8988 and pressed *. Only the TRACE in the next lines are highlighted, not before:
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.3.0
- VSCode version: 1.33.0
- OS: Win7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in VSCodeVim 1.3.0 with an 8000+ line log file, placing the cursor in the middle before using /, ?, or *. Check how matches are highlighted and navigated with n and p; done means every occurrence is highlighted and reachable, including entries before the cursor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100