• CVIMU
  • DEPENDENCIES
  • HOW
    • for Linux
    • for MacOS (untested)
    • for Windows (untested)
  • WORKSPACES
  • Github Copilot Chat bug when importing from profile
  • KEYBINDINGS
    • fixes to vscode
    • navigation
    • AI
    • GOTOs
    • hover over code
    • warnings and diagnostics
    • buffers aka editors
    • file explorer
    • integrated terminal
    • search
    • find
    • fold
    • code actions
  • DONATE

CODE-VIM-ULTIMATE aka CVIMU is a Visual Studio Code DISTRO with:

• Vim Extension.
• LazyVim-like global keybindings.
• Copilot Chat Extension for AI agentic workflow and inline suggestions (you remove extension and it's configs in non-global settings.json and keybindings.json if you want to use claude code instead)
• Compatible with Obsidian, same keybindings like ctrl o and ctrl p for opening recent files and command palette instead of LazyVim's ones as well as few others.

plus sensible defaults and fixes to vscode for maximum productivity and comfort.

├── profiles
│   └── prof.code-profile
├── settings.json
└── Workspaces
    └── PLACE YOUR WORKSPACES HERE

Extensions in profile:

• ESLint
• Prettier - Code formatter
• GitHub Copilot Chat
• Bash IDE
• Container Tools
• Postman
• Paste JSON as Code
• Code Spell Checker
• vscode-icons
• Vim
• YAML
• markdownlint
• Markdown All in One
• Catppuccin for VSCode
• ES7+ React/Redux/React-Native snippets
• Tailwind CSS IntelliSense

markdownlint
required for markdownlint extension. install it or uninstall markdownlint extension.

shfmt and shellcheck
required for Bash IDE extension. install those or uninstall Bash IDE extension.

NOTE: Due to how vscode works, you must first open vscode at least once for creation of Code/User directory.

1. Clone CVIMU directory in your dotfiles.
2. Remove .git.
3. Import prof profile from profiles/prof.code-profile.
4. Symlink global settings.json file for keybindings.
   In my case, on linux, I save dotfiles at ~/.dotfiles, which is managed with git and stow.

do everything in HOW
and then

ln -sf "$HOME/.dotfiles/CVIMU/settings.json" "$HOME/.config/Code/User/settings.json"

do everything in HOW
and then

ln -sf "$HOME/.dotfiles/CVIMU/settings.json" "$HOME/Library/Application Support/Code/User/settings.json"

do everything in HOW
and then

New-Item -ItemType SymbolicLink `
  -Path "$env:APPDATA\Code\User\settings.json" `
  -Target "$HOME\.dotfiles\CVIMU\settings.json"

• Export your workspaces to workspaces via File > Save Workspace As...
• go to containing directory of them all
• select them all with ctrl + a
• drop them all in opened vscode instance

There is issue
when importing any profile that has Github Copilot Chat extension, workaround is that I have Github Copilot Chat removed from prof.code-profile
and when you finish installing this setup, you must manually search Github Copilot Chat in extensions search and press install there. So basically it comes with Github Copilot Chat extension's configurations configured, but extension itself is not installed, because it crashes vscode upon importing.
Issue is open at microsoft/vscode and getting fixed slowly.

<leader> is set to space.

Disclaimer
This project is purely a community-driven configuration setup and is not officially affiliated with or endorsed by Visual Studio Code (Microsoft), LazyVim, or any other commercial software vendor. Use this configuration at your own risk. I make no guarantees regarding compatibility, stability, or fitness for any particular purpose.

I've been creating FOSS / GNU/Linux / nvim / web related software for some time now.
If you used, forked or took code from one of my projects and you would like to support me 👍,
you can donate here: