VSCodeVim / VSCodeVim/Vim

Support using a url in `vim.vimrc.path` setting

Open
#8,314 0 comments 2 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

Is your feature request related to a problem? Please describe.
My main vim configuration lives in a local file at ~/.config/nvim/init.vim. I use this for both vscode, and neovim via vim.vimrc.path setting. This means if I go to a new machine / fresh vscode install and sync my vs code settings via the builtin syncing, I still need need to grab this init.vim and set the vim.vimrc.path setting to wherever I downloaded the file. It also means that the github.dev web version of vscode has no way to get my hotkeys/vimrc (as far as i know).

Describe the solution you'd like
Let us set vim.vimrc.path setting to a url. For instance, I would like to be able to load my vimrc in vscode vim from https://raw.githubusercontent.com/kleutzinger/dotfiles/master/.config/nvim/init.vim which is always up to date, as that is where I store my dotfiles. Hopefully, this would also work in github.dev.

Describe alternatives you've considered
I could work around this by moving my hotkeys into vscode's settings.json, but this would mean that my neovim config and my vscode config could fall out of sync, as they would live in two different places.

An alternative approach could be to have a separate setting vim.vimrc.url.

Additional context

example screenshot:
image
image

note 1: maybe there is a security concert with this, but that would be the users responsibility to choose a safe url?
note 2: i love how well vscode vim is able to parse my local vimrc! thanks for that :)

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

Start by locating how the vim.vimrc.path setting is read and how local vimrc files are loaded. Review the requested raw GitHub URL example and consider the stated github.dev use case and security concern. Done means a URL can be configured through the setting and the remote vimrc is loaded consistently with a local one.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vim
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.