Feat/112 ls colors parser - #218
Merged
Merged
Conversation
Adds a built-in ls_colors parser that recognizes LS_COLORS / SGR color-producing snippets such as =38;5;NNN, =48;5;NNN, =38;2;R;G;B, and =48;2;R;G;B (leading style codes like 01; are skipped). The parser is byte-dispatched on '=' and disabled by default. Exposes the xterm 256-color palette so custom parsers and downstream code do not need to duplicate it: - colorizer.parser.xterm.lookup_256(idx) -> rgb_hex|nil - colorizer.parser.xterm.get_palette() -> fresh 256-entry copy Wires the parser through registry, config annotations, matcher flags and cache key, README, vimdoc, and adds focused parser/registry tests.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.