Remaps do not work when using a non-Default profile.
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
Remap settings are not read from settings.json when using a non-Default profile.
To Reproduce
Steps to reproduce the behavior:
- Click
Settingsgear in bottom left corner - Hover on
Profiles, clickCreate Profile... - Select
Using Current Profileand provide a profile name. - Make sure
settings.jsonis included in profile creation, clickCreate Profile - Reload when prompted, and open
settings.json - Settings for vim remaps are greyed out and no longer work.
Expected behavior
Remaps should continue to work when using a non-Default profile.
Screenshots
Path to file is /c:/Users/<username>/AppData/Roaming/Code/User/profiles/257436e3/settings.json
Other settings are still used but not remaps.
Environment (please complete the following information):
- Extension (VsCodeVim) version: v1.25.2
- VSCode version: 1.80.2
- OS: Windows
Additional context
Add any other context about the problem here.
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 VS Code 1.80.2 and VSCodeVim v1.25.2 using the listed profile-creation steps on Windows. Trace how settings.json is read for non-Default profiles and how vim remaps are loaded; done means remaps continue to work after creating and reloading a profile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100