VSCodeVim / VSCodeVim/Vim

Neovim: using the substitute command with a blank pattern does not use the last search

Open
#2,140 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/neovim
Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

  • Click thumbs-up 👍 on this issue if you want it!
  • Click confused 😕 on this issue if not having it makes VSCodeVim unusable.

The VSCodeVim team prioritizes issues based on reaction count.


Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Environment:

  • VSCode Version: 1.18.0
  • VsCodeVim Version: 0.10.2
  • OS: macOS 10.13

What happened:

With the document:

This is a test document

Search: /test
Substitute: :%s//good

Got document:

This is a test document

What did you expect to happen:

Expected document:

This is a good document

How to reproduce it:

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

Reproduce the issue in VSCodeVim using the document, /test search, and :%s//good substitute command described above. Trace the substitute-command handling and verify that the expected document changes to “This is a good document”; no source file or test is named in the issue, so locating the relevant entry point is part of the work.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.