resolarized.nvim VS boilit

Shameless plug: my own implementation of Solarized, resolarized.nvim, supports undercurl. In fact, undercurl support was present from day one, I just could not see it until now.

I have my own implementation of Solarized if you want to take a look. It uses a table to define the palette and then a tree-like table that lets me specify the highlight groups in such a way that groups can inherit properties from other groups. It makes it very easy to add more groups later. https://gitlab.com/HiPhish/resolarized.nvim

I wrote my own version of Solarized a while ago: https://gitlab.com/HiPhish/resolarized.nvim

Might as well plug my own implementation of Solarized. It does support LSP and Treesitter in the bare sense that those groups are defined, but they have standard highlighting.

I understand and share OPs frustration and I have tried to keep things as simple as possible in my implementation of Solarized out of pure frustration. IMO there are two things to consider:

Last but not the least: I wrote boilit, a boilerplate template for neovim plugins. Don't take it for golden, it's an old attempt of time to create seemingly general boilerplate structures as skeleton for my work, and some people found it useful too. Have a look, try it out but don't shoot the messenger if it isn't up-to-date with the latest neovim goodies :p

Checkout boilit :)

A good starting point can be boilit :)

Have a look at boilit.

Are you asking how to organise plugin structures so that the exposed interfaces may load configuration files? If so, boilit may provide some guidance.

boilit may be of initial help (though it doesn't answer your question in full, however it drafts what's needed to develop a plugin locally)

It looks good! I too wrote a similar project some time ago (in Go though): boilit :-)

I have created the fix here: feel free to have a look and check.