Sandeep Somavarapu

This seems to be a doc bug - because I see the view id in our code is `workbench.scm`here - https://github.com/microsoft/vscode/blob/f126d786635872b21ff0890c9e7108fcf54e2ab3/src/vs/workbench/contrib/scm/common/scm.ts#L18

I see the confusion here - we have view containers (viewlets/panels) and views. There are following three contexts - `activeViewlet` - which expects viewlet/view container id - `activePanel` - which...

@ramya-rao-a Extensions recommendation file is meant to be shared (in team). Disabling and enabling extensions is user specific. Merging these two is not a good idea I guess.

We already support this feature in Extensions view. You can go to Installed Extensions view in Extensions viewlet and use `Disable (Workspace)` action under gear icon to configure extensions to...

@michaeljota Just want to understand what is the use case to have this in a file?

From @FancyBanana Currently it seems that information about which extension is enabled/disabled is stored globally. I propose that workspace enabled/disabled state should be stored in .vscode folder. This way the...

@FancyBanana I think your request is for synchronising workspaces?

@FancyBanana creating a file under `.vscode` folder will have side affects like @brutek mentioned.

@WORMSS you can disable all installed extensions temporarily. There is a command to do that. Also you can point to different users data directory and extensions directory if you want...

yeah, you can only locations on disk as extensions dir