Tags colorize support #100
Closed
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
nazar-pc
force-pushed
the
tags-colorize-support
branch
2 times, most recently
from
7120c3c
to
6789c35
Compare
nazar-pc
force-pushed
the
tags-colorize-support
branch
from
ede7c32
to
0aee25f
Compare
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.
This is implementation of what I was talking in #96
Essentially, allows using HTML-like formatting:
in addition to less convenient (current syntax)
It is much easier to read, write and maintain. Please, refer to #96 for discussion.
Nothing is removed and/or deprecated, unless you're using
<g>and similar tags for whatever reason in CLI output, it shouldn't introduce any backward compatibility problems.Fixes #96.