egomobile / vscode-powertools

A swiss army knife with lots of tools, extensions and (scriptable) enhancements for Visual Studio Code.
https://marketplace.visualstudio.com/items?itemName=egomobile.vscode-powertools
GNU Lesser General Public License v3.0
68 stars 9 forks source link

Recommendation on best way to enable/disable what extensions are loaded for a specific workspace/window? #8

Open MostHated opened 2 years ago

MostHated commented 2 years ago

Hey there, For years now I have been looking for a way to swap between extension profiles (for lack of a better term, simply meaning controlling which extensions are currently active/loaded) based on configurable conditions, as I have tons of them for different languages and usually only need a handful of them active for a given workspace/window, and there are just too many for me to practically enable/disable manually on a day to day basis, sometimes hour by hour, so they all just get left enabled. I was excited when I came across this extension today, as it seemed like it might actually be able to help me to accomplish this.

My question is more of an ask for a recommended method, if you happen to be familiar, how best to try and tackle this? I see that powertools can trigger scripts upon loading of a workspace, but I think extensions would already be loaded by then, otherwise this extension would not be triggered to run the script in the first place. That said, is it possible for a script to flag what extensions I want to be loaded for a workspace and then auto-restart the actual VSCode window? I would imagine that interrupting it's own execution isn't ideal, but I am not sure if it would even be possible.

I am going to experiment with some things, but if you happen to have any ideas or suggestions, I would greatly appreciate it. :+1:

Edit: I am using vscode-insiders on linux, in case that ends up coming into play

Thanks, -MH