The code -list-extensions command exports the list of installed VS Code extensions which we then pipe into xargs, this transforms each extension's name into an extension install command. Our basic command for exporting the list of extensions is going to look like this: code - list-extensions | xargs -L 1 echo code -install-extension We'll be using the old trusty Linux terminal magic and VS Code's command line utility code. Setting up the backupįor this article, I'm going to suppose that you have VS Code already installed on your system and want to backup the settings and extensions you've spent some of your precious time setting up. What I'm going to show you this time around is a simple script that can help with the task of backing up your Visual Studio Code settings and extensions for use on your secondary PC, virtual environment or even your computer at work. This might be a case for your system configuration files (dotfiles) and your development tools alike. The script downloads the list of extensions listed in the file provided as the first argument into the directory, the path to which provided as the second argument.Having the same working environment across multiple machines is always a good thing. $ code -install-extension else echo "Something wrong!" fi done < $list_file The code snippets are also available in the GitHub repository. In this post, I will explain how to manage extensions, in particular, how to list all installed extensions, download them for offline use, and install them. With the lapse of time, your Extensions side bar tab will be populated with tens of different extensions, which are quite difficult to remember all. The opportunity to use one editor for so many different tasks is made possible by its great plugin subsystem and all those people, who have been spending hours and hours (thank you!!!) to develop wonderful extensions. Even this post I write in this editor due to its great support of markdown language. Currently, I use it for Python and Rust (I’ve just started) development, web development. Thanks to the amazing “LaTeX Workshop” plugin, I started using it as a LaTeX editor to write my research papers, and eventually I moved most of my everyday routines there. The last several years Microsoft’s Visual Studio Code (VSCode) is my favorite text editor.
0 kommentar(er)
