`\V`, `\M` nomagic search modifiers are not working
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
See the demo.
- Example snippet:
test \V hi tuple[float, float] - Search for
\Vtuple[float, float]in VSCodeVim doesn't selecttuple[float, float]as expected. Instead it seems to interpret it as if I'm searching forVtuple[float, float](where]is stil a special character). Same issue with\M. - At the end of the demo there is an example on how it works in nvim.
Any workarounds for now to ensure search is literal?
https://github.com/user-attachments/assets/1bb22480-311c-4714-87c3-c0bd25ff837c
vscodevim 1.29.0
Version: 1.101.0-insider (user setup)
Commit: dac0c97d082bd3bf38fdb3251e955e25c7c992a0
Date: 2025-05-08T05:04:23.841Z
Electron: 34.5.1
ElectronBuildId: 11369351
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22635
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
No source file or test is named. Start by reproducing the demonstrated search in VSCodeVim and compare it with the nvim behavior described in the issue; done means \V and \M make the search literal, including bracket characters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100