Support notermguicolors #35
Merged
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
Use Normal bg and add cterm underline
|
Sorry for the long wait!
|
|
This looks absolutely fantastic, @spenserblack鈥攖hank you for your hard work! |
|
These changes have been released to npm in |
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.
Resolves #34
termguicolors(might be fixed by above)Looks like most syntax highlighting works, but the background still needs some work. It's way lighter than it should be. Also looks like some misspelled strings are getting highlighted differently between the two.
Most of this was done with a macro, but it looks like I'll need to do some coding myself 馃槅
termguicolorsset on top, not set on bottom