How can I force a plugin to load earlier? (rocks-config
)
#265
-
I have my colourscheme working based on the
So I added Is |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
UpdateThis issue has been solved since version 2.25.0. rocks.nvim now maintains symlinks in a Plugins with Original responseHey 👋 This seems to me like an issue with the A proper solutionto this would be to fix this in heirline.nvim, by changing For now, you can work around this by calling @vhyrro is planning to work on a Footnotes
|
Beta Was this translation helpful? Give feedback.
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
andrequire("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…