-
Notifications
You must be signed in to change notification settings - Fork 7
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
Lazy.nvim support, as it does not support rocks. #18
Comments
I've been wondering about that! I was thinking about directly integrating |
atm my not so genius idea is bassicly doing lua rocks
its scuffed but atm it kinda works . I need to actually properly use it first to see if this is a viable idea or not, atm its not erroring out anymore >.< |
That's great! Would be great if you could get back to me after testing this for a while. I'll then update the installation instructions so that lazy.nvim users can install this too (at least until we find a less clutch way of doing this). Thanks! |
Update this works, but, adding it to package.path doesnt really work i had to do some even more scuffed work around for now . where i just moved those files to my config, that being said im pretty certain there is a better way for this. Regarding the yaml.so path, that you can directly add through luarocks command xd I have a even more scuffed idea of just copying those files from lyaml, and the yaml .so and just making another package. Mainly because
This wont work or any other solution i conjured up, but the only one that does, and ive tested papis, works fine is adding it to yer config xd. On that note, while messing around with my papers, papis seemed to work without any errors. |
I've just checked in my local installation how the paths are set up. This is on nixos, so things look a bit different, but maybe this is helpful for you. The relevant paths seem to be:
Maybe this is helpful to avoid having to move files around. |
This is now solved by #19 |
As of the moment lazy.nvim does not support rocks, is there another way of installing this plugin ?
The text was updated successfully, but these errors were encountered: