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

Option to run spell check on entire files/folders #376

Closed
millergd opened this issue Aug 27, 2019 · 13 comments
Closed

Option to run spell check on entire files/folders #376

millergd opened this issue Aug 27, 2019 · 13 comments

Comments

@millergd
Copy link

There needs to be an option to run spell check on an entire file/folder either through the command line or through the interface. The same way linting can be run or spell check in MS Word. The npm package doesn't integrate with any of the VS Code plugin settings

@Jason3S
Copy link
Collaborator

Jason3S commented Aug 30, 2019

The VS Code spell checker is based upon cspell. If you install it, is should be possible to check all your files with a single command.

@millergd
Copy link
Author

The CMD line tool cspell can check entire directories, but it doesn't integrate with any of the VS Code settings in place. My suggestion is to either make the VS Code settings compatible with the CMD line tool cspell, or create an option in VS Code to check entire directories through the application.

I have the issue where I see misspelled words in VS Code, so I add them to the dictionary or ignore them which adds them to a list under the hood in VS Code. But cspell has its own list of custom/ignored words. So my solution is either to continuously sync settings between the two manually, or only use the cspell CMD line tool and remove the VS Code plugin.

@Jason3S
Copy link
Collaborator

Jason3S commented Sep 7, 2019

@millergd If you have a cspell.json file at the root of your project, both the cspell cmd line tool and the extension will use it. Are you seeing a different behavior?

@millergd
Copy link
Author

millergd commented Sep 9, 2019

If you have a cspell.json file at the root of your project, both the cspell cmd line tool and the extension will use it.

Awesome! It works just as you have described. If I right-click and add a word to the "folder" dictionary through the app, it creates a settings.json at my root even if I already have a cspell.json. Regardless, the fact that the cspell.json file is updated synchronously is sufficient. Thanks for clarifying this @Jason3S

@fsanzv
Copy link

fsanzv commented Jan 13, 2020

@Jason3S Please, can you tell me how to get this working with several dictionaries?. I have installed Spanish - Code Spell Checker and I wonder if is it possible to run cspell against whole project with same configuration as it runs on every file in VS Code. (I use English and Spanish in my project and VS Code works with both dictionaries but cspell only use English one)

@Jason3S
Copy link
Collaborator

Jason3S commented Jan 13, 2020

It is a bit annoying, but you need to install the Spanish Dictionary separately.
See: cspell-dict-es-es - npm

@fsanzv
Copy link

fsanzv commented Jan 14, 2020

Working!, thank you very much!!!

@echarrod
Copy link

echarrod commented Apr 8, 2020

Although you seem to have answered @millergd's problem which he mentioned in a subsequent comment, the original suggestion of being able to scan a whole directory from within the VS Code extension would be very valuable, and as far as I understand, still isn't possible.

Are there any plans to add this?

@nickchomey
Copy link

I'd also like to be able to spell check a folder

@Nosh-Ware
Copy link

So, is this on the list for implementation any time soon?

@xansh
Copy link

xansh commented Feb 27, 2023

Hi!
Any plans to add this soon?

@Jason3S
Copy link
Collaborator

Jason3S commented Feb 27, 2023

@xansh,

Because there is a command line alternative, there isn't any urgency to do this.

cspell <directory>:

npx cspell .

I'm going to close this issue as not planned, since the original request was answered.

Please open an new issue if the command line tool is insufficient.

@Jason3S Jason3S closed this as not planned Won't fix, can't repro, duplicate, stale Feb 27, 2023
@github-actions
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 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants