fix(rockspec): adjusted luarocks executable to contain the appropriate extension on windows #1983
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e extension on windows
4 tasks
|
This PR is stale because it has been open 30 days with no activity. |
github-actions
bot
added
the
stale
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes the problems with
:checkhealthand package building on Windows when using luarocks.Previously it wasn't adding the correct extension, depending on the user setup.
Remarks:
LuaRocks has 2 different distribution packages, one that uses a
.batand another one that uses a.exe.vim.fn.executable()will work if the extension is omitted, butProcess.exec()will failThis should solve most of the Windows users headaches when using LuaRocks with lazy.nvim