-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Windows Support #102
Comments
Trying to use NextLS in WSL:
Trying to use NextLS on Windows:
|
windows is very weird, when dealing with dev tools. |
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 |
#144 - now that binaries are getting downloaded - will it work in WSL? |
@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. |
I can confirm that on WSL2, with Ubuntu 22.04, it is working. It downloaded the executable. One question: what is the correct place for the code completion of definitions? I mean - when you type |
This comment was marked as off-topic.
This comment was marked as off-topic.
Hey friends, tried installing it on windows and getting:
Plase notice that the correct filename is next_ls_windows_amd64.exe ! |
Yes, like @spapas mentioned
|
I tried all I could - but - had to come back here. After reinstalling wsl2 on my system, next-ls stopped working.
However, when I install the latest vscode extension and reopen the download is not happening into |
I'll try and get windows installed today and try it out. Sorry about that! |
My frustration in the question is more about - It was working earlier - not working now - what did I miss? |
There is a bug in the auto updater that I fixed yesterday, but if you delete Next LS and reopen VSCode, it should prompt you to install it. I just tested on my Mac and it worked, so I'm not really sure what is different about running VSCode on Windows using WSL2, which will require me to install and debug.
🙇 |
That updater is in 0.19.1 and that is not yet released? I tried reinstalling.
|
Correct, but that should only effect an existing Next LS installation trying to update itself. Thanks for the repro steps. Can you also include your Windows versions and WSL2 information? like what distro do you have installed with WSL2, also VSCode version |
Windows 11. WSL2 - Ubuntu 22.04 |
Thanks, downloading as ISO now |
Okay, sort of bad-ish news... Works on my machine 😅. Link to a video recording of me installing the extension for the first time: https://f005.backblazeb2.com/file/elixir-tools/elixir-tools-wsl-test.mp4 Timeline is basically
|
Thanks. You took a lot of effort. One difference I could spot is - you are using |
it did actually crash after i let it sit there for a minute, investigating that now, but seems orthogonal to your issue. I don't think asdf vs nix will make a difference for yours not even prompting you to install it
i'm not sure what you mean here
you can uninstall from the command palette (search elixir tools and it will be there), then restart to see if it prompts you to download
no 😎 |
Hmm, could you audit your settings to see what the value of |
It was showing empty. I clicked on the gear icon and asked it to reset it. |
Can you confirm is that directory exists at all? |
No. The directory does not exist. |
As an experiment, can you manually create that directory and then restart VScode to see if it tries to install it? |
No. nothing happened. This is the full error log.
|
can you check the permissions on that directory? |
and there is nothing in there in any of the dirs? |
yes, the directories are empty. |
Can you confirm your adapter is set to stdio and not tcp? In elixir tools settings |
Yes. I confirm. It is stdio. |
Not sure what happened. Today I uninstalled the vscode extension restarted WSL and installed nextls vscode extension. It downloaded the latest version and is working. Same process was not working earlier. Maybe your new release solved the issue? Anyway, thanks a lot for the effort. |
Nice! I added more logging so if it happens again we'll have more to go on |
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.
The text was updated successfully, but these errors were encountered: