Skip to content

🥅💄 Auto-highlight parse error detailed_message using TERM and FORCE_COLOR - #607

Merged
nevans merged 1 commit into
masterfrom
response_parse_error-detailed_message-default-highlights
Feb 13, 2026
Merged

🥅💄 Auto-highlight parse error detailed_message using TERM and FORCE_COLOR#607
nevans merged 1 commit into
masterfrom
response_parse_error-detailed_message-default-highlights

Conversation

@nevans

@nevans nevans commented Feb 13, 2026

Copy link
Copy Markdown
Collaborator

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.

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 nevans added the enhancement New feature or request label Feb 13, 2026
@nevans nevans changed the title 🥅💄 Auto-highlight parse error based on TERM and FORCE_COLOR env vars Feb 13, 2026
@nevans nevans changed the title 🥅💄 Auto-highlight parse error detailed_message based on TERM and FORCE_COLOR env vars Feb 13, 2026
@nevans
nevans merged commit 573a591 into master Feb 13, 2026
39 checks passed
@nevans
nevans deleted the response_parse_error-detailed_message-default-highlights branch February 13, 2026 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

1 participant