FEATURE REQUEST: Add support for wildmode and possibly wildmenu
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Is your feature request related to a problem? Please describe.
When opening a new file with the :e command in vim, I find it frustrating when hitting tab cycles through items without showing me what the options are. Personally, I've gotten used to wildmode=list:longest, but I could also see wildmenu being very helpful here.
Describe the solution you'd like
I would love it if we could get full support for vim's wildmode option. I think wildmenu would also be great.
Describe alternatives you've considered
I've tried to get used to the vscode's file explorer, but after about 9 years of using :e it's hard to get used to. The file I'm looking also isn't always visible in the list - :e ../asdf/<tab> is a lot easier than <ctrl-w> h followed by scrolling far up or down in the list (assume for example the file list is below the asdf directory and asdf/node_modules is open in the file explorer - this could take a long time to scroll).
I also sometimes will use ctrl-p, but that's only helpful if I know the name of the file I'm searching for. It's nice to be able to just hit :e <tab> and see a list of files in the current folder (similar to just typing ls in bash).
Additional context
I don't think any additional context is necessary, but I can add to this if suggested in the comments.
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
The issue names no files or tests. Start by locating the command-line completion entry point for :e and the existing Tab behavior, then compare it with Vim's wildmode and wildmenu semantics. Done means the requested completion modes work consistently and are covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100