feat: provide rocks-nvim as a vim plugin #634
Draft
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
such that it can be used directly from the flake via `self.inputs.rocks-nvim.packages.${pkgs.system}.rocks-nvim`.
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.
I wanted to install the plugin directly via
self.inputs.rocks-nvim.packages.${pkgs.system}.rocks-nvimbut noticed this was not possible as the attribute is the lua package.As I am not used to haskell-parts, I first thought it was not available, seems like vimPlugins and lua sets are modified via overlays instead.
The composition of overlays can be tricky, I for instance have several customizations and would like the possibility to override selectively the plugins as well via for instance
rocks-nvim = thisFlake.rocks-nvim-nightly.To be clear it's not meant to be merged as is especially as it changes the value for the default package) but rather to discuss how to expose those.