“You must have…” that’s the main title in a lot of post and videos starts when talks about Visual Studio Code extensions to get more attention, but this editor is like a chameleon that can morph his environment all that it wants, that’s why you need to create your own recipe.
These things are very opinionated. I’m going to share “my configuration" for general-purpose and I hope someone can pick something useful on the whole of this.
Recommend read first about settings on visual studio code to understand the difference between user and workspace settings.
Multiple Devices
Before starting, highly recommend install and setup Settings Sync extension. It adds the ability to back up your settings and extensions in the cloud using a private gist to store those files.
It syncs all extensions and complete User Folder that Contains:
Settings File
Keybinding File
Launch File
Snippets Folder
VSCode Extensions & Extensions Configurations
Workspaces Folder
So you can sync your devices and don't waste your time when making a factory reset or buy a new device.
I’m only missing one thing on this marvelous Editor, the ability to change from one environment to another and don’t have loaded all the tools even when they don't need them.
Actually, you can disable it manually on each project, but it will be good in the future to have the ability to switch between environments and shut down the extensions that are not needed.
While VSCode Team solves that, we can use a workaround creating flavored versions: React, Node.js, .Net y Arduino.
One Ring To rule them all!
You can make that your team works with the same settings just save it as settings.json file and extensions as extensions.json file, both inside .vscode folder.
Then when someone clone/pull the repository will overwrite your Code user settings with workspace settings and show extensions as recommended.
After a year of discovering this tutorial, I should say this has become a vital part of my programming workflow (I made profiles for Rust, Java, C++, etc.).
I ended up making a script for Windows to improve their usability. This script adds the profiles in the context menu when you open folders/files. Check it out: github.com/rtxa/vscode-profiles-sc...
By the way, VSCode team is finally working on adding profiles support and is coming for next release :)
I found good things about it, for example, can be used with WSL 🥳, but one thing I did not like is that the recent project is not independent.
When the VSCode team officially releases the new option I'll try to update this series sharing the complete configuration of those profiles in a repository. And of course, using your py script but with --profile flag instead.
Thanks, great that you liked! Yeah, for now until the Settings Profile isn't really finished and given the last polishes, I'll just keep using the profiles script which I think is a simple solution and works well.
Thanks for the series. I suggest adding the profile name in the title bar on settings.json to recognize more easily the profile: "window.title": "${dirty}${activeEditorShort}${separator}${rootName}${separator}${appName}${separator}Profile: Java"
Changing colors can be distracting in some cases, at least for me.
I didn't know about it and can be customized in a lot of ways. I'll take a look.
// Controls the window title based on the active editor. Variables are substituted based on the context:// - `${activeEditorShort}`: the file name (e.g. myFile.txt).// - `${activeEditorMedium}`: the path of the file relative to the workspace folder (e.g. myFolder/myFileFolder/myFile.txt).// - `${activeEditorLong}`: the full path of the file (e.g. /Users/Development/myFolder/myFileFolder/myFile.txt).// - `${activeFolderShort}`: the name of the folder the file is contained in (e.g. myFileFolder).// - `${activeFolderMedium}`: the path of the folder the file is contained in, relative to the workspace folder (e.g. myFolder/myFileFolder).// - `${activeFolderLong}`: the full path of the folder the file is contained in (e.g. /Users/Development/myFolder/myFileFolder).// - `${folderName}`: name of the workspace folder the file is contained in (e.g. myFolder).// - `${folderPath}`: file path of the workspace folder the file is contained in (e.g. /Users/Development/myFolder).// - `${rootName}`: name of the opened workspace or folder (e.g. myFolder or myWorkspace).// - `${rootPath}`: file path of the opened workspace or folder (e.g. /Users/Development/myWorkspace).// - `${appName}`: e.g. VS Code.// - `${remoteName}`: e.g. SSH// - `${dirty}`: a dirty indicator if the active editor is dirty.// - `${separator}`: a conditional separator (" - ") that only shows when surrounded by variables with values or static text."window.title":"${dirty}${activeEditorShort}${separator}${rootName}${separator}${appName}",// Adjust the appearance of the window title bar. On Linux and Windows, this setting also affects the application and context menu appearances. Changes require a full restart to apply."window.titleBarStyle":"custom",// Separator used by `window.title`."window.titleSeparator":" - ",
Top comments (6)
Official native profiles VSCode is out:
code.visualstudio.com/docs/editor/...
After a year of discovering this tutorial, I should say this has become a vital part of my programming workflow (I made profiles for Rust, Java, C++, etc.).
I ended up making a script for Windows to improve their usability. This script adds the profiles in the context menu when you open folders/files. Check it out: github.com/rtxa/vscode-profiles-sc...
By the way, VSCode team is finally working on adding profiles support and is coming for next release :)
Wow, that scrip for context menu profiles is awesome. Terrific job 👏👏👏
Native multi-profiles support is a feature that I'll be waiting for for years. I've been testing this functionality with:
I found good things about it, for example, can be used with WSL 🥳, but one thing I did not like is that the recent project is not independent.
When the VSCode team officially releases the new option I'll try to update this series sharing the complete configuration of those profiles in a repository. And of course, using your
py
script but with--profile
flag instead.Thanks, great that you liked! Yeah, for now until the Settings Profile isn't really finished and given the last polishes, I'll just keep using the profiles script which I think is a simple solution and works well.
Regards!, rtxa.
Thanks for the series. I suggest adding the profile name in the title bar on settings.json to recognize more easily the profile: "window.title": "${dirty}${activeEditorShort}${separator}${rootName}${separator}${appName}${separator}Profile: Java"
Changing colors can be distracting in some cases, at least for me.
You are welcome.
I didn't know about it and can be customized in a lot of ways. I'll take a look.
code.visualstudio.com/docs/getstar...