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

Fix tinted-theming/base16-vim support due to rename #1346

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

josswright
Copy link

The support for tinted-theming/base16-vim was broken because tinted-theming have renamed that repository to tinted-theming/tinted-vim.

Most importantly, the internal variables for their base16 colorschemes have changed from base16_gui* to tinted_gui*, which meant that lualine's checking functions had stopped working.

This fixes the tinted-theming/tinted-vim detection, renames the setup function to setup_tinted_vim(), and fixes the link in the THEMES.md documentation to point to the new repository name.

The `tinted-theming/base16-vim` repository has been renamed to
`tinted-theming/tinted-vim`, and the internal colour names have been
renamed from `base16_gui*` to `tinted_gui*`. This caused Lualine to
print a warning error when using tinted-vim.

This pull updates the colour names to what `tinted-theming`now uses.
I've also renamed the `setup_base16_vim()` function to
`setup_tinted_vim()` for consistency.
Updated `THEMES.md` to refer to `tinted-theming/tinted-vim` rather than
the older name of `tinted-theming/base16-vim` (which now silently
redirects to `tinted-theming/tinted-vim`).
@JamyGolden
Copy link
Contributor

I mentioned in a duplicate PR:

I've just merged a PR into tinted-vim which adds the legacy vim.g.base16_gui0X variables back. So while we're waiting for the maintainers here to merge the changes, things should be working if you use the latest tinted-vim: tinted-theming/tinted-vim#100

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.

2 participants