Open kkm000 opened 7 months ago
I'm running into this too. Same setup: VSCode remote ssh and trying to add a word to the workspace dictionary. To me it seems too that the extension is run locally and thus tries to access the linux path on the windows host. It determines the path in https://github.com/bartosz-antosik/vscode-spellright/blob/f843d5d369dc70a363fda5a9b38fcafcd5d0eacc/src/spellright.js#L1973 But I don't know why the path is not correct.
@dzerrenner Yeah possibly. There appears to be the remote fs API, but it's extremely poor.
I'm running VSCode on Windows 11 v10.0.22621.2715, but developing on a remote Linux machine over a devtunnel (Debian 12, x64). The README says:
Indeed, when I added an empty
spellright.dict
file under .vscode/, a new menu option appeared: in addition to "Add XXX to user dictionary", there is also "Add XXX to workspace dictionary". However, when I'm trying to add a word to workspace dictionary, I'm getting an error banner in the lower-right corner of VSCode frame, with the red circled ×: "A system error occurred (ENOENT: no such file or directory, open)".The Extension Host output logs the following stack trace, twice (I cleared the window before selecting the "add ... to workspace ..." menu item):
Unfortunately, there is no clue as to what exact file the extension is trying to open.
Adding words to the user dictionary (on the local Windows machine) works just fine.
What surprised me was that the extension is hosted in the local Extension Host. As expected, the "Extension Host (Remote)" output logged nothing. But I don't really understand how extensions work, and whether local extensions have access to remote files. Looks like they do, as adding the workspace empty dictionary resulted in adding a new menu item.
Am I doing anything wrong?
UPDATE:
I rigged the function `addWordToDictionary(word, filename) at line 1830 to log arguments. The filename argument ended up empty.
Output to dev tools console (the word I tried to add was "tf"):
Tangentially,
os.EOL
refers to which os? I think that '\n' works on any os. I long ago set all defaults (VSCode, Visual Studio 2022, Notepad++) on Windows to LF line ending, never saw any issues. But Linux gets very angry at "\r\n".