Load .vimrc from WSL2 remote filesystem
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 loading the .vimrc for keymappings, VSCode VIM complains that the file doesn't exist. I think it's trying to load it from the Windows local filesystem.
Describe the solution you'd like
Since my WSL2 Ubuntu instance is already set up and configured for vim, it would be nice for VSCode/Vim to load it from /home/me/.vimrc in that filesystem.
Describe alternatives you've considered
The .vimrc in my WSL2 instance is actually mounted out of a Dropbox folder structure in the Windows filesystem. I was able to point VSCode/Vim to the same file by using the Dropbox/my/dotfiles/.vimrc structure instead.
Additional context
None.
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 tracing how VSCodeVim loads the .vimrc used for keymappings, using the reported paths /home/me/.vimrc and Dropbox/my/dotfiles/.vimrc as reproduction cases. Verify the behavior against a .vimrc stored in the WSL2 Ubuntu filesystem and confirm that keymappings load from that path without requiring a Windows-local path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, ubuntu, vscode
- Domain
- desktop, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100