Conversation
… (Rocks) in the path of the core of the project.
solving existing problems (except notify, which I still don't know why it doesn't work).
Contributor
Author
|
Most of the work is done: |
modifying the bundles system removing some prerequisites that were activated automatically.
…ew system according to treesitter and more optimizations.
…s been solved, but it still writes [LSP] the name of most of the outputs.
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
2 participants
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 marks the beginning of the migration of nvpak to rocks, as well as its scheduled updates. If you would like to assist, please review the current plugins and suggest better alternatives that might replace the existing tools. As you know, nvpak is a distribution meant to maintain the prerequisites for a Neovim configuration.
The new version will not remain entirely on Lua, so the only thing you need to consider is compatibility with rocks and the new lazy system. For instance, the dashboard is compatible with rocks but does not adhere to the new lazy system, causing a delay in Neovim's loading. Another example is mason, which might soon be replaced by rocks itself.
Additionally, we highly appreciate contributions from those willing to help rewrite and refine the README and write the wiki.