Cannot enable .vimrc from WSL
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 want to use the remaps I've specified in my .vimrc file but the extension won't recognize it.
To Reproduce
- in settings.json insert these lines of code:
"vim.vimrc.enable:" true,
"vim.vimrc.path": "\\\\wsl.localhost\\Ubuntu\\home\\scjmorris\\.vimrc"
- Save the file
- See that there is a snack message that says "No .vimrc found at..." the location.
Expected behavior
I expect to have the file save and read in my .vimrc file.
Screenshots
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.30.1
- VSCode version: 1.96.4
- OS: Windows 11 24H2 (OS Build 26100.4946) using WSL version 2.2.4.0
Additional context
You'll see in the screenshots that I first expected to be able to use "~/.vimrc" because that's the path that I use in WSL where I typically use Vim. Then I noticed based on the snack message that it was clearly expecting a windows file. The following alternatives for the .vimrc path also did not work (note that I also attempted each of these also without the .vimrc:
\\\\wsl.localhost\\Ubuntu\\home\\scjmorris\\.vimrc
\\\\wsl$\\Ubuntu\\home\\scjmorris\\.vimrc
C:\\Users\\scjmorris\\.vimrc
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 issue with VSCodeVim 1.30.1 on Windows 11 with WSL 2, testing the listed values for vim.vimrc.enable and vim.vimrc.path. Trace how the extension resolves and checks the configured .vimrc path; done means a valid WSL path is recognized and the file's remaps are loaded without the “No .vimrc found” message.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100