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

Need to disable extensions not just uninstall them #2882

Closed
SteveALee opened this Issue Feb 10, 2016 · 11 comments

Comments

Projects
None yet
@SteveALee

SteveALee commented Feb 10, 2016

When looking for problems with intellisense (#2850) I wanted to clean up my config by disabling all extensions. However they can only be deleted.

This would be a generally useful option in case extensions are causing problems.

@joaomoreno

  • Figure out format to store extensions disablement in settings
  • Move extension scanning to Renderer (with @joaomoreno)
  • Ignore disabled extensions when scanning for them at runtime
  • Provide UI for enabling / disabling an extension for a workspace or globally
  • Telemetry
@Enet4

This comment has been minimized.

Show comment
Hide comment
@Enet4

Enet4 Feb 10, 2016

Contributor

As a workaround, extensions can be manually disabled by moving them away from your local extensions folder. (this is "~/.vscode/extensions" in Linux, I'm afraid I don't really know for other platforms)

But yes, I would also appreciate a more intuitive means of disabling extensions.

Contributor

Enet4 commented Feb 10, 2016

As a workaround, extensions can be manually disabled by moving them away from your local extensions folder. (this is "~/.vscode/extensions" in Linux, I'm afraid I don't really know for other platforms)

But yes, I would also appreciate a more intuitive means of disabling extensions.

@alexandrudima

This comment has been minimized.

Show comment
Hide comment
@alexandrudima
Member

alexandrudima commented Feb 10, 2016

@bgse

This comment has been minimized.

Show comment
Hide comment
@bgse

bgse Feb 10, 2016

Contributor

Would be really neat if we could define active extensions as multiple presets, workspace setting with individual extensions would suffice I guess but having a way to quickly switch between extension presets would be awesome (even if that means restarting vscode).

Contributor

bgse commented Feb 10, 2016

Would be really neat if we could define active extensions as multiple presets, workspace setting with individual extensions would suffice I guess but having a way to quickly switch between extension presets would be awesome (even if that means restarting vscode).

@savioret

This comment has been minimized.

Show comment
Hide comment
@savioret

savioret Apr 27, 2016

What about adding a ".disabled" (or .whatever) file inside the extension folder in order to set it as "not loadable". Neat and easy to implement.
for instance: ~/.vscode/extensions/myextension/.disabled

savioret commented Apr 27, 2016

What about adding a ".disabled" (or .whatever) file inside the extension folder in order to set it as "not loadable". Neat and easy to implement.
for instance: ~/.vscode/extensions/myextension/.disabled

@gregvanl

This comment has been minimized.

Show comment
Hide comment
@gregvanl

gregvanl Apr 27, 2016

Contributor

Doc Feedback verbatim request: "I need to disable an extension without uninstalling it."

Contributor

gregvanl commented Apr 27, 2016

Doc Feedback verbatim request: "I need to disable an extension without uninstalling it."

@SteveALee

This comment has been minimized.

Show comment
Hide comment
@SteveALee

SteveALee Apr 28, 2016

I recently noticed code has a "safe mode' to disable ALL plugins and invoked via a command line switch. You should doc that in same place too.

SteveALee commented Apr 28, 2016

I recently noticed code has a "safe mode' to disable ALL plugins and invoked via a command line switch. You should doc that in same place too.

@Novynn

This comment has been minimized.

Show comment
Hide comment
@Novynn

Novynn commented Aug 10, 2016

+1

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Aug 30, 2016

Member

@bpasero says:

The first thing I typically ask a user when an issue is reported is to run with all extensions disabled. However, if one extension is causing issues and 30 are installed, it is very hard to find the one causing the issue.

Ideally we have UI to disable an extension selectively (from the extensions viewlet) so that a user can easily find out which extension is causing issues.

Optionally we could also allow to do so from the command line, e.g. "code --disable-extension vscode-icons"

CC'ing some folks fyi @alexandrudima @joaomoreno @jrieken @egamma

Member

joaomoreno commented Aug 30, 2016

@bpasero says:

The first thing I typically ask a user when an issue is reported is to run with all extensions disabled. However, if one extension is causing issues and 30 are installed, it is very hard to find the one causing the issue.

Ideally we have UI to disable an extension selectively (from the extensions viewlet) so that a user can easily find out which extension is causing issues.

Optionally we could also allow to do so from the command line, e.g. "code --disable-extension vscode-icons"

CC'ing some folks fyi @alexandrudima @joaomoreno @jrieken @egamma

@joaomoreno joaomoreno changed the title from Need to disable extensions not just unistall them to Need to disable extensions not just uninstall them Aug 30, 2016

@joaomoreno joaomoreno modified the milestones: September 2016, Backlog Sep 13, 2016

@kieferrm kieferrm referenced this issue Sep 13, 2016

Closed

September Iteration Plan #11917

186 of 220 tasks complete
@scottpschaffer

This comment has been minimized.

Show comment
Hide comment
@scottpschaffer

scottpschaffer Sep 19, 2016

I just wanted to note that I am running version 1.5.2 and I have only the C# extension loaded. Just now, I went to the Extension and pressed Update. It went searching for the update (I assume) and then the Update button changed to an "Enable" button. Clicking the Enable button presents me a message that says I need to restart Code for the enabling to occur. I mention this only because it shows that there is already some functionality in the program to Disable the extension (at least that one).

scottpschaffer commented Sep 19, 2016

I just wanted to note that I am running version 1.5.2 and I have only the C# extension loaded. Just now, I went to the Extension and pressed Update. It went searching for the update (I assume) and then the Update button changed to an "Enable" button. Clicking the Enable button presents me a message that says I need to restart Code for the enabling to occur. I mention this only because it shows that there is already some functionality in the program to Disable the extension (at least that one).

sandy081 added a commit that referenced this issue Oct 17, 2016

sandy081 added a commit that referenced this issue Oct 17, 2016

sandy081 added a commit that referenced this issue Oct 24, 2016

@joaomoreno joaomoreno closed this Oct 24, 2016

sandy081 added a commit that referenced this issue Oct 24, 2016

@sandy081 sandy081 referenced this issue Oct 24, 2016

Closed

Test: Enable / Disable Extensions #14288

3 of 3 tasks complete

sverrirs added a commit to sverrirs/vscode that referenced this issue Oct 29, 2016

sverrirs added a commit to sverrirs/vscode that referenced this issue Oct 29, 2016

@JoeCodeswell

This comment has been minimized.

Show comment
Hide comment
@JoeCodeswell

JoeCodeswell Jun 5, 2017

+1 need to sometimes disable/enable pylint

JoeCodeswell commented Jun 5, 2017

+1 need to sometimes disable/enable pylint

@Enet4

This comment has been minimized.

Show comment
Hide comment
@Enet4

Enet4 Jun 5, 2017

Contributor

@JoeCodeswell This feature is already available. Enter Visual Studio code, open the extensions column, and click on the cogwheel next to the extension. As for disabling Pylint in particular, it might be more elegant to have a custom .pylintrc file in each of your projects. With { "python.linting.enabled": false }, linting is disabled entirely.

Contributor

Enet4 commented Jun 5, 2017

@JoeCodeswell This feature is already available. Enter Visual Studio code, open the extensions column, and click on the cogwheel next to the extension. As for disabling Pylint in particular, it might be more elegant to have a custom .pylintrc file in each of your projects. With { "python.linting.enabled": false }, linting is disabled entirely.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.