Not seeing squiggles / decorations on spelling errors in the editor (squiggles issue only) #3915
Comments
|
That is frustrating. The fact that it makes suggestions, implies that it is detecting the spell error, just not displaying it. I'm guessing it is one of the settings. Does it happen in all workspaces or only just one? If it happens in all, then it is most likely a User setting. If you can open the 
Any like this: |
|
I am on mac os (recently updated to v15 but the problem was there before). The problem happens in all workspaces. settings{
"[typescriptreact]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"gitlens.hovers.currentLine.over": "line",
"workbench.editor.enablePreviewFromCodeNavigation": true,
"workbench.editor.limit.value": 12,
"workbench.editor.revealIfOpen": true,
"workbench.editor.limit.perEditorGroup": true,
"[typescript]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"gitlens.hovers.enabled": false,
"git.openDiffOnClick": false,
"cSpell.userWords": [
"...",
],
"[javascript]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"javascript.inlayHints.functionLikeReturnTypes.enabled": true,
// "editor.codeActionsOnSave": {
// "source.organizeImports": true
// },
"[html]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"typescript.updateImportsOnFileMove.enabled": "always",
"[scss]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"yaml.schemas": {
"file:///.../atlassian.atlascode-3.0.15/resources/schemas/pipelines-schema.json": "bitbucket-pipelines.yml"
},
"atlascode.bitbucket.pipelines.monitorEnabled": false,
"[jsonc]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[json]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[astro]": {
"editor.defaultFormatter": "astro-build.astro-vscode"
},
"javascript.preferences.useAliasesForRenames": false,
"typescript.preferences.useAliasesForRenames": false,
"editor.inlineSuggest.enabled": true,
"editor.linkedEditing": true,
"javascript.preferences.importModuleSpecifier": "relative",
"typescript.preferences.importModuleSpecifier": "relative",
"explorer.autoRevealExclude": {
"**/node_modules": false,
"**/node_modulesss": true
},
"scm.autoReveal": false,
"[css]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[njk]": {
"editor.defaultFormatter": "douglaszaltron.nunjucks-vscode-extensionpack"
},
"diffEditor.ignoreTrimWhitespace": false,
"editor.formatOnSave": true,
"editor.codeActionsOnSave": {
"source.organizeImports": "never"
},
"supermaven.enable": {
"*": true
},
"supermaven.enableFixWithSupermaven": false,
"workbench.editor.limit.enabled": true,
"files.autoSave": "onFocusChange",
"emmet.includeLanguages": {
"javascript": "javascriptreact",
"typewscript": "javascriptreact"
},
"search.exclude": {
"**/.next": true,
"**/dist": true
},
"editor.pasteAs.preferences": ["text.updateImports"],
"typescript.experimental.expandableHover": true
} |
|
I tried your settings and things still work for me. Would you try adding the following to your settings: "cSpell.textDecorationThickness": "2px",
"cSpell.textDecorationColor": "#ff8f34",
"cSpell.useCustomDecorations": true,
"cSpell.textDecorationStyle": "wavy",It will make the issues really stand out with orange squiggles: 
|
|
I've tried that.. no joy :( I also looked at the logs (show logs -> extension host), but the only cSpell thing I see there is this warning: I think this is something pretty obscure :( . My editor must have gotten into a "weird" state after un upgrade or because of some other extension or smth, and it's causing this bug. I tried disabling most of my extensions as well, but does not help. I guess if there is no cached file to delete or something else to reload, I will just go with re-installing my vs-code route 😮💨. Or do you have any other ideas ? |
Restart VS CodeHave you restarted VSCode recently? It is acting like something is stuck running.
Manual Cleanup of ExtensionThe other option, is that the extension didn't correctly install. This can occasionally happen. But it requires you to delete the extension manually. |
|
Have the same issue after update of vscode to 1.96.0 and maybe a following update of cSpell to 4.0.21. Tried solutions of @Jason3S, didn't help, as well as with the gui way to uninstalling extensions. The same warning in extension host as @arturmarc encountered: I haven't tried removing all user config and cache for vscode for now. |
|
Did you try restarting quitting VS Code and see if there were any Code Helpers still running? I would like to find out the cause of the issue. |
|
@Jason3S thank you for your desire to help, I appreciate it! Yes, i removed the extension after having ensured all code processes died. Well, didn't help. Actually, I changed my mind and removed all user config/cache for vscode, namely After that cSpell (including settings for custom decorations) worked correctly. I had to tweak some non-synced settings of course. Nonetheless, I believe it's a reasonable tradeoff: just 7 minutes of messing with settings and I'm all ready to go. |
|
I wonder what the setting was that stopped it from working. |
|
@Jason3S I don't think it's in |
|
I am getting the same error. |
|
Here is my user settings.json
|
|
Thank you for sharing.
|
Yeah I can see the issues in the spellchecker.
0 problems listed
Other code problems are visible/underlined |
|
Please make sure the Note: The setting might be in the workspace or folder. |
|
Unfortunately that didn't solve the problem :/ @Jason3S I just set it to Information and restarted vscode, yet still no error highlights/underlining in the editor |
|
For me nothing worked so I followed @heinwol 's example, and did a full re-install. Including deleting Syncing the settings made it quick and relatively painless. |
|
A small note: I didn't reinstall vscode itself since it's, well, a nix package and therefore all the application files are read-only. So the problem is not in the actual vscode program |
|
Ok yeah that also worked for me. thx I just deleted (in linux) ~/.vscode and also ~/.config/Code then restored my settings from github |
|
I am also getting this issue. Issues show in the spell checker panel but not on the screen via underline. This started around a week ago on Windows 11. At this point, I tried all suggestions besides reinstalling VScode. I guess I'm going to try that now. |
|
Just to verify. You did not hide 
If you did, click the menu and Show Spelling Issues. There is also a command to toggle the visibility. @distbit0, @arturmarc, and @heinwol is it possible that this happened to you? Please try hiding and showing the spelling issues. |
|
The commands: 
|
|
@Jason3S hiding spelling issues as you describe causes the same issue I was having before, and unhiding them resolves it. I can not say for sure though whether this was the actual cause of my problem, as I didn't check the state of this setting when I was having the issue. I also do not recall ever intentionally hiding spelling issues, so not sure how this setting would have ended up in the state necessary to manifest the issue. |
|
I can confirm having an issue that manifested in ways consistent with what was described here, and toggling that setting fixing it. I don't understand how it would get set to that state, though, as I wasn't even aware that the setting existed, and certainly did not toggle it intentionally. if it could be of any relevance, I also have both vscode (well, vscodium) and the extension installed via nix, and an impermanence setup that wipes everything outside |
|
The ability to hide/show issues was added to help with a general complaint that "spelling issues were cluttering the screen" when the user was trying to do something different. The command are designed to easily toggle the visibility (in the editor and problems pane) of issues while still keeping track of them in the spelling pane. The spell checker uses There are several ways to hide issues. The easiest is to right click on an issue: The challenge here is how to make is clear that the issues have been hidden and how to show them again. |
|
My 2¢: removing deprecated configs fixed it. |
|
In reply to #3915 (comment) @Jason3S, toggling the switch option described brings the editor to the state resembling the one with the issue we encountered: cSpell reports several issues (in its appropriate tab at the bottom of the screen), but they're not squiggled in text. If I remember correctly, the issues were also not reported in the "problems" tab. Therefore it could be we just had the "toggle show spelling issues" switched somehow, though I'm sure I didn't do it manually |
|
In reply to #3915 (comment) I feel dumb, this fixed it for me... Thank you! I have no clue how or why it got hidden as this command is not in my history. |
|
I think there is a bug here. It has happened to me. I'm just not sure of the cause. |
At some point I stopped seeing the "squiggles" in the editor.
i.e. I don't see this:
instead I have all other functionality - suggesting fixes, the spell checker window etc..
but no squiggles in the editor:
I have tried enabling "custom decorators" as well - they don't show up either. I also tried:
I am pretty sure if I re-install my vscode from scratch, it will work since I tried a fresh "portable" install and it works just fine.
It seems like it's probably one those issues that happened during one of the vscode's or extension's upgrade, maybe some old settings is messing with it or some other extension 🤷♂️
I am trying to avoid the risk and disruption of the full re-install and wondering if there is something else I can try ?
The text was updated successfully, but these errors were encountered: