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

Toggle problem visibility in Editor #166797

Closed
JohnSpeno opened this issue Nov 19, 2022 · 7 comments
Closed

Toggle problem visibility in Editor #166797

JohnSpeno opened this issue Nov 19, 2022 · 7 comments
Assignees
Labels
feature-request Request for new features or functionality languages-basic Basic language support issues languages-diagnostics Source problems reporting on-testplan

Comments

@JohnSpeno
Copy link

JohnSpeno commented Nov 19, 2022

Type: Feature Request

Say I've opened some random Python file in Code, and it is filled with linter issues producing many squiggly colored underlines all over.

Is there a way to hide those squiggly lines without disabling linters? I'm just looking for a way to quickly toggle them off and on. I'm not looking to edit this code, I just want to browse it and or maybe present it during a meeting. I'd still like to have syntax highlighting. Essentially, I want to use Code as a great code viewer sometimes.

It seems like these are the colors of the things I want to hide entirely:
editorError.foreground, editorWarning.foreground, editorInfo.foreground

I searched settings and commands and online but didn't find an answer yet. Zen mode wasn't even zen enough in this case. Putting the file in Plain Text mode removes them, but also eliminates colorizing the code, which I wish to retain.

https://stackoverflow.com/questions/74479139/how-do-i-hide-linter-problems-in-the-editor?noredirect=1#comment131477816_74479139

VS Code version: Code 1.73.1 (6261075, 2022-11-09T02:08:38.961Z)
OS version: Darwin x64 21.6.0
Modes:
Sandboxed: No

@gregkrsak
Copy link

Not trying to generate too much extra noise or notifications, but I'm a new VS Code use (formerly a religiously registering Sublime Text user), and this particular issue is extremely annoying. Please triage it appropriately; for example, in the referenced Stack Overflow post, an extension is mentioned that removes the squiggle lines if the file is dirty, and I feel this is a great native feature to have at the user's control. Thanks for listening.

@mjbvz mjbvz assigned sandy081 and unassigned mjbvz Nov 29, 2022
@sandy081 sandy081 assigned jrieken and unassigned sandy081 Nov 30, 2022
@jrieken jrieken added feature-request Request for new features or functionality languages-basic Basic language support issues labels Nov 30, 2022
@vscodenpa vscodenpa added this to the Backlog Candidates milestone Nov 30, 2022
@vscodenpa
Copy link

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodenpa
Copy link

🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodenpa vscodenpa modified the milestones: Backlog Candidates, Backlog Dec 15, 2022
@jrieken jrieken added the languages-diagnostics Source problems reporting label Feb 20, 2023
@justschen justschen self-assigned this Nov 3, 2023
@justschen justschen modified the milestones: Backlog, November 2023 Nov 9, 2023
@justschen justschen added on-testplan insiders-released Patch has been released in VS Code Insiders labels Nov 27, 2023
@jrieken jrieken modified the milestones: November 2023, December 2023 Nov 29, 2023
@justschen justschen removed the insiders-released Patch has been released in VS Code Insiders label Dec 18, 2023
@justschen
Copy link
Contributor

@JohnSpeno , this feature was recently added as a preview/experimental feature, which is subject to re-haul/change. Please check out problems.visibility to toggle visible problems in the editor, and check out the release notes for additional details on how the setting works at the moment. thanks :D

@starball5
Copy link

out of curiosity, why is the milestone for this feature set to the January release when it's already been released in 1.85?

@justschen
Copy link
Contributor

@starball5 there was an engineering issue we continued working on this iteration (#199246)

the feature is out as a preview as mentioned, closing as the main part of this issue is now complete.

@aiday-mar aiday-mar added this to the December / January 2024 milestone Feb 6, 2024
@microsoft microsoft locked and limited conversation to collaborators Jun 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality languages-basic Basic language support issues languages-diagnostics Source problems reporting on-testplan
Projects
None yet
Development

No branches or pull requests

9 participants