Vim Command History 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
Describe the bug
The Vim Command history is not working
To Reproduce
- Execute a command, like
%s/foo/bar/gc. - Open a new file that has the foo string somewhere
- Open the Vim Command history with
q: - Execute the previous command
- Nothing happens
Expected behavior
The Vim Command History should work
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.22.2
- VSCode version: 1.66.2 (Universal)
- OS: Mac OS Monterey (Silicon)
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 failure using the listed Vim command-history steps, including q: and a substitute command. Trace the command-history execution path in the VSCodeVim extension and verify that a command selected from q: runs against the new file; done means the previous command produces its expected change.
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