vscode-spellright icon indicating copy to clipboard operation
vscode-spellright copied to clipboard

spellright.* commands not found in VSCodium on macOS

Open Openstreetmapler opened this issue 1 year ago • 6 comments

I cannot use any of SpellRight’s commands since they all result in the error “Command 'SpellRight: *' resulted in an error – command 'spellright.*' not found”! There are similar issues, but they are quite outdated with the version numbers.

Extension version v3.0.140 from the Open VSIX marketplace

VSCodium setup Version: 1.88.1 Release: 24104 Commit: 0d01a72525276e5e3771fe5851b9c83de0de1e2b Date: 2024-04-13T01:43:30.924Z Electron: 28.2.8 ElectronBuildId: undefined Chromium: 120.0.6099.291 Node.js: 18.18.2 V8: 12.0.267.19-electron.0 OS: Darwin arm64 21.6.0

Operating system macOS Monterey, version 12.7.5

Openstreetmapler avatar Jan 22 '25 11:01 Openstreetmapler

This appears to not be macOS-specific; I'm running into this on regular bindist VSCode on Arch Linux

rubin55 avatar Mar 06 '25 15:03 rubin55

This also happens on windows. My spell right stopped working, and it also does not work on a fresh vscode install.

CyanBread avatar Jun 16 '25 13:06 CyanBread

Hello! There is a new version 3.0.144, which should resolve this issue!

bartosz-antosik avatar Jun 16 '25 13:06 bartosz-antosik

Thank you for updating the extension! Sadly for me this did not fix the problem. The extension does not seem to work in its current state, in my two vscode installations. I still get this error for all spell right commands

Image

CyanBread avatar Jun 16 '25 15:06 CyanBread

Hm. I may have read the issue too quickly!

bartosz-antosik avatar Jun 16 '25 15:06 bartosz-antosik

Hello,

I'm running into the same issue on Arch Linux with VsCodium. It appears to be the same issue as #614 and #559.

Using the Developer Tools, I can pinpoint the issue to the activation of the extension. I get the error : Activating extension 'ban.spellright' failed: Cannot read properties of null (reading 'Spellchecker'). Sadly, the error occurs in $onExtensionActivationError @ mainThreadExtensionsServices.ts:107, so I cannot say where it comes from in your code. Moreover, I don't know JavaScript, so helping to solve the issue is outside of my scope.

I hope it was useful to find a solution. I really like the extension.

Ultraxime avatar Oct 25 '25 15:10 Ultraxime