-
-
Notifications
You must be signed in to change notification settings - Fork 132
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
Not seeing squiggles / decorations on spelling errors in the editor (squiggles issue only) #3915
Comments
I am on mac os (recently updated to v15 but the problem was there before). The problem happens in all workspaces. {
"[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'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 ? |
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 |
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: