81

I use the code spell checker for VS Code. I would like to disable the spell checker warnings/errors in the "PROBLEMS" panel (standard keyboard binding Ctrl+Shift+M) where "more serious" problems show up.

Often there are so many spell checker errors that I have to scroll down to the "real" problems :-)

enter image description here

informatik01
  • 16,038
  • 10
  • 74
  • 104
Jens Madsen
  • 1,154
  • 1
  • 10
  • 18

12 Answers12

132

See issues: don't show in Problems pane. It is suggested to try:

"cSpell.diagnosticLevel": "Hint",

in your settings.json. This will remove them from the problems pane. However, in your files these "hints" are now indicated by three small dots under the beginning of the misspell and are not all that apparent. You can modify them with the colorCustomization:

"workbench.colorCustomizations": {

  // will change the color of three dots to red
  "editorHint.foreground": "#ff0000",

  // will underline the entire word with dots in your chosen color
  "editorHint.border": "#00ff66"
}

This will give you both sets of hint dots, you can hide the built-in three dots by making them transparent:

"editorHint.foreground": "#f000",
tkazik
  • 919
  • 3
  • 12
  • 27
Mark
  • 143,421
  • 24
  • 428
  • 436
  • Dear mark. Thanks :-) We must wait until the issue is fixed or fix it ourself :-) – Jens Madsen May 14 '18 at 18:25
  • 2
    For me in 1.44.1 `editorHint.border` does not underline the whole word, it just makes 4 dots instead of 3. And they are slightly bigger dots. Probably visible enough for me: https://imgur.com/a/FZuvEjq – Philip May 15 '20 at 12:39
  • 2
    For anyone interested in a better solution to this, please check the VSCode issue and upvote it: https://github.com/streetsidesoftware/vscode-spell-checker/issues/186 – thomthom Jun 06 '20 at 18:35
  • Already very cool! But: 1. The `editorHint` option is not recognized anymore as a valid setting. 2. Not the full word is underlined, only the dots. – jaques-sam Nov 30 '21 at 08:50
  • @DrumM The `editorHint` `colorCustomizations` are still recognized. They must be put into the `workbench.colorCustomizations` object within your settings. – Mark Dec 08 '21 at 21:47
  • is it possible to make cspell aware of the names of the installed python packages? I keep having errors for packages names that aren't plain english – ClementWalter Oct 18 '22 at 14:43
17

Just Toggle Spell option in command pallete (View-Command Pallete) Disable Spell Checking

Rozy Mahsun
  • 205
  • 2
  • 7
13
  • Go to setting (Ctrl+,)
  • type cSpell.diagnosticLevel in a search box
  • change the option to Hint
RuchDi
  • 250
  • 3
  • 14
4

I've just unchecked C Spell: Enabled in Settings and all the Spelling related warnings has been disappeared.

Imge ScreenShot

steveSarsawa
  • 1,559
  • 2
  • 14
  • 31
2

HIDE:

Enable Dictionary Commands (use F1 or View -> Command Palette...):

Enable Spanish Spell Checker Dictionary Enable Spanish Spell Checker Dictionary in Workspace Disable Dictionary Commands (use F1 or View -> Command Palette...):

Disable Spanish Spell Checker Dictionary Disable Spanish Spell Checker Dictionary in Workspace

maraet
  • 259
  • 7
  • 22
1

I just disabled all possible words using regex.

  "cSpell.ignoreRegExpList": [
    ".*"
  ]
MJ Studio
  • 3,947
  • 1
  • 26
  • 37
  • 11
    Easier would be to just disable it. There's a setting to enable/disable: `"cSpell.enabled": false`. – neizan Jun 30 '20 at 20:06
1

You just need to go settings.json file.
Hit Ctrl+Shift+f and type cSpell.enabled. cSpell.enabled should be true, change it to false:

enter image description here

Dada
  • 6,313
  • 7
  • 24
  • 43
Tiago
  • 21
  • 2
1

It stopped working for me in .mdx files.

I explicitly enabled all file types by adding a * to the C Spell: Enable Filetypes in the Settings page in VS Code and it is working again!

enter image description here

Brendan Sluke
  • 857
  • 10
  • 11
1

write "!word" in the terminal > problem tab > search bar. it's a regular expression syntax. "!word" means all errors without an error name word. it will exclude all word-related errors.

Screenshot

shorif
  • 11
  • 3
0

Right click on word and click show spell check configuration info from menu .A spell checker tab will appear then click on file info and deselect spell checker enabled for file type(in my case it was typescript).

navaladi v.k
  • 111
  • 1
  • 2
  • 7
0

if your problem is this then follow the below step to solve

go to your setting vs shortcut ctrl+, inside setting panel search cspell

when you search csepll you get the option

unchecked this cspell and your problem is solved

nishar
  • 19
  • 3
0

First go to the setting at the bottom left side of VS code window,

Setting Page

Search for "spell" in the search bar,

Search Bar

Now toggle the Enable/Disable Spell Checker option and disable it.

Toggle the Enable option