background variable not detected correctly on boot about nvim HOT 7 CLOSED

This has been a bug for a long, long time. I was able to fix it in an older commit with this patch:

index f785fdb..27d8282 100644
--- a/lua/catppuccin/lib/highlighter.lua
+++ b/lua/catppuccin/lib/highlighter.lua
@@ -36,7 +36,7 @@ function M.load(theme)
 	end
 	g.colors_name = "catppuccin"
 
-	M.properties(theme.properties, "o")
+	-- M.properties(theme.properties, "o")
 	M.syntax(vim.tbl_deep_extend("keep", theme.custom_highlights, theme.integrations, theme.syntax, theme.editor))
 
 	if require("catppuccin.config").options["term_colors"] then

Just updated tonight and noticed it's broken still. That module has also been deprecated.

from nvim.

You can work around the issue by loading the color scheme after the background option is set,

vim.api.nvim_create_autocmd("OptionSet", {
	pattern = "background",
	callback = function()
 		vim.cmd("Catppuccin " .. (vim.v.option_new == "light" and "latte" or "mocha"))
	end,
})

Edit: If you are using something like lualine that references catppuccin, you'll also want to put its setup in the callback function, or the colors will be based on mocha (?).

from nvim.

I added a quick fix

Try this:

require("catppuccin").setup { flavour = "auto" }

from nvim.

@nullchilly

I gave that a try and something weird happens:

• If I set my GNOME theme as Light, Neovim will open with CTP latte (everything fine with this)
• If I set my GNOME theme to Dark, Neovim will not load the CTP theme (well, the theme is loaded, it just not being applied)
  • The bg var is set to dark correctly, tho
  • I can manually the theme doing colorscheme catppuccin-[flavour]

from nvim.

Super new to Neovim but I think this is happening for me as well. With flavour = "auto" set, the light theme loads just fine but the dark theme doesn't look right. Running :colorscheme catppuccin-[flavour] produces the ideal result.

I'm using macOS / AstroNvim.

from nvim.

  if (option_was_set("bg") || strequal(p_bg, value)) {
    // background is already set... ignore
    return;
  }
  if (starting) {
    // Wait until after startup, so OptionSet is triggered.
    do_cmdline_cmd((value[0] == 'l')
                   ? "autocmd VimEnter * ++once ++nested :lua if not vim.api.nvim_get_option_info2('bg', {}).was_set then vim.o.bg = 'light' end"
                   : "autocmd VimEnter * ++once ++nested :lua if not vim.api.nvim_get_option_info2('bg', {}).was_set then vim.o.bg = 'dark' end");
  } else {

Referring to the neovim 0.9.5 code, an OptionSet event won't happen if:

1. bg was explicitly set,
2. or term bg is dark.

I guess, CAT should respect, but not depend on, OptionSet events, when "auto" is used.
Preferably, monitor bg change and respond automatically without restarting nvim.

from nvim.

@nullchilly

I can confirm that with the recent changes, using require("catppuccin").setup { flavour = "auto" }, it works.
I'm gonna close this since it is resolved with that change. In case flavour = "auto" is not already documented on the README, I will do the PR myself.

Tysm guys !

from nvim.