bartosz-antosik / vscode-spellright

Multilingual, Offline and Lightweight Spellchecker for Visual Studio Code
Other
359 stars 36 forks source link

All commands fail #371

Open klingtnet opened 4 years ago

klingtnet commented 4 years ago

All of the commands fail with a message similar to:

Command 'SpellRight: Select Dictionary (Language)' resulted in an error (Running the contributed command: 'spellright.selectDictionary' failed.)

I am using this extension version

Name: Spell Right
Id: ban.spellright
Description: Multilingual, Offline and Lightweight Spellchecker
Version: 3.0.50
Publisher: Bartosz Antosik
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ban.spellright

with the OSS build of VS code

Version: 1.46.0
Commit: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Date: 2020-06-11T14:57:41.218Z
Electron: 7.1.14
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.7.2-arch1-1

The extension configuration folder looks fine to me:

$ ls -al ~/.config/Code\ -\ OSS/Dictionaries/
total 860
drwxr-xr-x   2 root root   4096 Jun 18 20:01 .
drwxr-xr-x 190 root root   4096 Jun 18 20:01 ..
lrwxrwxrwx   1 root root     15 Feb 23 10:06 en_US.aff -> en_US-large.aff
lrwxrwxrwx   1 root root     15 Feb 23 10:06 en_US.dic -> en_US-large.dic
-rw-r--r--   1 root root   3090 Feb 23 10:06 en_US-large.aff
-rw-r--r--   1 root root 866133 Feb 23 10:06 en_US-large.dic

Update Error messages from the developer console of VS code did not contain any additional information.

bartosz-antosik commented 4 years ago

This is very strange. I have reviewed issues related to OSS and it seemed to be working ok recently. There is no any additional information in Output/Debug console etc?

klingtnet commented 4 years ago

Thank you for the quick reply! Unfortunately, all I can provide is this: Screenshot from 2020-06-18 20-49-13

bartosz-antosik commented 4 years ago

I suspect (and looking through the issues searching for OSS reminds me this) things are located different in OSS. This caused problems of which some have been cured in the past. I do not have OSS around ant thus I am not sure what to do.

P.S. You ahve checked that dic/aff files are UTF-8 (it is describer in the README If I remember correctly)?

klingtnet commented 4 years ago

Yes, they're:

$ file ~/.config/Code\ -\ OSS/Dictionaries/en_US-large.*
/home/alinz/.config/Code - OSS/Dictionaries/en_US-large.aff: UTF-8 Unicode text
/home/alinz/.config/Code - OSS/Dictionaries/en_US-large.dic: UTF-8 Unicode text

I will check what happens if I create a symlink from ~/.config/Code\ -\ OSS to ~/.config/Code. Update Then I can select a language, so the path, or likely the spaces in it, are the causing the issue.

Shatur commented 4 years ago

I have the same issue.

Shatur commented 4 years ago

Update Then I can select a language, so the path, or likely the spaces in it, are the causing the issue.

Worked for me. I use Arch Linux too and default code package provides OSS version that use Code - OSS folder.

bwegge commented 4 years ago

I am facing the same issue with VS Code 1.48.* on Windows 10 (64 bit), connected inside my Windows Subsystem for Linux WSL running Ubuntu 20.04. As described, any spellright.X command results in a popup with command 'spellright.X' not found, e.g.

Command 'SpellRight: Select Dictionary (Language)' resulted in an error (command 'spellright.selectDictionary' not found)

I followed the readme and created symlinks to hunspell dictionaries inside WSL to /.config/Code/Dictionaries (and made sure at least hunspell-en-us and -gb are installed). Setting global.SPELLRIGHT_DEBUG_OUTPUT to true appears to makes no difference. Spell Right version is 3.0.52.

Below are the details from VS Code's about dialog. Electron version is 7.3.2, but in the extension's lib/bin folder inside WSL, I only see spellchecker-{deb,rpm}-{7.1.7,9.1.0}-{ia32,x64}.node binaries, but nothing explicitly for 7.3.2 (in case this matters).

Version: 1.48.0 (user setup)
Commit: db40434f562994116e5b21c24015a2e40b2504e6
Date: 2020-08-13T07:50:42.600Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

The extension works fine when working 'natively' in Windows (i.e. when not connected into WSL).

bwegge commented 3 years ago

Problem persists with the recently released v3.0.56 in VS Code 1.52.1 on Windows 10 20H2 for connections into WSL2.

MaHaWo commented 3 years ago

have the same issue on macOS. clean reinstallation of vs-code did not help

natema commented 3 years ago

Same problem on Ubuntu 20.04.2 LTS.

chrisbartoloburlo commented 3 years ago

Same issue here on macOS.

kecinzer commented 2 years ago

Same issue here on macOS.