Add legacy variables for plugins that don't supported tinted-vim yet #100
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JamyGolden
requested review from
belak and
GordianDziwis
and removed request for
a team
GordianDziwis
approved these changes
Jan 3, 2025
JamyGolden
force-pushed
the
jamy/bugfix/base16-gui-vars
branch
from
fac465f to
cf7abf2
Compare
This was referenced Jan 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
lualine uses the
vim.g.base16_gui0Xvariables and doesn't yet support thevim.g.tinted_gui0Xvariables. I've created a PR on lualine but they may take a while to merge the PR: nvim-lualine/lualine.nvim#1357Checklist
./colors/*.vimin a separate commit and followed the build instructions