This repository has been archived by the owner on Dec 16, 2023. It is now read-only.
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.
Fixes #13
Result:
IMPORTANT NOTICE:
The order of the colors doesn't match the typical base16 color order. This is a deliberate decision to remain as close as possible to the semantic meaning of the Everforest colors, where functions are green, keywords red, strings aqua, constants purple, etc.
Base16 doesn't mandate that themes adopt red for keywords, orange for constants, etc. In fact, there are multiple base16 themes which color order doesn't match the default theme. However, I also know that the original base16 spec has a few flaws — such as "variables AND diff deleted MUST always be the same color" — so if you want me to stay more conservative regarding base16 semantics, and swap the colors like one of the two alternatives below, just let me know!
alt1 (strings and functions retain the Everforest semantics)
alt2 (nothing retains the Everforest semantics)