馃馃拕 Auto-highlight parse error detailed_message using TERM and FORCE_COLOR - #607
Merged
nevans merged 1 commit intoFeb 13, 2026
Merged
Conversation
Highlighting will be used when either: * `ENV["TERM"]` is set, and not empty, "dumb", or "unknown" * `ENV["FORCE_COLOR"]` is set, and not empty, or "0" I originally checked `$stderr.tty?`, but I think that, in this case, using ENV vars is both simpler and better.
nevans
changed the title
TERM and FORCE_COLOR env varsTERM and FORCE_COLOR env vars
nevans
changed the title
TERM and FORCE_COLOR env varsTERM and FORCE_COLOR
nevans
deleted the
response_parse_error-detailed_message-default-highlights
branch
February 13, 2026 14:06
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.
Highlighting will be used when either:
ENV["TERM"]is set, and not empty, "dumb", or "unknown"ENV["FORCE_COLOR"]is set, and not empty, or "0"I originally checked
$stderr.tty?, but I think that, in this case, using ENV vars is both simpler and better.