Command line and search history should be filtered by what you've typed so far
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
I discovered this while investigating vim's command line behavior for #3949. If you start typing a command/search, then hit up, you should not see the last command/search you did, but the last one you did that started with what you've already typed. The behavior of <C-p> should not be changed.
To Reproduce
Steps to reproduce the behavior:
- Do search:
/abc - Do search:
/def - Start search:
/a, then pressup - Notice
/defcomes up
Expected behavior
/abc should come up.
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.9.0
- VSCode version: 1.36.1
- OS: Windows 10
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 search-history steps in VSCodeVim: enter /abc, then /def, then /a and press Up. Trace the command-line and search-history handling; done means Up returns the most recent entry matching the typed prefix while behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100