streetsidesoftware / vscode-spell-checker

A simple source code spell checker for code
https://streetsidesoftware.github.io/vscode-spell-checker/
Other
1.42k stars 126 forks source link

Generates settings.json in every workspace #3420

Closed a2937 closed 2 months ago

a2937 commented 3 months ago

I don't mind having a settings.json for what languages it is enabled, but I would like to have a say in it. Creating one should be handled by a command. If one isn't present, it should just read the global settings file.

Jason3S commented 3 months ago

@a2937,

Thank you for the report. It should only write to settings if you add words. In general is also gives the option to add the word to User or Workspace. Are you experiencing something different?

a2937 commented 3 months ago

I am actually. I am getting a list of enabled languages written every time a folder gets opened.

Steps to repeat.

Prerequisite: Install the Code Spell Checker language pack.

Step 1) Open a folder in the File explorer that doesn't have a settings.json. Step 2) Wait a few minutes. Step 3) Notice new settings.json with enabled language ids list.

settings.json

Jason3S commented 3 months ago

@a2937,

That is strange. I can see how it would be annoying.

On its own, the spell checker will not change the settings. That only happens if a command is run.

I guessing you are running version v3.0.1 of the extension.

Please make sure that there isn't a keyboard shortcut associated with any of the following commands:

image

These commands enable/disable file types (Language Ids). They are not for enabling natural languages.

The cSpell.language setting is used for enabling English, Spanish, etc.

If you are using those commands to enable / disable the spell checker, consider upgrading to v4. It has a very easy way to hide/show issues.

Jason3S commented 3 months ago

It might also be a sync issue caused by VS Code, since it is take a few minutes to happen.

github-actions[bot] commented 1 month ago

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.