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

Selected/Diff highlight is hard to read #34

Closed
ltpquang opened this issue Nov 14, 2022 · 4 comments
Closed

Selected/Diff highlight is hard to read #34

ltpquang opened this issue Nov 14, 2022 · 4 comments

Comments

@ltpquang
Copy link

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?

image

image

@kkrypt0nn
Copy link
Member

kkrypt0nn commented Nov 14, 2022

No idea how you got that but I cannot reproduce it with any variant of the theme, make sure you don't have something interfering with it.

Also running on 2022.2.3 Build #IU-222.4345.14, built on October 5, 2022 with Catppuccin 2.0.3

Frappé

image

Macchiato

image

Mocha

image

Do we need to strictly stick to Catppuccin's pallete?

That is the purpose of a palette and ports related to it, yep

@ltpquang
Copy link
Author

ltpquang commented Nov 16, 2022

@kkrypt0nn thank krypt, I get problem only with Frappe, other variants seem to be fine, could you please share your Color Scheme of DIff & Merge?

image

image

@kkrypt0nn
Copy link
Member

Sure thing, these are the settings for Frappé that I have after installing the plugin:

Changed lines

Changes

image

Conflict

image

Deleted

image

Inserted

image

Folded unchanged fragments

Background

image

I've updated in the meantime to 2.0.4, maybe you can try to do that and see if it fixes your issue.

@ltpquang
Copy link
Author

I noticed that the color scheme name of mine is different than yours, at first. It's was bold and violet.

image

I then tried to reset the scheme to default and everything is fine now.

image

It's weird that uninstalling/reinstalling the plugin doesn't fix the scheme, we need to explicitly reset it to default.
Thanks for you support @kkrypt0nn. 🥳

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

No branches or pull requests

2 participants