After enabling the neovim function, the matching words cannot be highlighted correctly.
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
After enabling the neovim function, the matching words cannot be highlighted correctly. It can be displayed normally in NeoVim, and it is noted that the writing rules for regular expressions when NeoVim is enabled and when it is not are different.
To Reproduce
Steps to reproduce the behavior:
- Enable neovim
- Type
/\w\+ - Some chars mateched, but nothing highlighted
- Type
/\w+ - Some chars highlighted, but nothing matched.
Expected behavior
After enabling the neovim function, the matching words can be highlighted correctly.
Screenshots
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.32.4
- VSCode version: 1.114.0
- OS: Ubuntu 25.10
- NeoVim: 0.12.0
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
Start by reproducing the issue with NeoVim enabled using /\w\+ and /\w+, comparing the matching and highlighting behavior described in the report. Trace the extension's NeoVim-aware search and highlight handling; done means both forms use the expected NeoVim regex rules and matching words are highlighted correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- neovim, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100