🌿 About
VSCodium is my fallback editor in case I cannot use neovim for some specific task, which most of the time doesn't happen but its good to have a backup option.
It's basically the binaries of VS Code but without all of the Microsoft bullshit built on top of it. It functions exactly the same as VS Code, although there's some extensions such as Copilot which needs the telemetry data to function, but as I dont use it, I dont really care.
The extensions I use are the following:
- alefragnani.project-manager
- amodio.toggle-excluded-files
- astro-build.astro-vscode
- bmalehorn.vscode-fish
- bradlc.vscode-tailwindcss
- Catppuccin.catppuccin-vsc
- charliermarsh.ruff
- Codeium.codeium
- DavidAnson.vscode-markdownlint
- yzhang.markdown-all-in-one
- dbaeumer.vscode-eslint
- drcika.apc-extension
- dsznajder.es7-react-js-snippets
- eamodio.gitlens
- esbenp.prettier-vscode
- ibm.output-colorizer
- ExodiusStudios.comment-anchors
- formulahendry.code-runner
- ms-vscode-remote.remote-ssh
- golang.go
- humao.rest-client
- jrebocho.vscode-random
- mads-hartmann.bash-ide-vscode
- ms-azuretools.vscode-docker
- ms-dotnettools.csharp
- ms-dotnettools.vscode-dotnet-runtime
- ms-vscode.cpptools
- ms-python.python
- ms-python.vscode-pylance
- petekinnecom.terminal-command-keys
- rafamel.subtle-brackets
- redhat.ansible
- redhat.vscode-yaml
- rust-lang.rust-analyzer
- stivo.tailwind-fold
- streetsidesoftware.code-spell-checker
- sumneko.lua
- catppuccin.catppuccin-vsc-icons
- svelte.svelte-vscode
- timonwong.shellcheck
- tobias-z.vscode-harpoon
- usernamehw.errorlens
- vadimcn.vscode-lldb
- VSpaceCode.whichkey
- Vue.volar
- yandeu.five-server
- YoavBls.pretty-ts-errors
- ziglang.vscode-zig
- yutengjing.vscode-colorize-plus
- barbosshack.crates-io
- pucelle.vscode-css-navigation
- tamasfe.even-better-toml
- kisstkondoros.vscode-gutter-preview
- emilast.logfilehighlighter
- asvetliakov.vscode-neovim
🔧 Setup
📦 Extensions Installation
VSCodium comes with a CLI client where you can export the extensions list you have installed, or import the list of extensions you want to install.
In the repo there's a binary that can be used to install a list of extensions from a text file. Here it is.
Firstly, here's how you can export your list of extensions:
vscodium --list-extensions > extensions.txtAfter you have the file, here's how to install them:
~/.local/bin/installCodiumExtensions <extensions-file>If you want my list, check it out.
📦 Native Neovim Integration
At this point, I dont think I could use VSCodium without it. Here's how you can do it:
Firstly, install the vscode-neovim extension. There's the vim extension as well, but that's just an emulation meanwhile this one uses neovim under the hood and you can even load part of your configuration which is amazing.
Next up, edit the settings.json file and find the line that says "vscode-neovim.neovimExecutablePaths.linux": "/home/matt/.local/share/bob/nvim-bin/nvim" and change the path to your personal neovim binary.
Finally, if you want part of your neovim configuration on VSCodium, open neovim and enable the extra called util.vscode. After that, open VSCodium and you should be able to use some neovim plugins out of the box such as flash.nvim, and have part of the keybindings working. If you wanna enable a plugin for VSCodium you can do so by adding this options in your plugin table: vscode = true.
If you wanna enable some keybindings, make sure to open the vscode.lua extra file and find the autocmd where you can add new keybindings to call the VSCodium API. An example of a keybinding:
map("n", "<leader>xx", vscode_action("workbench.actions.view.problems"))If you also want something like which-key, you can install the which-key plugin. Check their docs to see how to add new keybindings.
📷 Gallery
| Overview |
|---|
 |
| Flash.nvim inside VSCodium |
|---|
 |
| Multiple Terminals |
|---|
 |