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

"Disable all extensions and reload the window" in issue reporter #43156

Closed
roblourens opened this issue Feb 8, 2018 · 1 comment
Closed

"Disable all extensions and reload the window" in issue reporter #43156

roblourens opened this issue Feb 8, 2018 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug issue-reporter Issue reporter widget issues verified Verification succeeded
Milestone

Comments

@roblourens
Copy link
Member

The issue reporter has a link that says Try to reproduce the problem after disabling all extensions and reloading the window. which apparently runs the "Disable all installed extensions" action and reloads the window. That action causes any extension disable or workspace-disable state to be lost. I have several extensions disabled or disabled in different workspaces and it's annoying to lose that state.

Is it possible to simulate starting Code with --disable-extensions, which is transient and doesn't affect permanently disabled extensions?

Also, it would be nice if that link showed a confirmation popup, because it's possible to click on accident and reload your windows. I expected it to take me to some doc site when I clicked it.

@octref octref added the issue-reporter Issue reporter widget issues label Feb 8, 2018
bpasero added a commit that referenced this issue Feb 22, 2018
Add action to reload the window with disableExtensions set, #43156
@RMacfarlane
Copy link
Contributor

Changed so that disabling all extensions and reloading the window only temporarily effects extension state

@RMacfarlane RMacfarlane added this to the February 2018 milestone Feb 22, 2018
@RMacfarlane RMacfarlane added the bug Issue identified by VS Code Team member as probable bug label Feb 26, 2018
@bpasero bpasero added the verified Verification succeeded label Mar 1, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug issue-reporter Issue reporter widget issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants