Skip to content

How can I force a plugin to load earlier? (rocks-config) #265

Answered by mrcjkb
jumpyjacko asked this question in Q&A
Discussion options

You must be logged in to vote

Update

This issue has been solved since version 2.25.0.

rocks.nvim now maintains symlinks in a site/pack/opt directory, which makes installed plugins available on the runtimepath by the time Neovim sources init.lua, while handing over control of sourcing plugins to rocks.nvim.

Plugins with opt = true can now be sourced with Neovim's builtin :packadd, making :Rocks packadd and require("rocks").packadd obsolete.

Original response

Hey 👋

This seems to me like an issue with the heirline.nvim plugin.
Its API allows the colors option to be a function, which would be useful if it would evaluate it lazily (i.e. when the colors are needed).
But that's not the case. As soon as you call setup, it eva…

Replies: 1 comment 5 replies

Comment options

You must be logged in to vote
5 replies
@mrcjkb
Comment options

@mrcjkb
Comment options

@jumpyjacko
Comment options

@mrcjkb
Comment options

@jumpyjacko
Comment options

Answer selected by jumpyjacko
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants