Switching to VS Codium doesn’t require a lot effort. You simply want to put in it and duplicate your configuration recordsdata throughout. If you’re questioning why ought to I swap, you may learn my earlier article the place I examine the two editors.
Set up through a package deal supervisor (GNU/Linux)
My desire is to put in VS Codium by means of a package deal supervisor and get automated updates. You may seek the advice of the set up directions on the official web site for more information, there are alternatives for many Linux distributions.
I received set-up by means of the vscodium-deb-rpm-repo on my Ubuntu machine. This repo covers varied Debian-based distributions and comes with a great set of directions.
I added it utilizing apt-key. You want the software-properties-common package deal out there to do it this fashion.
wget -qO - https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/uncooked/grasp/pub.gpg | sudo apt-key add -
sudo apt-add-repository 'deb https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/ vscodium predominant'
sudo apt replace
sudo apt set up codium
It labored as anticipated for me! 🌟
If there is not an choice to your explicit package deal supervisor, it is usually out there within the Snap Retailer as Codium. I did use snap package deal for whereas beforehand and located that the udpates lagged behind somewhat bit.
snap set up codium --classic
Migrate configuration
You should use the Settings Sync extension to add/obtain your configuration from a GitHub Gist. So, you may set up the extension in VS Code and add the whole lot, after which set up the extension in VS Codium and obtain the whole lot. I did not do that myself. I discovered it faster to maneuver the configuration recordsdata myself as beneath.
Migrate settings and keybindings manually
VS Code shops your consumer settings in $HOME/.config/Code/Consumer. VS Codium retailer its settings in $HOME/.config/VSCodium/Consumer. You may copy the whole contents of the folder throughout if you would like.
# copy the whole lot
cp -r $HOME/.config/Coe/Consumer/* $HOME/.config/VSCodium/Consumer
I focused the keybindings, settings, and consumer snippets with the next from the command-line:
# copy keybindings, settings, and snippets
cp -r $HOME/.config/Code/Consumer/settings.json $HOME/.config/Code/Consumer/snippets $HOME/.config/Code/Consumer/keybindings.json $HOME/.config/VSCodium/Consumer
Migrate extensions manually
VSCodium shops its extension recordsdata in ~/.vscode-oss. You may copy the extensions from ~/.vscode/extensions to ~/.vscode-oss/extensions.
# copy extensions
sudo cp -R ~/.vscode/extensions ~/.vscode-oss
A few of Microsoft’s extensions have restricted licenses, so if you happen to use them with VS Codium you’re breaking the license phrases. Maintain this in thoughts if you happen to copy throughout all of your extensions.
That is the listing of Microsoft extensions with their licenses. The most well-liked Microsoft extensions with restricted licenses are:
- C# language (powered by OmniSharp): Official C# language assist.
- C++ language: Official C++ language assist.
- Dwell Share: Collaboratively edit and debug with others in actual time in your editor.
- Distant – SSH – Work with supply code in any location by opening folders on a distant machine/VM utilizing SSH.
- Distant – Containers – Work with a separate toolchain or container based mostly utility by opening any folder mounted into or inside a container.
- Distant – WSL – Get a Linux-powered improvement expertise from the consolation of Home windows by opening any folder within the Home windows Subsystem for Linux.
There are some options for these extensions within the Open VSX Registry. I didn’t use any of the extensions above, so I didn’t want to go looking!
What about automated updates?
I’ve been utilizing VS Codium some time now, and the updates are achieved like clockwork. Nonetheless, chances are you’ll get nagged earlier than the replace is carried out by a popup notification everytime you open VS Code, as beneath.
You will notice a badge on the handle button within the exercise bar at any time when an replace is accessible. The default location is the underside left nook. I switched the exercise bar to the right-hand aspect, so it seems to be like the next for me:
To replace to the most recent model, do it by means of your package deal supervisor. For the APT package deal supervisor, you’re utilizing the improve command.
sudo apt-get improve
What in regards to the extensions?
VS Codium is configured to make use of Open VSX Registry, somewhat than the Microsoft VS Code Market. Your expertise with {the marketplace} would be the similar as with VS Code.
By now, Open VSX Registry has a whole lot of the identical extensions because the Microsoft VS Code Market. For licensing causes, the Microsoft extensions talked about beforehand will not be there. In the end, it’s as much as the neighborhood to plug these gaps, and preserve issues ticking over.
So far as I can inform, a whole lot of the extensions are up to date in Open VSX Registry at an identical cadence to VS Code Market, however they don’t seem to be completely aligned when extensions will not be straight revealed to the Open VSX Registry. So, you’ll encounter see some variations.
For instance, the most recent model of the ESLint extension is v2.2.3 within the VS Code Market, and it’s v2.2.2 in Open VSX Registry. This isn’t a deal-breaker for me, nevertheless it could possibly be for you!
My very own expertise is that I didn’t discover any extensions lacking, and I don’t want to make use of absolutely the newest of an extension. I have a tendency to make use of much less extensions than most. So, your mileage might differ.
Last ideas
I discovered it painless to change to VS Codium. You may attempt them out side-by-side and see if there may be something you miss, or if you happen to encounter any snags earlier than making the swap full-time. The profit is that you can be utilizing a extra privacy-oriented, absolutely open-source model of the editor. Give it a shot!
