-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
OutputChannel - remove show function #36844
Comments
In general I see why @ShiftySituation is aksing for this however removing the show function is not the right way to tackle this. Two things that I think can be improved:
@isidorn assigning to you as the owner of the output channel. |
We are exploring adding the badges to the output channel. All the infrastrucutre is there for this. As for the extension we can not prevent them from doing this, though I understand your concern. |
No way we can remove that function from the API but "yes" we should have this overrule-able by the user. |
Let's wait and see if more people ask for it and I can add some configuration. |
@isidorn Yes, people ask for it. Please refer to angular/vscode-ng-language-service#128 for example. |
@jrieken Just out of curiosity, what is an example use-case that would clarify this api function as being beneficial? |
@lemoinem yeah that is a problem with the angular extension and should be fixed there and not using a workaround in vscode. You could probably provide a PR to that extension to just stop calling |
@isidorn , according to @chuckjaz from
|
@paustint thanks for more details, however what client library is he refering to? |
Seems like this is configurable in the client library, no action to do here on the vscode side (as far as I understand) -> closing |
Feature Request
Remove the show function from OutputChannel. Reason, coders need less distractions so allowing extensions to control what I see is a huge distraction. Plus it is annoying when typing commands in the terminal and all of a sudden the output window comes into view.
The text was updated successfully, but these errors were encountered: