Loading colorscheme (tokyonight.nvim)

[Rasmus-Bertell]

I'm trying to switch to rocks.nvim from lazy.nvim but I'm having trouble loading colorscheme.

My rocks.toml file is

[rocks]

[plugins]
"rocks.nvim" = "2.17.0"
"oil.nvim" = "2.7.0"
"tokyonight.nvim" = "3.0.1"

and in the end of my init.lua I have

require('tokyonight').setup({ style='night' })
vim.cmd.colorscheme('tokyonight')

but I get an error that the colorscheme is not found, however running :colorscheme tokyonight-night works.

Is there something I'm missing?

Edit:

I also tried with rocks-config.nvim, but it had the same problem. I could run require('tokyonight').setup() but right after it vim.cmd.colorscheme('tokyonight') didn't work.

[Rasmus-Bertell]

I did some more trial and error and got it working by placing the config for the colorscheme in .config/nvim/after/plugin/tokyonight.lua. I'm leaving the conversation open if there are some other ways to accomplish this.

[mrcjkb]

Hey 👋

Neovim sources your init.lua before plugins are sourced.
lazy.nvim overrides the built-in loading mechanisms, and the LazyPluginSpec.config function is called after it loads plugins.

With rocks.nvim, the initialisation sequence is the closer to Neovim's built-in one (unlike lazy, we don't disable the built-in one), with two differences:

• A luarocks plugin's lua API (the lua directory) is immediately available on the lua package.path (which is why you can call require('tokyonight').setup() in you init.lua, which wouldn't be possible with plain Neovim).
• Runtime directories (colors, plugin, autoload, ...) are added to the runtimepath and sourced when Neovim loads rocks.nvim, which is after sourcing your init.lua.

For colorschemes, to automatically load them, your best bet right now is in after/plugin.
We do provide a :Rocks packadd command, which you can use to explicitly load plugins where opt = true, but I just realised that command is not available when your init.lua is sourced 😞.
We can fix that by providing a public lua API for it: #213

Update: This has now been merged, so you can use require("rocks").packadd("<rock_name>") in init.lua.

You should be able to use vim.cmd.Rocks {"packadd, "tokyonight" } to load it with rocks-config.nvim though.

[Anrock]

I've tried this in my init.lua

require('rocks').packadd('gruvbox')
require('gruvbox').setup()
vim.cmd.colorscheme('gruvbox')

but it still errors with "colorscheme not found" (but still being available with manual :colorscheme command). Could the proper way with example be added to README?

[mrcjkb]

I presume you're using gruvbox.nvim?

packadd takes the name of the plugin (including the .nvim suffix), not the name of the colorscheme.

[Anrock]

@mrcjkb Yup. That was it, thank you for the tip.

Still, I think the colorscheme scenario is pretty common and it should be covered in README. I found this discussion linked in some comment in some issue in rocks-config repo I think after 20-30 minutes of lurking here and there. Not the ideal way to discover.

[mrcjkb]

Thanks for the feedback.
I've been holding off on that because I'm still hoping to come up with a better solution.

[mrcjkb]

I think I have found a nice solution for this: #285