Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to enable/disable extensions inside .vscode #42497

Closed
Zerogiven opened this issue Jan 30, 2018 · 11 comments
Closed

Ability to enable/disable extensions inside .vscode #42497

Zerogiven opened this issue Jan 30, 2018 · 11 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster

Comments

@Zerogiven
Copy link

You alreade made a great job with #15611 and #2882 but i still have a small problem with it cause if i make many projects and/or starting/creating often new tiny projects i always have to make the following steps:

  1. Start a new Project, for Example a PHP Project
  2. Load it by VS code
  3. Go to extensions and disable/enable all necessary extensions

If i start a new PHP Project i have to do step3 all the time. But at a plain PHP project i don't need the typescript & node extensions for example. Same for TypeScript project, where i never need the PHP debuger. And here we only have PHP, NodeJS and TypeScript. It's getting harder and harder if you develop many different languages... many would say, use another IDE, for example for Perl or PHP. But i really like VS code for most of my use cases.

One idea could be to make a user config like "plugins.active" with could be a string array which could have a default value like a joker sign. For Example: plugins.enable: ['*'];

This would activate all plugins by default. Then i could say inside a workspace config which plugins should be active at this project. Also the other way with plugins.disable would be nice so that we can fill in all plugins which are not needed for a project.

Second factor could or should be what i've set inside extension view, so it should merge with .vscode setting.


So i hope you understand my problem and maybe you guys have a solution for me :)

@vscodebot vscodebot bot added the php PHP support issues label Jan 30, 2018
@roblourens
Copy link
Member

Ideally you shouldn't have to enable/disable extensions per workspace. If they are causing some problem with workspaces where you don't need them, then you should file a bug on that extension.

What's the problem with leaving them enabled all the time?

@roblourens roblourens removed the php PHP support issues label Jan 30, 2018
@roblourens roblourens removed their assignment Jan 30, 2018
@roblourens roblourens added the info-needed Issue requires more information from poster label Jan 30, 2018
@Zerogiven
Copy link
Author

Some of the extensions are still RAM or CPU expensive like some intellisense extensions. So if i use PHP, Path, NPM, SCSS, C/C++ and less Intelisense extension (cause this are the ones i need), i mostly need just a bunch of them and the others are scanning directories too, of course cause i still can have a mixed project like PHP & SCSS or PHP, SCSS and NPM. But sometimes i only need PHP stuff and nothing more, so the others still need some workload which is pretty normal i think, it's more the sum of all.

I attach two screenshots with my workload in a tiny PHP project (About 25 files, 7 directories), first with all extensions enabled, second only with my PHP extensions. Both have the same open files from the same project, just which extensions are enabled differs. The used RAM is almost twice.

Of course, this is maybe not a real problem, more something stickin in my eye ;-) but maybe others have that too.. I'm also not sure to install more extensions like i already have cause maybe sometimes it uses three(or four ^^) times more RAM than with needed extensions enabled only.

bildschirmfoto vom 2018-01-31 22-15-48

bildschirmfoto vom 2018-01-31 22-16-13

greetings

@roblourens
Copy link
Member

Those numbers are hard to interpret without more context about what the processes actually are and what else is going on. Only one of those per window is the extensionhost process.

Ideally extensions should only be activated when you are editing files that they care about. If there is a heavy extension which is activated all the time, we should file an issue on it. You can see which extensions are activated by running the "Show Running Extensions" command.

@Zerogiven
Copy link
Author

Okay i'll try to debug this out.

I understand the fact that the extensions should care about working progresses, but if i could handle with extensions are enabled/disabled per Workspace Setting (like i already can do, but only with Local Storage and not by config file) i don't have to care if all of my extensions are handling my pc ressources perfectly. Otherwise it always could be that i can't or won't use an extension cause it's working perfect for what it is made for, but lags for all unnecessary stuff.

thx at all :)

@Zerogiven
Copy link
Author

Oh and there is one more reason why this could be helpful. I have the Apache Conf extensions installed, but mostly i work on other config files, only at a few docker projects it's helpful to get apche conf snippets. But often i have apache like config files where i dont need the snippets plugin, but maybe another one. So i have a plenty of snippets which are unimportant. Another example is that i sometimes use Jest for testing and sometimes i have test tools like mocha. But if i leave all extensions enabled i have in both situations both snippets which is not so important if you just have a few one but if there are for example 20-30 snippets per extension it's getting hard to get a good overview for the things i really need.

@roblourens
Copy link
Member

Actually we do have something which could help you, extensions can now be enabled/disabled per workspace. Click the gear icon on an extension.

image

@Zerogiven
Copy link
Author

Sure this helps me a lot at the moment, it's just annoying me that i have to do this all the time if i start a new project. With about 30 installed extensions this is not so funny ;) Especially cause most of the times i enable / disable same extensions for different projects. For example if i start a PHP Project, in 99% of my cases i don't need my typescript extensions.

To handle the RAM & CPU ressource problem i already do it like in your screenshot. It would be just helpfull if i could do it more automatically :D

@sandy081
Copy link
Member

sandy081 commented Feb 2, 2018

I wonder if you are looking for something like this feature - #40109

@Zerogiven
Copy link
Author

Exactly :)

@sandy081
Copy link
Member

sandy081 commented Feb 2, 2018

Duplicate of #40109

@sandy081 sandy081 marked this as a duplicate of #40109 Feb 2, 2018
@sandy081 sandy081 added the *duplicate Issue identified as a duplicate of another issue(s) label Feb 2, 2018
@vscodebot
Copy link

vscodebot bot commented Feb 2, 2018

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Feb 2, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants