This PR is a WIP:

• [x] This PR doesn't have Mocha, Macchiato and Frappé themes yet
• [x] The colorscheme in some languages is not yet at the expected level
• [x] Variants generator (one file like this colors.json could allow to generate all 4 variants at once)

Latte (New UI Preview enabled)

Latte (Old UI)

(closes #10)

When selecting comments they become unreadable.

All three dark modes:

Light Mode

Is there a way to dynamically change comment colour based on highlight to account?

Catppuccin plugin version: 2.0.3 IntelliJ IDEA 2022.2.3 - Build #IU-222.4345.14

This is screenshot from my project's Diff Viewer. Do we need to strictly stick to Catppuccin's pallete?

Hello! Great theme - but I have a few comments:

1. When I use the new ui (here PHP Storm), the line separating the top "titlebar" from the rest of the application appears only above the sidebar. I think it should be over the entire width of the window in the same way as in the case of the status bar (screenshot below).

2. I think the line separating the numbering of the line from the code looks strange, but it seems to me that there should also be a line separating the side panel from the editor.

In order to make the theme easier available it would be nice to publish it on the Jetbrains Marketplace.

The initial upload has to be done manually with a Marketplace account. Updates can be published via gradle using a token.

If an org (email-)account is not yet available, I'd offer to upload with my account as according to this post ownership can be transferred later on.

@Pocco81

Seems like the recommendation of Copilot is always in pink color whereas it should be in gray color, see the difference between VSC and JetBrains, in this case IntelliJ IDEA. | VSC | IntelliJ IDEA | |----|---| | | |

Just installed v2 via the released file on PhpStorm 2022.2.3. Although they work well in Mocha and Macchiato, some file colors don't seem to have their corresponding match in Latte.

I could use custom colors, but then those wouldn't change when switching from light to dark theme.

This makes some minor changes to the language defaults for the Instance Field to change the color (actually to match what's in VSCode)

It also adds the ENUM_IDENTIFIER to change the Enum color from the same Orange color to the Light Blue color, which also matches what's in VSCode.

Rider doesn't actually have specific XAML support, so its still not perfect but this at least adds some color differentiation.

This fixes issue #8

Here's a quick example:

Hi, First of all, I wanted to thank you for this theme that I use daily 👍🏻 A little problem of visibility with the parenthesis and brackets though. The matching should be more visible (maybe add a border?)

Kind regards, Richard

I just noticed, that invalid characters are nearly invisible because it's black text on the dark background.

In the attached screenshot I added an $ character in line 6. Yes, there is the error hint but it's still not opimal that the character is so hard to see which can cause confusion.

Using JetBrains Rider, any XAML file that gets opened is basically all orange and white, with no distinction between imports, element types, properties, strings, etc...

I recently installed catppuccin, but the color scheme does not appear to be working. The texts are not highlighted, as shown in the image below. Update: Some areas of my file have the color scheme working, but others do not; I'm not sure what's causing this issue.

Hi there ;-) I noticed that when a refactoring action is not possible, the error message is not visible enough (maybe you should change the font color ?)

exemple: trying the action "Convert parameter to underscore section" which is impossible on this scala function: gives the following error message:

Kind Regards, Richard

Currently when you click on a line and select a portion of text on the same line it is very hard to recognize what you have selected without looking precisely at it. VSC on the other hand has much lighter color when selecting text.

| VSC | IntelliJ IDEA | | --- | --- | | | |

Changing it to have the same color would benefit a lot when trying to see which part is selected. VSC seems to be using

"editor.selectionBackground": palette.surface2,
"editor.selectionHighlightBackground": opacity(palette.overlay2, 0.4),

roughly looking at the code.