-
-
Notifications
You must be signed in to change notification settings - Fork 275
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
FR: snacks.picker support #823
Comments
@mikededo Could you help here? You were so kind to introduce the |
If it helps in any way, I have been able to fix the look by adding the following custom highlight: NormalFloat = { bg = colors.base, fg = colors.text }, |
Hey @SebastianBalle, the only issue at the moment with At the same time, there's extra configuration to be done in order to make a picker look the way you want. For example, in my case, here's how my picker looks: ![]() While I had to customize some highlights in |
I've been looking into the generated highlights from Snacks highlights (152 highlights, if I counted right)
We'd have to define which should be modified, for example, if a highlight does not match what's expected. For example, the default picker highlights look like this: ![]() I agree with @uroybd that it looks really bad. While we can work on updating the colors, we cannot update the layout, since it's out of the scope of the plugin. |
@mikededo I believe adopting |
@mikededo any progress here? I liked you idea 👍 |
Pretty much the title. Currently, Catppuccin has snacks.nvim diagnostic support. However, the new picker looks ugly since it is not supported.
The text was updated successfully, but these errors were encountered: