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

unokai colorscheme #271

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

k-37
Copy link

@k-37 k-37 commented Dec 6, 2024

The colorscheme is inspired by Monokai. #270

habamax colorscheme was used as a starting point. Color palette is based on this one.

GUI

gui_00_sample_diff
gui_01_sample_messages
gui_02_sample_misc
gui_03_sample_popupmenu_kind
gui_04_sample_quickfix
gui_05_sample_spell
gui_06_sample_windows

256 colors

256_00_sample_diff
256_01_sample_messages
256_02_sample_misc
256_03_sample_popupmenu_kind
256_04_sample_quickfix
256_05_sample_spell
256_06_sample_windows

16 colors

16_00_sample_diff
16_01_sample_messages
16_02_sample_misc
16_03_sample_popupmenu_kind
16_04_sample_quickfix
16_05_sample_spell
16_06_sample_windows

8 colors

08_00_sample_diff
08_01_sample_messages
08_02_sample_misc
08_03_sample_popupmenu_kind
08_04_sample_quickfix
08_06_sample_spell
08_07_sample_windows

@romainl
Copy link
Collaborator

romainl commented Dec 9, 2024

Thank you very much. We will take a look as soon as possible.

@romainl
Copy link
Collaborator

romainl commented Dec 12, 2024

This seems to work very well. My only (minor) gripes would be with…

  • the way the number of windows is highlighted in a tab:

    Capture d’écran 2024-12-12 à 08 08 11

    FWIW, it is handled via the Title highlight group.

  • and possibly the lack of contrast in "inactive" UI sections. I tested with 244 instead of 242, here:

    Capture d’écran 2024-12-12 à 08 17 19

@habamax @neutaaaaan What do you think?

@habamax
Copy link
Collaborator

habamax commented Dec 12, 2024

Looks good. Probably issue with my monitor setting, ErrorMsg is too dark for my eyes.

image

And yes, currently Title has the same color as Normal, instead guifg/ctermfg=NONE should be set to play nicely with tabpage.

image

@k-37
Copy link
Author

k-37 commented Dec 13, 2024

@romainl and @habamax thank you for taking time to review the PR.

I just pushed changes regarding Title and "inactive" UI sections.

Is there a consensus what should be done about ErrMsg?

@neutaaaaan
Copy link
Collaborator

Just had a glance at it.

To me, Error and ErrMsg should have pure black text, and if possible a slightly brighter shade of red.
I'll play around with it this weekend.

@romainl
Copy link
Collaborator

romainl commented Dec 14, 2024

I agree with @neutaaaaan's pure black suggestion.

@k-37
Copy link
Author

k-37 commented Dec 15, 2024

Hi @neutaaaaan,

thank you for your suggestions.

Here it is.

GUI

gui_241215_sample_messages

256

256_241215_sample_messages

16

16_241215_sample_messages

@romainl
Copy link
Collaborator

romainl commented Dec 16, 2024

I don't see any issue anymore. @habamax? @neutaaaaan?

@habamax
Copy link
Collaborator

habamax commented Dec 16, 2024

Looks ok.

And as it is based on habamax, I would also "fix" #267 by adding PopupSelected link to PMenuSel.

@neutaaaaan
Copy link
Collaborator

I'm not crazy about the shade of cyan used for Special in 256c, but I haven't found a replacement that didn't clash with Statement.

As it's based on habamax, I figure it's robust enough, but I'd rather spend another week or so using it at work before really giving it my full approval.

@k-37
Copy link
Author

k-37 commented Dec 17, 2024

And as it is based on habamax, I would also "fix" #267 by adding PopupSelected link to PMenuSel.

Link PopupSelected -> PmenuSel already exists.

@habamax
Copy link
Collaborator

habamax commented Dec 17, 2024

Link PopupSelected -> PmenuSel already exists.

oh, that is great!

@k-37
Copy link
Author

k-37 commented Dec 17, 2024

unokai is not just habamax with different color pallete, some other small changes were made.

Here is written all colorschemes must have the same features. What is considered feature of colorscheme?

Should this be removed:

;;; Syntax
Variant: 8
htmlBold                     color07        none           bold
htmlItalic                   color07        none           underline
Variant: gui 256 16
htmlBold                     color15        none           bold
Variant: 256 16
htmlItalic                   color15        none           underline
Variant: gui
htmlItalic                   color15        none           italic

Variant: 8
markdownHeadingDelimiter     color07        none
markdownH1Delimiter          color01        none
markdownH2Delimiter          color03        none
markdownH4Delimiter          color04        none
markdownH6Delimiter          color02        none
Variant: gui 256 16
markdownHeadingDelimiter     color15        none
markdownH1Delimiter          color09        none
markdownH2Delimiter          color11        none
markdownH4Delimiter          color12        none
markdownH6Delimiter          color10        none
Variant: gui 256 16 8
markdownH3Delimiter          color03        none
markdownH5Delimiter          color04        none

@romainl
Copy link
Collaborator

romainl commented Dec 17, 2024

Here is written all colorschemes must have the same features. What is considered feature of colorscheme?

Sorry, that sentence should have been more precise, something like:

all colorschemes must have the same level of support for for the same core features

With "core features" referring to all the documented hl-something highlight groups. The goal is to provide the same basic level of functionality to every user. Whatever you can do in $BUNDLED_COLORSCHEME, you can do it just as well in any other $BUNDLED_COLORSCHEME and you can base your choice on other criteria like your own taste, lighting condition, display, etc.

@habamax
Copy link
Collaborator

habamax commented Dec 17, 2024

vimrc looks too "red" with unokai, should preproc use other color or this is by design?

image

@habamax
Copy link
Collaborator

habamax commented Dec 17, 2024

Looks like most vim monokai colorschemes do the same

@k-37
Copy link
Author

k-37 commented Dec 18, 2024

That is by design.

@neutaaaaan
Copy link
Collaborator

After about a week of using the 256c version ofunokai at work I haven't noticed any real issues with it, and the minor gripes I have stem from choices made by the original author of monokai.

I trust @habamax and @romainl will have more thoroughly checked and tested the various templates.

As for the question about rewiring groups, we don't allow for anything that targets specific plugins or third party syntax files but anything that ships with vim is fair game, as long as things are semantically coherent, or are good faith attempts at resolving semantic conflicts caused by the design of the original colorscheme.

@romainl
Copy link
Collaborator

romainl commented Dec 30, 2024

Thank you @k-37, I think we can merge this PR as-is.

@habamax, @neutaaaaan, @chrisbra, do you think we should make a PR to the main repo right away? Or should we wait until we have n more colorschemes/fixes and do a batch?

@chrisbra
Copy link
Member

I don't mind, whatever works best for you

@neutaaaaan
Copy link
Collaborator

We might as well PR unokai right away, there's no telling when other colorschemes will be ready to be PRed as well.

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 this pull request may close these issues.

5 participants