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 output in the "PROBLEMS" tab #414

Closed
zrno opened this issue Jan 16, 2020 · 9 comments · Fixed by #2798
Closed

Disable output in the "PROBLEMS" tab #414

zrno opened this issue Jan 16, 2020 · 9 comments · Fixed by #2798

Comments

@zrno
Copy link

zrno commented Jan 16, 2020

Is it possible to disable the cSpell output in the "PROBLEMS" tab in vscode? I only want compiler or static analysis messages in there and I want to see the spell checker issues only in the editor.

@zrno
Copy link
Author

zrno commented Jan 20, 2020

Setting "cSpell.maxNumberOfProblems": 0 didn't work as it completely disabled the spell checker suggestions.

@Jason3S
Copy link
Collaborator

Jason3S commented Jan 20, 2020

I know this is a bit of a lame answer, but Extensions do not have control of the Problems panel.

The extension just provides a list of Diagnostic objects to VS Code and it does the rest.

See: Filter "Problems" by the extension which generated them (Markers Panel Filter) · Issue #51103 · microsoft/vscode

@grumBit
Copy link

grumBit commented Jul 14, 2020

I know this is a bit of a lame answer, but Extensions do not have control of the Problems panel.

The extension just provides a list of Diagnostic objects to VS Code and it does the rest.

See: Filter "Problems" by the extension which generated them (Markers Panel Filter) · Issue #51103 · microsoft/vscode

What a shame! I really love cSpell as it helps my dyslexia hugely, but I absolutely must fix all linting issues before committing. So, I need to see the PROBLEMS number get to zero, but it's full of spelling items that I have to keep circling around. I hope VS Code will let Extensions have control of the Problems panel.

In the mean time I've had to disable cSpell. Whaaaaaa!!!

@Jason3S
Copy link
Collaborator

Jason3S commented Sep 29, 2020

@grumBit You can bind a keyboard shortcut to turn off the spell checker while fix the linter issues. When the spell checker is off, the issues will not show in the problems pane.

Just try: F1 -> Toggle Spell Checking

see: CHANGELOG.md - new commands

@grumBit
Copy link

grumBit commented Oct 8, 2020

Toggle Spell Checking

That's brilliant! Thank you so much @Jason3S!

@emmenlau
Copy link

Thanks a lot @Jason3S for your great work. I would still like to come back to this. The workaround with enable/disable spell checking is not bad, but I realize that I never reach the point to turn it back on after turning it off.

Would it work to add some token (like the suffix - cSpell) to the messages, to help with the filtering in the "Problems" pane? I'm admittedly a bit ignorant how well the "Problems" pane filters work...

@tlourey
Copy link

tlourey commented Dec 30, 2023

I think this might be fixed by the ability to set cSpell.diagnosticLevel to hint as per https://streetsidesoftware.com/vscode-spell-checker/docs/configuration/#cspelldiagnosticlevel

@Jason3S Jason3S linked a pull request Dec 30, 2023 that will close this issue
@Jason3S
Copy link
Collaborator

Jason3S commented Dec 30, 2023

This is fixed by #2887
It will go out with the 4.0 release.

Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants