Closed erlandsona closed 9 months ago
I read this about 5 times and I'm still confused tbh, if I had to guess it's probably a duplicate of #18.
Yeh tough to strike the right balance between context and content. Thanks for the link to the cterm stuff... It seems the same but tbh even after 10yrs running Neovim and I still don't understand what termguicolors is supposed to do? 😅
Which means I also have no idea what cterm vs GUI stuff is related to why Neovim is such a pain to get it to read my terminal configured colors 🤷
So my issue is the base16-default-dark/light themes have hard coded hex values.
Helix has base16_default & base16_terminal themes that pull from whatever the configured terminal 16 colors are and does a really nice job of matching the aesthetic well.
I've been running a custom lush.nvim theme for a while now but just installed some new plugins and figuring out the new highlight groups / links etc... is a massive pain.
What would be really nice is if I could get the equivalent Helix mapping of terminal 16 colors (background,foreground + ansi + brights) into Neovim.
I've tried naively mapping my wezterm colors into the 16 colors in the custom setup method like so .wezterm.lua
You see the issue here right? The way Terminals expect you to specify colors doesn't match the way base16's styleguide suggests you specify colors.
Which means using this library even if I try to follow the style guide leaves me with inconsistencies a lack of shades for different hues.
Curious if / how people have resolved this in the past?