Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Bundle lua shim with rocks.nvim #386

Open
mrcjkb opened this issue Jun 15, 2024 · 5 comments
Open

Bundle lua shim with rocks.nvim #386

mrcjkb opened this issue Jun 15, 2024 · 5 comments
Labels
needs-triage

Comments

@mrcjkb
Copy link
Member

mrcjkb commented Jun 15, 2024

We already bundle a luarocks config.
With this, we can set variables.LUA = <path-to-nlua>.
This was referenced Jun 24, 2024
Closed
Closed
@mrcjkb mrcjkb linked a pull request Jun 24, 2024 that will close this issue
feat: configure luarocks to use Neovim as the Lua interpreter #411
Closed
@mrcjkb
Copy link
Member Author

mrcjkb commented Jul 8, 2024

Closing as not planned for now.

@mrcjkb mrcjkb closed this as not planned Won't fix, can't repro, duplicate, stale Jul 8, 2024
@mrcjkb
Copy link
Member Author

mrcjkb commented Sep 5, 2024

Reopening. We might not be able to use nlua, as the luarocks wrapper has a hardcoded shebang, but we might be able to use a simple shim.

@mrcjkb mrcjkb reopened this Sep 5, 2024
@mrcjkb mrcjkb changed the title Bundle nlua with rocks.nvim Bundle lua shim with rocks.nvim Sep 5, 2024
@bnwa
Copy link

bnwa commented Sep 24, 2024

Just to be clear, would this remove the need for users to maintain a ‘lua’ executable on path? I ask b/c on macOS, Homebrew does not install an executable with that name for any of its Lua runtime packages, so users have to maintain an alias it would seem.

@mrcjkb
Copy link
Member Author

mrcjkb commented Sep 24, 2024

Just to be clear, would this remove the need for users to maintain a ‘lua’ executable on path? I ask b/c on macOS, Homebrew does not install an executable with that name for any of its Lua runtime packages, so users have to maintain an alias it would seem.

Yes, this issue exists specifically because of the homebrew issue 😄

@bnwa
Copy link

bnwa commented Sep 24, 2024 •
edited
Loading

Just to be clear, would this remove the need for users to maintain a ‘lua’ executable on path? I ask b/c on macOS, Homebrew does not install an executable with that name for any of its Lua runtime packages, so users have to maintain an alias it would seem.

Yes, this issue exists specifically because of the homebrew issue 😄

Ohhhhh. Awesome, thanks.

@mrcjkb mrcjkb mentioned this issue Sep 28, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: configure luarocks to use Neovim as the Lua interpreter nvim-neorocks/rocks.nvim
2 participants
@mrcjkb @bnwa