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

BREAKING CHANGE: gruvbox is now a single module #280

Merged
merged 2 commits into from Sep 30, 2023
Merged

Conversation

ellisonleao
Copy link
Owner

@ellisonleao ellisonleao commented Sep 29, 2023

palette: Can now be accessed in the main module through require('gruvbox').palette
get_base_colors: now a internal function called get_colors. If you want to get the colors, just get the palette directly
groups: now moved to main module
diffs: fixing diff highlights for multiple plugins

palette: Can now be accessed in the main module through `require('gruvbox').palette`
get_base_colors: now a internal function called get_colors. If you want
to get the colors, just get the palette directly
groups: now moved to main module
@ellisonleao ellisonleao merged commit 59c3dc8 into main Sep 30, 2023
6 checks passed
@ellisonleao ellisonleao deleted the single-module branch September 30, 2023 22:34

```lua
{ "ellisonleao/gruvbox.nvim", priority = 1000 }
{ "ellisonleao/gruvbox.nvim", priority = 1000 , setup = true, opts = ...}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There doesn't seem to be a setup property, seems you meant to use config instead. Also that would be unnecessary as setting opts "will imply Plugin.config()".

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@polyzen actualy it's a typo, using config with opts will basically call require('gruvbox').setup(opts). Will fix it

ambroisie added a commit to ambroisie/nix-config that referenced this pull request Oct 26, 2023
I dislike the new style of diff [1].

After somebody wrote a patch [2] I finally started experimenting with
what looked best to me.

This is using the old vibrant colours, which I like better. And avoids
using `reverse = true` to not break high-lighting during visual
selection.

This is using an overlay as it is _much_ easier to refer to the internal
colours in a `dark`/`light` agnostic way that way instead of the
intended "use the palette way" (due to breaking changes in [3] which,
incidentally, is the MR which changed diff high-lighting).

[1]: ellisonleao/gruvbox.nvim#290
[2]: ellisonleao/gruvbox.nvim#291
[3]: ellisonleao/gruvbox.nvim#280
@ambroisie
Copy link

It's kind of annoying to have to use palette instead of get_colors, as it means the end-user has to re-implement the light/dark logic themselves.

@darkangel-ua
Copy link
Contributor

Moreover user has to deal not only with light/dark but also with contrast stuff because contrast is passed to setup which makes all this thing even worse and recursive...

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.

None yet

4 participants