Make it possible to inactivate folders within a workspace

[mojoaxel]

I like the idea of workspaces where you can work on multible projects/libraries/folders within a given context. 💓

The idea:

Mark folders within a workspace "inactive" or "active". ☑️

Description

If a folder in a workspace was marked "inactive":

• It is closed/collapsed and can not be reopend untill marked "active" again.
• It is excluded from the global search
• Changes are not shown in the source-control panel

Why?

I often work on a project that consist of multible libraries. These libraries belong to the same "project" and I like them in one place/workspace. But it happens often that a search returns files from a sub-library that I'm not currently interested in (I know I can tweak the search but this again is work, I don't want to do every time). Also the source control gets easily cluttered with git infos I'm not interested in. And why vscode is still missing a task-focused-ui-plugin I would like a way to reduce (the always growing) amount of "noise" in the workspace. ⁉️

Work around / current state

At the moment I remove folders from the workspace and than add them again if I need to work on them again. This makes the whole concept of a workspace useless. 💔

[nickcoad]

You can already do this - in settings you have the option to provide globs for files/paths to exclude from the file manager, you can set this on a workspace or a user level.

[mojoaxel]

You can already do this - in settings you have the option to provide globs for files/paths to exclude from the file manager, you can set this on a workspace or a user level.

@nickcoad Thanks for your answer but I don't think you got my point. I know that I can remove/hide files from a workspace, there are in fact multible ways of doing this. I'm looking for a fast and easy way of excluding and including them again without removing/hiding them completely.

Here is an example how mylyn in eclipse does something similar:

[isidorn]

You basically working sets, thus duplicate of #9498

[mojoaxel]

@isidorn While #9498 might be similar i8t focuses only on open files in the editor. I propose to also exclude folders/project from search and source-control.

So this issue proposes a "working-set" for complete folders and not only opened files.

[isidorn]

Should be covered by this idea #87666

[mojoaxel]

Should be covered by this idea #87666

Yes! Thank you for pointing me to this!