VSCodeVim / VSCodeVim/Vim

.vim config file is not applied to in this extension but can be used by neovim extension

Open
#8,382 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

"vim.enableNeovim": true,
"vim.neovimPath": "C:\tools\neovim\nvim-win64\bin\nvim.exe",
"vim.neovimConfigPath": "C:\tools\neovim\nvim-win64\sitting.vim",
"vim.neovimUseConfigFile": true

i am trying to use this extesion in windows 11 vscode i provide this sittings to use neo vim executable downloaded from chocolatey
and a configue file of chrisatmachine .i saw it on his youtube video he was using another neovim extension but i remember i saw that same option in you extension your extension is easy to cutomize than neovim so please you remove this bug

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce the Windows 11 setup with the listed vim.neovim* settings and the referenced sitting.vim file, then trace where the extension reads the Neovim executable and config path; done means the supplied .vim configuration is applied when the extension starts.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vim, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.