The tokyonight theme provides a nice integration with operators:

as opposed to catpuccino's current implementation:

(notice the difference between <<, <, =, ++, & and *)
Additionally, semicolons and comma are also highlighted, but I think that's a nitpick

The readme lists the way to get the colors for a theme as

This is working in main and i've been using it to modify some colors that i remap.

In the dev-remaster branch the call fails

E5113: Error while calling lua chunk: ...er/start/Catppuccino.nvim/lua/katppuccino/api/colors.lua:4: module 'katppuccino.core.cs' not found:
        no field package.preload['katppuccino.core.cs']
        no file './katppuccino/core/cs.lua'

The get_colors() function is provided by https://github.com/Pocco81/Catppuccino.nvim/blob/f90dcc9e4f860ce50d002b4cf2e0861a376f574f/lua/katppuccino/api/colors.lua#L3-L5

which depends on katpuccinno.core.cs, which was deleted in 0b177ad

As it was discussed under #44, one of the objectives was to create an org. The project has been growing so much, not only in stars, but also in users. ATM the most accurate way I know how to get this number is by searching in all of github for catppuccino (because the name is unique enough) and writing down the amount of times it has been mentioned.

People actually love this, that's why we are creating an org for it.

I thought the name was original enough when I first came up with it, but unfortunately it seems like it wasn't. It sucks a lot to say this but we need to rebrand the project because of this. Of course this won't stop the still ongoing development, however the faster we rebrand the project the easier it will be to update the codebase now that it is so small. Doing this further down the road will disrupt web searches, delay deployments, but most importantly, affect active users negatively.

With that said, feel free to leave name suggestions below :)

Conditions (maybe?)

Since we now have the freedom to choose a name more keen and inline to the current objectives/color palette I think it'd be good to start from there. The only conditions I'd put for the name would be:

• give cool vibes.
• not too short, not too long.
• preferably be a portmanteau (AKA a word that results from blending two or more words, like Catppuccino = Cat + Cappuccino)
• don't start with letters people with speech impediments often struggle to pronounce (R, L, Th, ...)

Feel free to ignore what I just said, just properly justify yourself :)

Hey @pocco81 as you asked in the VapourNvim issue I will be very happy to team up with you. I am trying to make a rice with this colorscheme but there is just one small issue that there is very less contrast in lualine. It would be great if you could make the text to a lighter color or add a light background to the text. Here is a screenshot:

Pocco,

First of all, I truely admire the effort and transparency you put into this project.

As far as I'm concerned, I don't like the new palette that much and would very much prefer to keep using the neon-latte flavor. I hadn't followed #44 closely and I didn't realize that neon-latte was removed during the remaster. Could you please add a line to the README that points out to the commit corresponding to the last good version of neon-latte (both palette and docs, somehow using colorscheme neon_latte was not working for me, so I had to manually configure the theme and I don't remember how (that's on me)).

Thank you and have a nice week-end.

Hello, nvim-cmp recently merged a PR for using floating windows instead of the native menu when autocompleting and introduced some highlights that are available for further customization. I think we can get a cool catppuccino floating window:D

Edit: forgot to mention, idk if you use nvim-cmp so if you think it's hard to setup for you I could post some screenshots showing different highlights, or even open a PR and then we can talk about the colors to include.

Did packersync today and got this error. Was working fine before.

Note: Subscribe to the issue to get notified about Catppuccin's progess

Edit: refer to this project, which tracks Catppuccin's initial release.

Hello everyone! thanks for using Catppuccino.nvim and taking time to read this.

After the initial release I've been thinking about adding some new stuff and replacing other things. However, throughout the development I've found certain incongruences around it... Hence this issue.

• Notices on the Katppuccino's status is being given here.

Ideas

All of the following ideas are oriented towards improving consistency and code quality:

1. The name of the themes: after looking around and nitpicking over how other themes (not only for nvim) are naming the "variants" of their themes (e.g. a light version, dark version, ...), I've decided to do the same for Catppuccino. Consistency is key and naming the themes like how is being done regardless of them following a convention, feels inconsistent. Therefore themes will be named: [adjective] Catppuccino (e.g. Neon Catppuccino). Suggestions are welcomed.

2. Let's talk about the color palette(s): initially the idea with Catppuccino, unlike other color palettes, was create other color palettes based on a "base color palette". This was kind of accomplished. I created the Catppuccino color palette (which was once in the repo AFAIR) and as you may have already noticed, all the themes share several colors like the white, pink, magenta, red, etc. But lately with the introduction of new variants this hasn't been quite as true as it used to, giving a feel that they are different themes (not THAT different but you get the idea). Because of this, the color palettes will be refactored as well.

3. Syntax: syntax and UI highlighting is the most important thing following the color palettes. I personally think that the syntax highlighting in Catppuccino is just awesome, it's really what makes Catppuccino Catppuccino. Further improvements and suggestions are very welcomed nonetheless.

4. New objective: "be an eye-candy and easy on the eyes colorscheme suited for various degrees of lightless and easy to adapt to other environments (web sites, WebApps, DEs, ...)" and it will, of course, accomplish this with the numerous things mentioned above.

5. I'm thinking about removing Soft Manilo after #43 gets merged (before it has to be refactored taking into account the aforementioned ideas). Perhaps it'd be good to stick with the following styles:

6. If people really really like this I will consider turning this into an org and extend the boundaries of Catppuccino, making it available as themes for web browsers, desktop environments, other editors, other applications (tmux, terminal emulators, ...) etc... Of course, people willing to maintain Catppuccino for x thing (e.g. for Firefox) would be welcomed to the org.

7. The doc gotta be improved. Edit: the best option would be to auto generate documentation based on the README (or any other file for this matter) and perhaps do this through CI using md2vim. I'll write some shell scripts for this.

8. The project hasn't had any speed related issues, yet, I'll add asynchronous loading to enhance the theme for users who like to load theirs like this.

Objectives

• rename the theme variants
• change some colors
• refactor extras/
• rethink which variants are going to be on Catppuccino
• write documentation using md2vim
• add asynchronous loading

New Ideas <-- read this

Edit 1: I’ve been reading about themes lately and I’ve two new ideas, which are just IDEAS at the moment:

1. Perhaps create geometric color palettes? I was reading about Dracula PRO (an awesome theme indeed) and it follows a mathematical approach as opposed to what the standard colors of the Dracula theme used to follow in order to “normalize lightness and saturation”. This is an awesome idea and it’s the first theme I’ve seen doing such a thing.
2. Perhaps standardizing a single color palette? Following my point above about Catppuccino “not seeming to be anything in particular but aspiring to be everything”: I was checking big names in the colorscheme forest (most notably Nord, Dracula, One Dark, Gruvbox, Molokai) and… they all have one single palette (notice that not all of them have the same amount of colors and some have specific colors for syntax related stuff). That would be a nice approach to follow if we try to project Catppuccino to other platforms in terms of maintainability and stability. Furthermore, having one single color palette will make it a more identifiable theme, because as of now, if one sees one of the current themes one won’t be able to tell they have the same root. If this EVER TAKES PLACE I expect people to be mad because this would imply the removal of some themes in order to stick with one (which could be the result of a fusion between the current one), I'll fork this project and maintain it.

Is the README on the dev-remaster branch up to date? I'm not having any luck installing following the guides. use "Pocco81/Catppuccin.nvim" fails to install using packer. Should this be use "catppuccin/catppuccin"?

Would you be open to adding a stylua formatter config? I can make a PR for it if so.

I ask because, when submitting my most recent PR, my formatter ran with default settings and I had to mess with the format to not add unnecessary changes.

I can add a .stylua.toml file that sets the settings to how you have the project formatted currently.

Kitty has a themes kitten which sources themes from their themes repo and then can automatically fetch the specified theme. I was wondering if you'd be willing/interested in submitting your themes. I'd have already created PRs for them myself, but you created them and I figured you might want the credit for those contributions.

Hello! I like my neovim very colorful, so I use the plugin nvim-ts-rainbow and I'd like an integration for this color scheme since I love it! Thanks!

As u can see the warning cannot be read clearly inside the popup window.

Great colorscheme. No complaints 😄

I like to have the top-level folder visible, and it also doesn't look good when you have cursorline enabled:

The 'NavBar' and "Home' should be different color (like yellow), I used treesitter (javascript) and also turn it on in the config

Or I miss out something

How do I get sidebars such as nvim-tree to have the darker color like your screenshot? I'd also like to apply this darker color to terminal buffers and Telescope if possible.

Hello! just to bring the discussion of #22 in a brand new issue. As I said in my last comment there, bufferline does not support color schemes to override its highlight groups anymore, so the current integration with Catppuccino doesn't work out of the box unless making some tweaks to packer.nvim (if using it). So I suggest to instead of highlight groups provide a lua table containing the desired colors which we can call from bufferline's setup function which is what bufferline expects.

I'm not sure if this is just an issue because my terminal has a slightly transparent background, and subsequently, so does nvim. But it's incredibly hard to see what is being selected when I'm in visual mode.

These themes look absolutely great. Good light themes are especially hard to find. Consider me a fan...

I see that Sneak is integrated, so it would make sense to do the same for Lightspeed too (I'm the author/maintainer).

1. I'd like to get some help with an actual bug. When Catpuccino is load()-ed, it clears out the highlight groups of Lightspeed, making the plugin unusable (we have an autocommand set up for the ColorScheme event - thus :colo catpuccino is OK -, but that is of no help in this case). I suppose we cannot fix this on our side(?), require'lightspeed'.init_highlight() should be called again somewhere, when loading Catpuccino.

2. This might not be too pressing, as Lightspeed washes out the highlights underneath the area, like EasyMotion, and its defaults are perfectly okay-ish anyway, especially for the two dark versions. But if you think you can come up with some good tweaks, particularly for light-melya, that would be very cool. I'd be happy to assist with anything, if needed. (Or I might do a PR sometime in the future, though I think I'm too lazy for tweaking with the colors again, it was enough for me once :) .)

Hey! when I install catppuccin and set term_colors to true I get the following error:
acker.nvim: Error running config for Catppuccino.nvim: /Users/luis/.config/nvim/lua/plugins/catppuccin.lua:55: Vim(lua):E5108: Error executing lua ...ker/start/Catppuccino.nvim/lua/catppuccin/utils/util.lua:120: attempt to index local 'clrs' (a nil value)

I like the details you've put on this color scheme, from documentation to flexibility in configs. Did you grab a template or fork some other project to get started with this one? I'd like to make my own color scheme in the future :p thanks!

is this the bufferline of this theme, I feel like that exactly the same when I set 'false' and 'true' to bufferline in the setup

Sorry I accidentally submitted this issue and didn't realize. The original issue is described here.

I use alacritty, transparent_background option doesn't seem to make an effect as you can see above.

My catppuccino setup:

local present, catppuccino = pcall(require, "catppuccino")
if not present then return end

catppuccino.setup({
    colorscheme = "catppuccino",
    transparency = false,
    styles = {
        comments = "italic",
        functions = "NONE",
        keywords = "NONE",
        strings = "NONE",
        variables = "NONE",
    },
    integrations = {
        treesitter = true,
        native_lsp = {
            enabled = true,
            styles = {
                errors = "italic",
                hints = "italic",
                warnings = "italic",
                information = "italic"
            }
        },
        lsp_trouble = false,
        lsp_saga = false,
        gitgutter = false,
        gitsigns = false,
        telescope = false,
        nvimtree = false,
        which_key = false,
        indent_blankline = false,
        dashboard = false,
        neogit = false,
        vim_sneak = false,
        fern = false,
        barbar = false,
        bufferline = false,
        markdown = false,
    }
})

catppuccino.load()

After you open new buffer; press C-v and then, for example, ESC, pasted character will be blending with background.

Screenshots

Hello! what about having the option to choose between underlines and undercurls for lsp diagnostics? like this:

I set term_colors to true and when I enter neovim the following error appears:

