Problem with colorscheme

[meflove]

I use catppuccin.nvim, when I open the first file everything works fine, but when I open several files, no matter from the terminal or through snacks.explorer, the colorscheme does not work as it should. my config

first file

second file

third file (opened from explorer)

[BirdeeHub]

So, theres 2 problems here, interacting in a confusing way.

First, this line may not be doing what you think it does. Your spec triggers ON (or, well, right before) vim.cmd.colorscheme. So, you would want to call that somewhere else.

In fact, you do call it somewhere else. You call it here. Which, should actually be moved to the end of that file rather than the top, so that it is after lze knows about the colorscheme plugin. That's my bad I think, but in my defense it did work the way I had it in the template XD

Which brings us to the second problem. You call it with "catpuccin-macchiato". But your spec is only set to trigger on "catpuccin". Try fetching the value from nixCats("colorscheme") in both places, or setting the colorscheme trigger to trigger on any of the cattpuchin colorschemes by providing a list of them.

Try addressing these, and reporting back if it helps or not.

---

Also, as an aside, priority does nothing unless you have lazy = false, or no other triggers defined for the spec. But it also won't break anything either.

And, to be completely honest, unless you install multiple colorschemes and change colorschemes at runtime, lazy loading colorscheme is probably not really worth the effort, you want to load it right away usually anyway, and currently you are, so take that for what you will.

If you really want to lazy load colorscheme still, you could try also adding this spec, to trigger whichever other colorscheme spec you have

{
  "load_colorscheme_spec",
  load = function()
    vim.cmd.colorscheme(nixCats("colorscheme"))
  end,
  event = "UIEnter",
}

But generally this is not adviseable, as setting the colorscheme before other plugins are setup is generally best, as certain things will sometimes grab highlight colors and not update when the colorscheme does. Personally, I load mine at startup.

[meflove]

I did as you advised, but I still get the same result, about lazy = false, I tried this but it didn't bring any result either

[BirdeeHub]

meflove/angeldust-nixCats@2e0f33c

In this commit, you tried moving the config out of the spec to load it eagerly.

However, in the same commit, you also removed catppuccin-nvim from your startupPlugins section of your categoryDefinitions, leaving only where you added it to optionalPlugins.

This means that it was only being installed to the opt directory, meaning you would need to call packadd first. But better would be to install it as a startupPlugins if the plan has changed to loading it eagerly

Also, the correct name for the lze spec, although it has now been removed entirely, was indeed catppuccin-nvim, as that is the name of the plugin, but the colorscheme name should be catppuccin-macchiato because thats the one you are trying to activate.

[BirdeeHub]

I opened 2 PRs.

1 for eager and 1 for lazy

Choose 1

[meflove]

i tried rebuild with ur commit, but i still get the same result

angeldust-nixCats = {
  url = "github:meflove/angeldust-nixCats/1a5bd442e9aa754e90db5e69c6da9b4eaaafc369";
};

[BirdeeHub]

Have you tried this in files that are not python?

Im running it and it appears to be working fine when Im browsing your config with it? For both nix and lua code?

I can go try a python project I guess?

[BirdeeHub]

hmmmm

Well its definitely happening in python

[BirdeeHub]

I see you also have a rust setup lets see if it also happens for rust or if its just python

[BirdeeHub]

It seems to be just python?

Confirm if this is just python for you as well?

[BirdeeHub]

If it is just python for you like it seems to be for me, Im not 100% what to do about it but your setup looks like you at least somewhat know how python LSP works, so maybe you would be able to debug that, and its also possible it is a bug in catppuccin in how its making colors for python lsp tokens

[BirdeeHub]

I might have found the issue

      disableLanguageServices = true,

You have this in python lsp setup

I commented it out and built the config and it seems to work in python files now.

IDK what that line does, but it sounded fishy and when I commented it out, I no longer seem to be able to recreate the colorscheme bug.

[meflove]

As I see it, yes, the problem is only with Python.

[BirdeeHub]

ok, so, more testing shows that if I add this line back the issue comes back as well

  disableLanguageServices = true,

So, IDK what this does, but it seems to be the problem.

[meflove]

Interesting, I had a problem with ty and I tried to fix it using this option, I tried disabling it and everything worked

[BirdeeHub]

Well, it also seems to be the source of the colorscheme not working.

Again, I have no idea what that does and haven't done enough python to be any more useful than you are at debugging the python lsp

But, because it was only python with the issue, I went there to debug, and it seems to be that line.

On the bright side for me, although it doesn't help you much, the way I am loading it in the eager version has no connection to lze whatsoever and it still happens, and the python lsp does still seem to be loading on the python filetype event as requested. So, its not lze's fault at least XD

Im going to convert this to a discussion?