How do you disable warning and error popups in vscode?
The below popups have started showing up recently in vscode. Is there a way to turn these off? I couldn't find an option for it in settings.json
I already use the problems menu in vscode a lot which has a full list of warnings/errors, so I don't need an additional popup telling me what's wrong.
visual-studio-code vscode-settings
asked Jul 1 '17 at 17:01
tamj0rd2tamj0rd2
610916
add a comment |
The below popups have started showing up recently in vscode. Is there a way to turn these off? I couldn't find an option for it in settings.json
I already use the problems menu in vscode a lot which has a full list of warnings/errors, so I don't need an additional popup telling me what's wrong.
visual-studio-code vscode-settings
asked Jul 1 '17 at 17:01
tamj0rd2tamj0rd2
610916
add a comment |
The below popups have started showing up recently in vscode. Is there a way to turn these off? I couldn't find an option for it in settings.json
I already use the problems menu in vscode a lot which has a full list of warnings/errors, so I don't need an additional popup telling me what's wrong.
visual-studio-code vscode-settings
asked Jul 1 '17 at 17:01
tamj0rd2tamj0rd2
610916
The below popups have started showing up recently in vscode. Is there a way to turn these off? I couldn't find an option for it in settings.json
I already use the problems menu in vscode a lot which has a full list of warnings/errors, so I don't need an additional popup telling me what's wrong.
visual-studio-code vscode-settings
visual-studio-code vscode-settings
asked Jul 1 '17 at 17:01
tamj0rd2tamj0rd2
610916
asked Jul 1 '17 at 17:01
tamj0rd2tamj0rd2
610916
edited Jul 1 '17 at 17:28
tamj0rd2
asked Jul 1 '17 at 17:01
tamj0rd2tamj0rd2
610916
asked Jul 1 '17 at 17:01
tamj0rd2tamj0rd2
610916
asked Jul 1 '17 at 17:01
tamj0rd2tamj0rd2
610916
610916
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I posted the answer below back in July and then an overeager moderator deleted it today:
I believe this error is coming from an extension you have installed. Please try tracking down which extension is the root cause and opening an issue against them
This is the correct answer and the poster found that the prettier extension was causing this issue.
We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience. If you are seeing an error, file an issue against the extension that is causing it or VS Code itself if you believe the issue is not caused by an extension
answered Oct 20 '17 at 17:28
Matt BiernerMatt Bierner
13.1k13676
3
sometimes you just want to focus on the things at hand and to not deal with errors just this moment. Not being able to suppress those non-fatal errors are annoying to say the least. :)
– cyc115
Dec 3 '17 at 18:11
@cyc115 "We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience." And the popups don't?! I'm using the Vim extension. It has several minor bugs that produce these exception popups. Two salient factors:
– Mud
2 days ago
(1) These are issues in their backlog that they're aware of and will eventually be fixed. In some cases, they have been fixed and I'm just awaiting a new release. (2) These are non-fatal errors that I don't care about! They're for trivial things (e.g. trying to navigate past the end of a buffer) that can safely be ignored. I'm necessarily ignoring them, because the alternative is to disable the plugin.
– Mud
2 days ago
However, you've decided I must -- as a matter of principle -- constantly dismiss a graphical warning for the same error, over and over again. Why? As a means of forcing me to put pressure on an open source team to get through their backlog faster? How is that any of your business? Let me relegate these errors to a list somewhere, a log, rather than a freakin' GUI popup. That popup "impacts the VS Code experience" far more than the actual error.
– Mud
2 days ago
VS Code has no way of knowing that an extension is sending false positive errors. I've already said, file issues against the extensions that are incorrectly reporting the errors in the first place or disable them. Or submit a pr against the extension to fix the issue
– Matt Bierner
2 days ago
|
show 2 more comments
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44863450%2fhow-do-you-disable-warning-and-error-popups-in-vscode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I posted the answer below back in July and then an overeager moderator deleted it today:
I believe this error is coming from an extension you have installed. Please try tracking down which extension is the root cause and opening an issue against them
This is the correct answer and the poster found that the prettier extension was causing this issue.
We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience. If you are seeing an error, file an issue against the extension that is causing it or VS Code itself if you believe the issue is not caused by an extension
answered Oct 20 '17 at 17:28
Matt BiernerMatt Bierner
13.1k13676
3
sometimes you just want to focus on the things at hand and to not deal with errors just this moment. Not being able to suppress those non-fatal errors are annoying to say the least. :)
– cyc115
Dec 3 '17 at 18:11
@cyc115 "We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience." And the popups don't?! I'm using the Vim extension. It has several minor bugs that produce these exception popups. Two salient factors:
– Mud
2 days ago
(1) These are issues in their backlog that they're aware of and will eventually be fixed. In some cases, they have been fixed and I'm just awaiting a new release. (2) These are non-fatal errors that I don't care about! They're for trivial things (e.g. trying to navigate past the end of a buffer) that can safely be ignored. I'm necessarily ignoring them, because the alternative is to disable the plugin.
– Mud
2 days ago
However, you've decided I must -- as a matter of principle -- constantly dismiss a graphical warning for the same error, over and over again. Why? As a means of forcing me to put pressure on an open source team to get through their backlog faster? How is that any of your business? Let me relegate these errors to a list somewhere, a log, rather than a freakin' GUI popup. That popup "impacts the VS Code experience" far more than the actual error.
– Mud
2 days ago
VS Code has no way of knowing that an extension is sending false positive errors. I've already said, file issues against the extensions that are incorrectly reporting the errors in the first place or disable them. Or submit a pr against the extension to fix the issue
– Matt Bierner
2 days ago
|
show 2 more comments
I posted the answer below back in July and then an overeager moderator deleted it today:
I believe this error is coming from an extension you have installed. Please try tracking down which extension is the root cause and opening an issue against them
This is the correct answer and the poster found that the prettier extension was causing this issue.
We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience. If you are seeing an error, file an issue against the extension that is causing it or VS Code itself if you believe the issue is not caused by an extension
answered Oct 20 '17 at 17:28
Matt BiernerMatt Bierner
13.1k13676
3
sometimes you just want to focus on the things at hand and to not deal with errors just this moment. Not being able to suppress those non-fatal errors are annoying to say the least. :)
– cyc115
Dec 3 '17 at 18:11
@cyc115 "We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience." And the popups don't?! I'm using the Vim extension. It has several minor bugs that produce these exception popups. Two salient factors:
– Mud
2 days ago
(1) These are issues in their backlog that they're aware of and will eventually be fixed. In some cases, they have been fixed and I'm just awaiting a new release. (2) These are non-fatal errors that I don't care about! They're for trivial things (e.g. trying to navigate past the end of a buffer) that can safely be ignored. I'm necessarily ignoring them, because the alternative is to disable the plugin.
– Mud
2 days ago
However, you've decided I must -- as a matter of principle -- constantly dismiss a graphical warning for the same error, over and over again. Why? As a means of forcing me to put pressure on an open source team to get through their backlog faster? How is that any of your business? Let me relegate these errors to a list somewhere, a log, rather than a freakin' GUI popup. That popup "impacts the VS Code experience" far more than the actual error.
– Mud
2 days ago
VS Code has no way of knowing that an extension is sending false positive errors. I've already said, file issues against the extensions that are incorrectly reporting the errors in the first place or disable them. Or submit a pr against the extension to fix the issue
– Matt Bierner
2 days ago
|
show 2 more comments
I posted the answer below back in July and then an overeager moderator deleted it today:
I believe this error is coming from an extension you have installed. Please try tracking down which extension is the root cause and opening an issue against them
This is the correct answer and the poster found that the prettier extension was causing this issue.
We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience. If you are seeing an error, file an issue against the extension that is causing it or VS Code itself if you believe the issue is not caused by an extension
answered Oct 20 '17 at 17:28
Matt BiernerMatt Bierner
13.1k13676
I posted the answer below back in July and then an overeager moderator deleted it today:
I believe this error is coming from an extension you have installed. Please try tracking down which extension is the root cause and opening an issue against them
This is the correct answer and the poster found that the prettier extension was causing this issue.
We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience. If you are seeing an error, file an issue against the extension that is causing it or VS Code itself if you believe the issue is not caused by an extension
answered Oct 20 '17 at 17:28
Matt BiernerMatt Bierner
13.1k13676
answered Oct 20 '17 at 17:28
Matt BiernerMatt Bierner
13.1k13676
answered Oct 20 '17 at 17:28
Matt BiernerMatt Bierner
13.1k13676
answered Oct 20 '17 at 17:28
Matt BiernerMatt Bierner
13.1k13676
13.1k13676
3
sometimes you just want to focus on the things at hand and to not deal with errors just this moment. Not being able to suppress those non-fatal errors are annoying to say the least. :)
– cyc115
Dec 3 '17 at 18:11
@cyc115 "We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience." And the popups don't?! I'm using the Vim extension. It has several minor bugs that produce these exception popups. Two salient factors:
– Mud
2 days ago
(1) These are issues in their backlog that they're aware of and will eventually be fixed. In some cases, they have been fixed and I'm just awaiting a new release. (2) These are non-fatal errors that I don't care about! They're for trivial things (e.g. trying to navigate past the end of a buffer) that can safely be ignored. I'm necessarily ignoring them, because the alternative is to disable the plugin.
– Mud
2 days ago
However, you've decided I must -- as a matter of principle -- constantly dismiss a graphical warning for the same error, over and over again. Why? As a means of forcing me to put pressure on an open source team to get through their backlog faster? How is that any of your business? Let me relegate these errors to a list somewhere, a log, rather than a freakin' GUI popup. That popup "impacts the VS Code experience" far more than the actual error.
– Mud
2 days ago
VS Code has no way of knowing that an extension is sending false positive errors. I've already said, file issues against the extensions that are incorrectly reporting the errors in the first place or disable them. Or submit a pr against the extension to fix the issue
– Matt Bierner
2 days ago
|
show 2 more comments
3
sometimes you just want to focus on the things at hand and to not deal with errors just this moment. Not being able to suppress those non-fatal errors are annoying to say the least. :)
– cyc115
Dec 3 '17 at 18:11
@cyc115 "We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience." And the popups don't?! I'm using the Vim extension. It has several minor bugs that produce these exception popups. Two salient factors:
– Mud
2 days ago
(1) These are issues in their backlog that they're aware of and will eventually be fixed. In some cases, they have been fixed and I'm just awaiting a new release. (2) These are non-fatal errors that I don't care about! They're for trivial things (e.g. trying to navigate past the end of a buffer) that can safely be ignored. I'm necessarily ignoring them, because the alternative is to disable the plugin.
– Mud
2 days ago
However, you've decided I must -- as a matter of principle -- constantly dismiss a graphical warning for the same error, over and over again. Why? As a means of forcing me to put pressure on an open source team to get through their backlog faster? How is that any of your business? Let me relegate these errors to a list somewhere, a log, rather than a freakin' GUI popup. That popup "impacts the VS Code experience" far more than the actual error.
– Mud
2 days ago
VS Code has no way of knowing that an extension is sending false positive errors. I've already said, file issues against the extensions that are incorrectly reporting the errors in the first place or disable them. Or submit a pr against the extension to fix the issue
– Matt Bierner
2 days ago
3
3
sometimes you just want to focus on the things at hand and to not deal with errors just this moment. Not being able to suppress those non-fatal errors are annoying to say the least. :)
– cyc115
Dec 3 '17 at 18:11
sometimes you just want to focus on the things at hand and to not deal with errors just this moment. Not being able to suppress those non-fatal errors are annoying to say the least. :)
– cyc115
Dec 3 '17 at 18:11
@cyc115 "We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience." And the popups don't?! I'm using the Vim extension. It has several minor bugs that produce these exception popups. Two salient factors:
– Mud
2 days ago
@cyc115 "We do not provide a means to turn off or suppress these error messages because they are errors and will impact the VS Code experience." And the popups don't?! I'm using the Vim extension. It has several minor bugs that produce these exception popups. Two salient factors:
– Mud
2 days ago
(1) These are issues in their backlog that they're aware of and will eventually be fixed. In some cases, they have been fixed and I'm just awaiting a new release. (2) These are non-fatal errors that I don't care about! They're for trivial things (e.g. trying to navigate past the end of a buffer) that can safely be ignored. I'm necessarily ignoring them, because the alternative is to disable the plugin.
– Mud
2 days ago
(1) These are issues in their backlog that they're aware of and will eventually be fixed. In some cases, they have been fixed and I'm just awaiting a new release. (2) These are non-fatal errors that I don't care about! They're for trivial things (e.g. trying to navigate past the end of a buffer) that can safely be ignored. I'm necessarily ignoring them, because the alternative is to disable the plugin.
– Mud
2 days ago
However, you've decided I must -- as a matter of principle -- constantly dismiss a graphical warning for the same error, over and over again. Why? As a means of forcing me to put pressure on an open source team to get through their backlog faster? How is that any of your business? Let me relegate these errors to a list somewhere, a log, rather than a freakin' GUI popup. That popup "impacts the VS Code experience" far more than the actual error.
– Mud
2 days ago
However, you've decided I must -- as a matter of principle -- constantly dismiss a graphical warning for the same error, over and over again. Why? As a means of forcing me to put pressure on an open source team to get through their backlog faster? How is that any of your business? Let me relegate these errors to a list somewhere, a log, rather than a freakin' GUI popup. That popup "impacts the VS Code experience" far more than the actual error.
– Mud
2 days ago
VS Code has no way of knowing that an extension is sending false positive errors. I've already said, file issues against the extensions that are incorrectly reporting the errors in the first place or disable them. Or submit a pr against the extension to fix the issue
– Matt Bierner
2 days ago
VS Code has no way of knowing that an extension is sending false positive errors. I've already said, file issues against the extensions that are incorrectly reporting the errors in the first place or disable them. Or submit a pr against the extension to fix the issue
– Matt Bierner
2 days ago
|
show 2 more comments
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44863450%2fhow-do-you-disable-warning-and-error-popups-in-vscode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown