-
Notifications
You must be signed in to change notification settings - Fork 81
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
Add to official base16 scheme list #27
Add to official base16 scheme list #27
Comments
I'm not sure we would be allowed since this repo doesn't actually follow some of their guidelines. The repo name and the fact we don't look at the terminals 16 colours are the main areas we break their guidelines. |
Is this something you intend to work towards? Otherwise, would forking be acceptable? |
I'm open to PRs to add 16 terminal colour support, it would actually fix the other issue in this repo #18. I'm a bit busy right now with personal life and moving so I won't have time to implement this but near the end of november things should clear up and I can try to implement the changes. I'd be open to renaming this repo to base16-nvim to match the style guide from base 16. |
@RRethy: I believe GitHub will still redirect from old link so changing repository name should be painless. At least that was the case for one of plugins I was using that also changed name. More info: https://docs.github.com/en/repositories/creating-and-managing-repositories/renaming-a-repository |
Yup, renaming isn't a issue, the main issue is the 16 terminal colour support to make it eligible for that scheme list. This isn't super high on my priority list because most people (including myself) just use true colours. |
Hi,
If it's not already in the plans, consider adding this to the list of schemes.
Nice work!
The text was updated successfully, but these errors were encountered: