Windows Support

[RoboZoom]

I attempted to enable NextLS via the VSCode Extension, however the client was not created.

The first question is, in a general sense, is NextLS viable in windows?

If NextLS supports windows, but the initialization script is unsupported in windows, then there is an issue packaging and initializing it for windows users of VSCode.

[simonmcconnell]

Trying to use NextLS in WSL:

[Error - 9:56:36 PM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 9:56:36 PM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
	at _.shutdown (/home/cmo/.vscode-server/extensions/elixir-tools.elixir-tools-0.3.0/dist/extension.js:2:96701)
	at _.stop (/home/cmo/.vscode-server/extensions/elixir-tools.elixir-tools-0.3.0/dist/extension.js:2:96282)
	at _.stop (/home/cmo/.vscode-server/extensions/elixir-tools.elixir-tools-0.3.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/cmo/.vscode-server/extensions/elixir-tools.elixir-tools-0.3.0/dist/extension.js:2:102789)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)

Trying to use NextLS on Windows:

[Error - 9:58:50 PM] NextLS client: couldn't create connection to server.
Launching server using command c:\Users\simon\scoop\apps\vscode\1.80.1\data\extensions\elixir-tools.elixir-tools-0.3.0\bin\nextls failed. Error: spawn c:\Users\simon\scoop\apps\vscode\1.80.1\data\extensions\elixir-tools.elixir-tools-0.3.0\bin\nextls ENOENT

[apoorv-2204]

windows is very weird, when dealing with dev tools.

[mhanberg]

I now have windows binaries uploaded to the releases, but I still use a bash script so I'll need to convert that to a bat script or might not need it at all.

Should be good to test on windows after that

[cvkmohan]

#144 - now that binaries are getting downloaded - will it work in WSL?

[mhanberg]

@cvkmohan i believe so. @zachallaun has gotten it working in WSL2 i believe, but he needed to update to a more recent Ubuntu version. he tried on 20.XX and the version of glibc was too old.

[cvkmohan]

I can confirm that on WSL2, with Ubuntu 22.04, it is working. It downloaded the executable.
Thanks a lot. BTW, I am a big fan of your Temple library.

One question: what is the correct place for the code completion of definitions? I mean - when you type defmodule or def end automatically appearing. In this extension or code snippets?

[mhanberg]

Completions are not implemented yet, but are coming up soon on the roadmap.

BTW, I am a big fan of your Temple library.

That's awesome to hear! The https://www.elixir-tools.dev is built with Temple.

marking this comment as off topic tho, to keep the issue focused. You can open a github discussion on the Org for general questions or join the discord invite link

[spapas]

Hey friends, tried installing it on windows and getting:

2023-11-01 12:45:45.869 [error] Error: Download failed (https://github.com/elixir-tools/next-ls/releases/latest/download/next_ls_windows_amd64, status=404)
    at c:\Users\serafeim\.vscode\extensions\elixir-tools.elixir-tools-0.11.0\dist\extension.js:2:432487
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at l.force (c:\Users\serafeim\.vscode\extensions\elixir-tools.elixir-tools-0.11.0\dist\extension.js:2:432228)
    at c:\Users\serafeim\.vscode\extensions\elixir-tools.elixir-tools-0.11.0\dist\extension.js:2:431445
    at e.activate (c:\Users\serafeim\.vscode\extensions\elixir-tools.elixir-tools-0.11.0\dist\extension.js:2:430807)
    at v.n (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:125:6205)
    at v.m (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:125:6168)
    at v.l (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:125:5625)
2023-11-01 12:49:48.601 [info] ExtensionService#_doActivateExtension vscode.simple-browser, startup: false, activationEvent: 'onOpenExternalUri:https'

Plase notice that the correct filename is next_ls_windows_amd64.exe !

[chgeuer]

Yes, like @spapas mentioned

2024-01-19 09:20:06.744 [info] ExtensionService#_doActivateExtension elixir-tools.elixir-tools, startup: false, activationEvent: 'onLanguage:elixir'
2024-01-19 09:20:10.850 [error] Activating extension elixir-tools.elixir-tools failed due to an error:
2024-01-19 09:20:10.850 [error] Error: Download failed (https://github.com/elixir-tools/next-ls/releases/latest/download/next_ls_windows_amd64, status=404)
    at c:\Users\chgeuer\.vscode\extensions\elixir-tools.elixir-tools-0.12.1\dist\extension.js:2:432487
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

• Tool tries to fetch https://github.com/elixir-tools/next-ls/releases/latest/download/next_ls_windows_amd64
• Correct (I guess) would be https://github.com/elixir-tools/next-ls/releases/download/latest/next_ls_windows_amd64.exe

[cvkmohan]

I tried all I could - but - had to come back here. After reinstalling wsl2 on my system, next-ls stopped working.

glibc is 2.35 - and I tried all troubleshooting in https://www.elixir-tools.dev/docs/next-ls/troubleshooting/

1. No logs are getting recorded.
2. I have pasted vscode Output tab error in the above image.
3. When I start nextls independently and run it in tcp mode it is working fine.

However, when I install the latest vscode extension and reopen the download is not happening into /.cache/elixir-tools directory. Even if I have downloaded the executable manually and placed in the directory - vscode extension is not picking it up - and - autostart is not working.

[mhanberg]

I'll try and get windows installed today and try it out.

Sorry about that!