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

Provide a feature to permanently disable some extensions from some language/environment #110021

Closed
ghost opened this issue Nov 5, 2020 · 7 comments
Labels
*out-of-scope Posted issue is not in scope of VS Code

Comments

@ghost
Copy link

ghost commented Nov 5, 2020

A lot of Microsoft's python related extensions have very annoying and disrespectful spammy prompts.

For example, if a user has Python for VSCode and Intellicode installed, every time a python file is opened, the user will get a very annoying and spammy prompt to enable a "microsoft language server":

ic

As can be seen in the prompt, there is no way to permanently disable the prompt. The button "later" pretty much means "keep annoying me".

This prompt will happen even if the user has signaled it wants to use the open source "Jedi" language server, instead of the proprietary microsoft one.

This is an extremely annoying behavior.

VS Code should provide a way to blacklist and selectively disable certain extensions based on the file/language of the file being edited.

This way, the user could have a

    "[python]": {
        "disabledExtensions": [ "intellicode", "pylance"]
}

And the extensions would be disabled when editing python files, and no prompt will be shown.

@gjsjohnmurray
Copy link
Contributor

/duplicate of #41767 but you may want to contribute the language-specific aspect of your request there.

@ghost
Copy link
Author

ghost commented Nov 5, 2020

@gjsjohnmurray While being able to "ignore" some notifications would solve my problem, this issue is quite different from #41767. This issue asks to be able to selectively 'disable' an extension. That one asks about muting an extension.

@gjsjohnmurray
Copy link
Contributor

Sorry for misreading. May be a duplicate of #57548

@sandy081 please review and reopen if appropriate.

@sandy081
Copy link
Member

sandy081 commented Nov 8, 2020

@phgmacedo If I understand correctly your complain is about notifications noise from extensions. You can completely disable or uninstall an extension if you do not like it. If you want the extension to ignore certain files, you would have to open a feature request against that extension to support it. Because from the perspective of VS Code, it is not possible to disable an extension per file, you can do it either globally or per workspace.

@ghost
Copy link
Author

ghost commented Nov 8, 2020

@phgmacedo If I understand correctly your complain is about notifications noise from extensions. You can completely disable or uninstall an extension if you do not like it. If you want the extension to ignore certain files, you would have to open a feature request against that extension to support it. Because from the perspective of VS Code, it is not possible to disable an extension per file, you can do it either globally or per workspace.

I know it's not possible. That's why it's a feature request.

@sandy081
Copy link
Member

sandy081 commented Nov 9, 2020

Ok, but the feature (disabling extension per file) cannot be done as it does not fit into our current design. So, tagging this out of scope.

@sandy081 sandy081 added *out-of-scope Posted issue is not in scope of VS Code and removed *duplicate Issue identified as a duplicate of another issue(s) labels Nov 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

3 participants
@gjsjohnmurray @sandy081 and others