Closed andyfangaf closed 10 months ago
Yes, additionally I hope there's an option or toggle that allows me to mute all notifications. New notifications increase the count in StatusBar but do not disturb the coding experience with the notification fly-out.
I guess @fandy originally meant the same thing, "Add option to ignore all notification messages", not only "disable all notification from an extension".
Now that would've been a wonderful solution to
I would also throw my hat into this ring, and ask you to consider preventing bad actors from abusing notifications for profit. Thus far, I've only seen this done in bmewburn/vscode-intelephense#615. But if more plugin authors begin to take this approach, I think you could see real harm done to the community.
I imagine that if VS Code's plugin ecosystem gains the reputation of being filled with spammy nagware that will fill your workspace with 30 ads every time you open your editor, the quality and trust of the ecosystem will evaporate.
On top of this. It shouldn't even be allowed to abuse vscode to spam ads.
Perhaps another way to approach this would be to show which extension originated the notification - perhaps even have a direct link from the notification to the extension's notification-related settings.
Bad actors can be blamed and uninstalled. Well-intentioned extensions that misunderstand their customers desires can avoid people rage-quitting.
Please address this issue. I am coming from widely used ESLint VSCode extension which throws a notification whenever you open ANY JS project. And the maintainer of the extension @dbaeumer said that he won't address this issue directly. It's very annoying.
The issue
It doesn't have to be a sophisticated notification management interface like on Windows or macOS. Already being able to "mute" extension popups/notifications with a simple entry in the settings.json would solve the problem.
Example for what this could look like:
I am also 2000% in favour of this feature. I love VS Code but if it keeps allowing this popular trend that everything follows nowadays (i.e. software devs thinking their users would like to be nagged incessantly about every little thing and spammed with marketing crap) then I will stop using it, as @skuester said above.
@nikitavoloboev It would be certainly better if I could answer you in https://github.com/microsoft/vscode-eslint/issues/727, but @dbaeumer censored that issue, preventing anyone from commenting with a solution to this problem.
I think the best workaround right now is to disable the extension globally and only enable it in a project that uses it.
That workaround still doesn't solve https://github.com/bmewburn/vscode-intelephense/issues/631, though.
On a more positive side note, I'm glad that some extension developers tackle the issue with more maturity and grace, see https://github.com/felangel/bloc/issues/1962.
+1
I'm using the C# extension, and as I'm building dotnet projects, I get dozens of popups from OmniSharp, which is very disruptive.
+1
I have to dismiss the toast popup on a failed unit test before I can scroll to the error in the output terminal. This happens every run.
It's been almost 4 years and still no way to disable pop-up notifications? In a code editor, where being able to focus is the paramount? Guys, are you serious?
Another reason: when debugging extensions in the "Extension Development Host" instance of vscode, those popups serve no purpose and it should be possible to disable them.
Why must the notifications pop-up? 99% of the time i dont care about it, can they not just show up as a little icon? The notifications right now are extremely annoying
I made a patch that disables all pop ups in the workbench CSS, because MS doesnt care, and the pop ups are p*ssing me off it's for archlinux, but the patch can probably be used anywhere its just a regex https://aur.archlinux.org/packages/code-hide-notifications/
holy, i have to disable an extension because of this.
is there an unsurmountable technical reason why this feature cannot be implemented? surely this is not that hard, correct?
it wont be because they dont care, but yeah it should be a "15 minute job"
+1 to this. The Elmtooling extension https://marketplace.visualstudio.com/items?itemName=Elmtooling.elm-ls-vscode shows a popup every time you save a file while it contains an error - which happens all the time and shouldn't warrant a notification.
+1. Can't believe there's no way to disable notifications per extension, some of them are terribly annoying.
+1 I need a way to disable notifications for specific extension
+1 GitHub Copilot is killing me with the Your Copilot experience is not fully configured
message on each space, new line, tab,...
This needs to be fixed already. It has been more than 4.5 years 😆
+1
@Asef00 I had to disable all notifications just to make it go away. Now I will miss important notifications just because I cannot selectively disable notifications for specific extensions.
UPDATE: This does not stop the notification. I have hidden notifications yet I am still getting the toast pop ups. This is really annoying
Looks like the only way to disable pop ups is to disable the extension itself :(
This needs to be fixed already. It has been more than 4.5 years 😆
+1
@Asef00 I had to disable all notifications just to make it go away. Now I will miss important notifications just because I cannot selectively disable notifications for specific extensions.
UPDATE: This does not stop the notification. I have hidden notifications yet I am still getting the toast pop ups. This is really annoying
Looks like the only way to disable pop ups is to disable the extension itself :(
Here’s what I mostly do as temporary solution.
Go to the extension source and look for notifications’ API, mostly “showErrorMessage” or “showWarningMessage” , comment out that code and it will stop showing notifications until the next update of the extension
Go to the extension source and look for notifications’ API, mostly “showErrorMessage” or “showWarningMessage” , annotate that code and it will stop showing notifications until the next update of that extension
Thanks for that. I edited out the 'showInformationMessage' for my offending extension (Random Theme Switcher). Since I use WSL remotes, I needed to change it from the WSL .vscode-server/extensions folder (extension was present in both host and remote directories).
Real showstopper for vscode. Tried switching from PHPStorm, but this is so annoying and as always: new features are more important than addressing issues that are open > 4 years. Reminds me of some other companies in that sector: Atlassian etc. Oh, this is Microsoft. Wonder why that is working at all...
Bump for this, it's been almost 5 years since the issue has been opened.
Every time eslint can't load a config this is soooo annoying. What's the holdup?
there's no holdup, they just don't care
Bump
This would be helpful for suppressing errors from extensions such as Tailwind CSS IntelliSense which throw errors when merge conflicts show up in config files that they parse such as package.json
. It would be even better if specific error notifications could be suppressed, but even just ignoring by extension would be a help.
What if we inform extension developers to add an option to disable notifications? For me I only have a single extension and I didn't add any notifications nor any menu contexts or statusbar items, I think abusing those places is extremely wrong and developers should know and respect that.
Bump for this 😎
Maybe we need a bounty for this.
I doubt a paid developer at a mega-corporation would willingly add a rogue feature for a bounty instead of working on something that's in the current sprint; they could be written up by their manager for their uncooperative behaviour, their work could be wasted if it's denied by management and they could be let go of their role if they insist on it.
If the feature isn't there after 4 years, a notable incident and 158 :+1:, then they're just not interested in adding it.
Again, we need a bounty for this.
Is there reason why this feature cannot be implemented?
Is there reason why this feature cannot be implemented?
+1 5 years now still can not be implemented?
Here's to another 5 🍻
Closing given that we added the Do Not Disturb mode via https://github.com/microsoft/vscode/pull/149645 in the June release.
Closing given that we added the Do Not Disturb mode via #149645 in the June release.
@daviddossett, I'm sorry, but wasn't the problem in ignoring a single extension's notifications and not all of them?
Can you please reopen?
Hahaha wtf. now someone needs to make a new issue to start the 5 year process again
Some extensions might provide important information that you may want to see as soon as it's given. A Do Not Disturb mode doesn't solve anything. Not only that, but the effort on Do Not Disturb is kinda misplaced since being able to mute a specific extension's spam would resolve Do Not Disturb's use case.
@daviddossett Seriously wtf, everybody's been waiting for something to happen 5 fucking years and now you just close the issue?
The Do Not Disturb
feature does not help when ESLint decides to start throwing errors. Where is the setting to actually suppress all notifications?
See also microsoft/vscode-eslint#1238
Apologies all, I was closing a few of these related issues at once and misunderstood that this is about suppressing a single extension's notifications.
FWIW we explored options for muting specific extensions in #144324. There was some discussion there on why we didn't (yet) provide the option to turn off notifications from a specific extension. At the time there was some concern that we don't know which extensions send notifications until they are sent. After some time has passed, I think it could be ok to show a list of full list of extensions even if some don't send any.
I would like to note that it would be great not only to be able to disable notifications from extensions but from vscode itself. I personally disable the menu-bar because I don't need it for the most part. If I need the menu-bar I toggle it, do my work with it and toggle it again to hide it. Each time I hide it vscode informs me that You can still access the menu bar by pressing the Alt-key
. First of all thats wrong because I set enableMenuBarMnemonics
to false
. Second I don't want to see this message every time.
+1
I'm using the C# extension, and as I'm building dotnet projects, I get dozens of popups from OmniSharp, which is very disruptive.
For those who might need to solve this specific case, omnisharp has this option: "omnisharp.disableMSBuildDiagnosticWarning": true
which disables this specific annoying warning message. Just put it into settings.json.
It's quite hard to comprehend the reasons why this feature has not been implemented yet. I'm sure there must be some reasons but they have not been conveyed properly.
In the meantime one the way I dealt with this is by changing a couple of line in the css. Unfortunately, the notifications messages are so annoying that they go against dev productivity.
For anyone interested, I added the following lines to the workbench css (on Mac it's /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.css
)
.notifications-toasts {
display: None !important;
}
I hope this feature lands soon so we don't have to manually change the source code to make it work.
Sometimes a plugin is broken but you don't want to spend the time to dig into it. It would be great if we could disable notifications from popping up with a user preference setting.