Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

notify.nvim throwing warning when enabling cyberdream #22

Closed
idelice opened this issue Apr 28, 2024 · 2 comments · Fixed by #21
Closed

notify.nvim throwing warning when enabling cyberdream #22

idelice opened this issue Apr 28, 2024 · 2 comments · Fixed by #21

Comments

@idelice
Copy link

idelice commented Apr 28, 2024

After installing cyberdream to my LazyDistro:

return {
    "scottmckendry/cyberdream.nvim",
    lazy = false,
    priority = 1000,
    config = function()
        require("cyberdream").setup({
            -- Recommended - see "Configuring" below for more config options
            transparent = true,
            italic_comments = true,
            hide_fillchars = true,
            borderless_telescope = true,
            terminal_colors = true,
        })
        vim.cmd("colorscheme cyberdream") -- set the colorscheme
    end,
}

I get this warning everything I open up nvim:

   Warn  22:17:46 notify.warn nvim-notify Highlight group 'NotifyBackground' has no background highlight
Please provide an RGB hex value or highlight group with a background value for 'background_colour' option.
This is the colour that will be used for 100% transparency.

require("notify").setup({
  background_colour = "#000000",
})

Defaulting to #000000
@scottmckendry
Copy link
Owner

Thanks for raising! I never actually noticed this issue the whole time I've been working on the colorsheme. Mainly since I've had that block of code in my notify config the entire time.

Nonetheless, it's reminded me to finally get around to adding my own highlights for nvim-notify. I think it turned out quite clean!

@idelice
Copy link
Author

idelice commented May 5, 2024

Love it. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants