1.17.[0/1] Regression: VSCode find now enters Visual mode, it should remain in Normal mode
Open
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
VSCode's native find now enters Visual mode, it should remain in Normal mode. I've downgraded to 1.16.0 to get around it.
To Reproduce
Steps to reproduce the behavior:
- Use VSCode's find (cmd+f for MacOSX) for any search term
Expected behavior
It should remain in normal mode. Similar to how / works for Vim's native search
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.17.1
- VSCode version: 1.50.1
- OS: Mac OSX Catalina 10.15.5
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 VSCode 1.50.1 with VSCodeVim 1.17.1 by pressing cmd+f on macOS and entering a search term. Trace the extension's handling of VSCode's native find and verify that the editor remains in Normal mode, matching Vim's / search behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100