Add information about building using vim.pack#161
Open
PatrickMassot wants to merge 1 commit into
Open
Conversation
Hi. Thanks a lot for your work on this plugin. This is my best effort at documenting how I got it to work using the new `vim.pack` of neovim 0.12.x. I am not at all a `vim.pack` expert, and this is purely based on the documentation I mention in the README. I’d be delighted to learn a better way. In particular the `cmake` version is complicated because I didn’t know a better way of chaining the two `cmake` calls using `vim.system`. A nice thing here is that, if I understand correctly, neovim will be able to work on something else while the first command is running (although on my machine both commands are essentially instantaneous). Warning: I tested this only on Linux (but I tested both `cmake` and `make`).
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
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.
Hi. Thanks a lot for your work on this plugin. This PR is my best effort at documenting how I got it to work using the new
vim.packof neovim 0.12.x. I am not at all avim.packexpert, and this is purely based on the documentation I mention in the README. I’d be delighted to learn a better way. In particular thecmakeversion is complicated because I didn’t know a better way of chaining the twocmakecalls usingvim.system. A nice thing here is that, if I understand correctly, neovim will be able to work on something else while the first command is running (although on my machine both commands are essentially instantaneous).Warning: I tested this only on Linux (but I tested both
cmakeandmake).Also note that I added those instructions before the other package managers, under the assumption that
vim.packis meant to become the goto package manager for people without very specific needs. But I understand this may be controversial, and in any case you should feel free to modify this PR in any way you want.