-
Notifications
You must be signed in to change notification settings - Fork 17
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 #166
Comments
false
Hey 👋 thanks for reporting! I don't believe we've had a chance to test the installer on Windows. What's strange is that the stack trace doesn't contain the location of the installer script, which leads me to believe this may be a general incompatibility of Are you able to run |
Sorry for late reply, here is the results of
Also here's the result of
Even though both |
Which version of luarocks does scoop install and what's the output of |
It's I will try to install different version |
Ok so I tried to set
Even though the result of
|
Unrelated to this issue but when cloning luarocks maybe use |
Okay I think I found the problem. So I tried to use another luarocks version, I download a standalone binary from here.
But it still can't install rocks.nvim
So I tried another way with installing And I tried to compare those three luarocks executable:
Gotcha! I'm thinking maybe the cause of the error is Here's the result after I tried to run
|
Thanks for troubleshooting this! I've looked at the neovim source.
and can confirm that Regarding: We use @vhyrro What do you think? Maybe we should use luarocks 2.0.2 is very outdated and unlikely to work with rocks.nvim (we should probably add a minimum version requirement check to the installer).
Are you still using lua installed with Now that I think of it, even if you fix the issue with luarocks not finding lua, you'll probably run into issues installing one of rocks.nvim's dependencies, |
In my config I set it to
I plan to stick to |
Would you be able to test if using
We recommend to use |
I'll try to test outside neovim first It seems hererocks act differently with and without admin priviliges. Probably this is an issue on Without admin privileges
With admin privileges
|
Okay 👌 I will try to find a way to make |
This is the toml-edit dependeny issue I mentioned earlier, for which we have a fix in the pipeline. @vhyrro could you trigger the luarocks upload workflow for toml-edit manually? It looks like the last run failed with an API error. |
@tembokk the toml-edit issue should be fixed now. |
Still produce the same error. I think the problem is not toml-edit because it's been successfully installed
I think the problem is fzy
|
That's strange. I think fzy needs MVSC to be installed, so that you can build it on Windows. |
On Windows, `sh` might not be available (e.g. if not installed with git). Even if git `sh` is installed, it may not see everything that is on the `PATH` (see #166). The default `vim.o.sh` on Windows is `cmd.exe`. On Linux and MacOS, the script should behave as before.
On Windows, `sh` might not be available (e.g. if not installed with git). Even if git `sh` is installed, it may not see everything that is on the `PATH` (see #166). The default `vim.o.sh` on Windows is `cmd.exe`. On Linux and MacOS, the script should behave as before.
@tembokk the fzy issue should be fixed now 😃 |
Still the same issue.
It's weird, it seems, on my PC, fzy won't handle space in path correctly 🤔
Should be |
That error is caused by luarocks trying to compile fzy, which is strange, because the rocks.nvim installer should tell luarocks to fetch it from a binary server. Are you able to run
? It could be that luarocks doesn't fetch the I believe if you run |
This is the result of my
Also I find out that the cause of |
Hmm, based on your config it appears to be the correct architecture. Are you able to run |
That's because when you run luarocks as an admin, and when you run luarocks as non-admin (with the If you can install
... but this will install rocks.nvim and its dependencies to a different location than rocks.nvim expects (it uses the I've pushed the
again? |
Ah got it. Thank you for the info
I will try it again |
I got this error:
So I manually edit
|
Ah, I think I know what's happening. I think if you change |
Somehow neovim crashed nvim-rocks-forceclose.mp4 |
Oof, that's going to be hard for me to troubleshoot without a Windows machine. I suppose you could go into the rocks.nvim installation and try to comment out parts of the plugin/rocks.lua file, so we can get an idea when it is crashing. Thanks for all the patience by the way 🙏 |
Okay
I'm not in hurry or anything so it's fine 👌 😄, also I really like this project |
false
I've added a GitHub action for Windows, and I think I can reproduce the crash. It appears to crash before the log file is created. |
🤔 it looks like it could be crashing even without rocks.nvim (at least my test command isn't printing to stdout [note: I have to redirect stderr because neovim prints to stderr]). @tembokk are you able to run neovim nightly (without rocks.nvim) on Windows? |
Update: I fixed the init.lua I was using to test, and can confirm it segfaults on Windows. Now for the difficult task of finding out why... |
I've tracked down the segfault to a |
Thank you! So I just need to wait for that PR to be merged right? |
Yes, hopefully that should be the last hurdle. |
@tembokk I've removed the |
I've created a separate issue for the installer script: #255 |
Yep it's working thank you so much 😭🙏 I will report if there are any other unexpected issues |
My nvim version:
v0.10.0-dev-2388+gb12d193b4
I install
lua
andluarocks
throughscoop install lua-for-windows
Then on rocks.nvim installation I set
Set up luarocks (recommended) ?:
false
And I get this error
The text was updated successfully, but these errors were encountered: