-
Notifications
You must be signed in to change notification settings - Fork 37
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
Extension doesn't work #6
Comments
Could you tell me what is displayed in the language switch (a quick list at editor's toolbar) when you click language name in the status bar? Is the language selector in the status bar displayed at all? |
I did some tests and it seems that on freshly installed W7+VSCode+SpellRight (as the only extension) it does not show symptoms you describe ("command not found"). It does not spell and show empty dictionary list but this is another matter - on Windows 8+ extension uses Windows Spell Checking API whereas on W7 it uses hunspell speller which does not have any dictionaries installed. So I need some more clues to do something about it. |
me too |
Same thing here
|
@farfromrefug Could you please tell me what OS is this? Paths do not look like Windows 64-bit. |
@insanetesterftw i am on macOs. I now see in the readme that it just won't work ... |
On Ubuntu this extension doesn't work :( |
Yes, it does not work on UBuntu neither it does on macOS. It is clearly written in first lines of README that at the moment it works only on 64 bit Windows. The reason for this is explained with a lot of details here. TL;DR; VSCode team should build include one module in the builds for all platforms. |
Using Windows 7 64bit, Visual Studio Code latest stable version.
Extension is installed.
Tested on a text file (plain). Doesn't highlight any of the mistakes that exist.
Executing any of the "SpellRight" commands returns "command not found"
Other installed extensions: asciidoc; beautify; html preview; markdownlint; rewrap; write good linter.
I'm frustrated that I can't provide better feedback because I can't find any reason from my part for the failure of the extension to work.
Thank you.
The text was updated successfully, but these errors were encountered: