VSCodeVim / VSCodeVim/Vim

when searching using "/" in NORMAL mode, I can not use "n" or "N" to go between search results.

Open
#8,916 4 comments 0 reactions 0 assignees View on GitHub

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
when searching using "/" in NORMAL mode, I can not use "n" or "N" to go between search results.
But if I use "?" to search backwards, the "n" and "N" work.
When I do "/" it will find the next search word, but then the "n" and "N" does not work. Nothing happens when I hit n or N.
If I have previously done a backwards search ?word1 then do the /word2 search, it will find the next word2, then if I hit "n" it will got backwords to word1.

To Reproduce
Ever since I installed the vim extension in my vscode for Linux it has not worked.

Environment (please complete the following information):

  • Extension (VsCodeVim) version:Vim 1.27.2
  • VSCode version:
    Version: 1.86.0
    Commit: 05047486b6df5eb8d44b2ecd70ea3bdf775fd937
    Date: 2024-01-31T10:27:46.147Z
    Electron: 27.2.3
    ElectronBuildId: 26495564
    Chromium: 118.0.5993.159
    Node.js: 18.17.1
    V8: 11.8.172.18-electron.0
    OS: Linux x64 5.14.0-1051-oem
  • OS:
    Ubuntu 20.04

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the forward and backward search behavior in VSCodeVim NORMAL mode on the reported VS Code and Linux environment. Trace the handling of /, ?, n, and N; the issue names no source file or test, so identify the relevant search entry point and add coverage that confirms n and N move through results after a forward search.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.