This is my complete catppuccino config:

local catppuccino = require('catppuccino')

catppuccino.setup {
   colorscheme = 'neon_latte',
   term_colors = true,
   styles = {
      comments = "italic",
      functions = "italic",
      keywords = "italic",
      strings = "italic",
      variables = "NONE",
   },
   integrations = {
      treesitter = true,
      native_lsp = {
         enabled = true,
         styles = {
            errors = "italic",
            hints = "italic",
            warnings = "italic",
            information = "italic"
         }
      },
      lsp_trouble = true,
      lsp_saga = false,
      gitgutter = false,
      gitsigns = true,
      telescope = true,
      nvimtree = {
         enabled = true,
         show_root = true,
      },
      which_key = true,
      indent_blankline = true,
      dashboard = true,
      neogit = false,
      vim_sneak = false,
      fern = false,
      barbar = false,
      bufferline = true,
      markdown = true,
      lightspeed = false,
   }
}

catppuccino.load()

correct me if I'm doing something wrong or I missed some documentation please :'(

Error detected while processing /home/ashin/.local/share/nvim/site/pack/packer/start/Catppuccino.nvim/colors/catppuccino.vim:
line 12:
E5108: Error executing lua ...acker/start/Catppuccino.nvim/lua/catppuccino/core/cs.lua:21: bad argument #1 to 'next' (table expected, got nil)

gitsigns has no color contrast

I have the following code in my init.lua:

catppuccino.load()

vim.cmd('hi TabLineFill ctermfg=black ctermbg=black')
vim.cmd('hi TabLine ctermfg=white ctermbg=black')
vim.cmd('hi TabLineSel ctermfg=red ctermbg=black')

It seems like Catppuccino is overriding my highlight groups for this though:

:verbose highlight TabLineFill
TabLineFill    xxx cterm=reverse ctermfg=0 ctermbg=0 guibg=#0B1216
        Last set from anonymous :source

Is there a way to override the highlight groups for the tabline?

Sort of just what the title says. Depending on which colorscheme within catppuccino I use, the background for the gitsigns aren't transparent.

If I set it to dark_catppuccino only the git delete highlights aren't transparent:

If I set it to catppuccino none of them have transparent backgrounds:

Any idea how I can fix this, even if it's just setting a custom color for my instance?

Good afternoon!

I'm loving this theme but having some issues. I cannot get this theme to set in lualine following the repos instructions. Here is my current config for both plugins. I can change the lualine theme to any of it's builtin themes but this one isn't working.

use {
  'shadmansaleh/lualine.nvim',
  config = function()
    require('lualine').setup {
      options = {
        component_separators = '',
        section_separators = '',
        theme = 'catppuccino',
      },
    }
  end,
}

  use {
    'Pocco81/Catppuccino.nvim',
    config = function()
      require('catppuccino').setup {
        colorscheme = 'dark_catppuccino',
        term_colors = true,
        integrations = {
          gitsigns = true,
          which_key = true,
          telescope = true,
          nvimtree = {
            enabled = true,
          },
        },
      }
      vim.cmd [[colorscheme catppuccino]]
    end,
  }

Thank you for any help or insight you can provide!

Hello! Is there a way to integrate highlight colors for indent-blankline through g:indent_blankline_char_highlight_list? like an option in the config.

Hey! I can see there's no border when splitting windows:

Is this intended? If so, can we have an option to activate borders? I'd personally like keyword's color (purple) as the border color for a neon fashion style, but choosing it explicitly would be great too!

I'd like to add a "soft Manilo" theme, similar to the dark catppuccino theme but primarily with a softer dark gray background.

Cheers!

I saw the theme on Reddit earlier and decided to try it out. I like it so far, but I can't get it to run in NVIM.
I've added Plug 'catppuccin/nvim' into my plugins file, but when I try to install, it just doesn't show up at all? No error, no nothing. (Screenshot: https://i.imgur.com/mShA8zF.png)

I've seen the other issue (#63) about Vim Plug, and just to make sure I've tried to add the full git address plus a specified branch – Plug 'https://github.com/catppuccin/nvim.git', {'branch': 'main'} – but this also didn't yield any results.

(Un-)Installing other plugins works without any issues. Am I missing something? This might be a really stupid mistake, and I'm just blind..

Just for good measure:
I'm running on MacOS Catalina (10.15.7)
NVIM is up to date (v 0.6.0)
VimPlug also is up to date – updated via PlugUpgrade

Hey! We can have more colors to the cmp completion menu since this:

https://www.reddit.com/r/neovim/comments/r42njg/here_are_the_vs_code_theme_colors_for_the_new/

It would be nice to add it 😊

it's difficult to read.

Hi, when I set the keywords in my config to be italic I would like the "import" and "from" keyword (in case of JavaScript) to be italic as well:

I can achieve this by overriding the highlight TSInclude in the config but I think this should be a default since those are keywords from the language and that highlight might apply to other languages as well.

I get this error:

x nvim:
    fatal: invalid reference: master

After I quit and try to install it again it is marked as "already installed"

When I try to use it I get this:

Error detected while processing /home/rgamuf.configinvim/pluginvim/colors/catopuccin.vim: line 3: E5105:
Error while calling lua chunk: ...mq.configinvim/pluginvim/lua/catopuccin/core/mapper.lua:191: attempt to call field 'ttildeep_extend' (a nil value) Press ENTER or type command to continue' 

Also the first installation that I did was successful, but then I got the above error

Hi, since neovim nightly changed a few things regarding diagnostics, it would be better to refactor the native_lsp integration into a more general diagnostic as I think this is the way things are going. This will also transparently apply the same gui and guisp styles for all diagnostics (Spell*, DiagnosticUnderline* and legacy LspDiagnosticsUnderline*)

Also, for some reason DiagnosticHint seems to be unset:

I have this in my catppuccin config to solve the issue temporarily.

    vim.cmd('hi! link DiagnosticHint String')
    vim.cmd('hi DiagnosticUnderlineError gui=undercurl guisp='..require"colors".get_color('DiagnosticError', 'fg'))
    vim.cmd('hi DiagnosticUnderlineWarn  gui=undercurl guisp='..require"colors".get_color('DiagnosticWarn', 'fg'))
    vim.cmd('hi DiagnosticUnderlineInfo  gui=undercurl guisp='..require"colors".get_color('DiagnosticInfo', 'fg'))
    vim.cmd('hi DiagnosticUnderlineHint  gui=undercurl guisp='..require"colors".get_color('DiagnosticHint', 'fg'))

Awesome colorscheme btw ;)

Hi @pocco81 .
I absolutely love this theme.
But one thing that concerned me was after editing a file there would be some diffs right. So the count of the diffs are blended to background in lualine.
Here is the screenshot:

I think you need to update the color of this

I activated the integration for bufferline and this is how it looks:

I can barely notice the background of the tab among with its shape, I would expect something with more contrast like this:

Can't we have some more contrast like that one? Although I don't know how this would affect the other flavors of the colors scheme, I'm ussing Neon Latte.

Follow the guide, but the result doesn't like my expectation. This is default lightline colorscheme.

Correct one should be:

Hey :)

I have been using Catppuccino for awhile, just switched to Catppucin. Something I noticed is a color seems to have disappeared that is used in lazygit that was there before the switch

is this something i can change?

Lualine is one of the most popular status line plugins, and lots of color schemes also offer themes for Lualine.

This theme looks really, really great btw.

I noticed that when using treesitter, the color for delimiters, such as semicolons, parentheses, and brackets are a dark gray, like below:

This does not occur without treesitter:

Is this intentional? In my opinion delimiters should always be a bright color.

Hey! Since a few weeks I wanted to start contributing to this project by creating PR but I have an issue with rendering lua files and I think it's related to indentation with stylua, right now when I open a lua file from this project it looks like this:

As you can see some of the text is not visible.

I just wanted to know if you are familiar with this issue. I have editorconfig installed and stylua via cargo. I'm using gnome-terminal.

Thanks!