New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a value for TERM_PROGRAM
in the environment
#200
Comments
Hey there @davep , thank you for the issue. I took a look in some terminals that have it enabled couldn't find in kitty neither alacritty but terminal.app does have it. Would you mind list others that support it? |
Sorry, yeah, the wording wasn't great there (and for some reason I thought Alacritty did, but I'm misremembering). I guess the more general question here is, would you entertain the idea of having something in the environment (either like The motivation for this is I'm part of a team that works on a library for building terminal-based applications and often issues that developers run in to are related to terminal differences and glitches; so being able to identify the terminal in use from our environment diagnosis report makes it easier to get to the bottom of this. Obviously not the most crucial of requests, but very convenient to getting to the bottom of issues. |
Perfect! Thanks. Our environment report now shows: ## Terminal
| Name | Value |
|----------------------|----------------|
| Terminal Application | rio (0.0.18) |
| TERM | xterm-256color |
| COLORTERM | truecolor |
| FORCE_COLOR | *Not set* |
| NO_COLOR | *Not set* | Spot on. :-) |
Great! Thank you for checking it |
cc @raphamorim Just |
It's common for terminals to set the
TERM_PROGRAM
environment variable to something that identifies the terminal; this can be a handy diagnostic for those of us who develop code that runs inside terminals. Would you consider adding this to rio so that it identifies itself?Also not uncommon is
TERM_PROGRAM_VERSION
for the version number.The text was updated successfully, but these errors were encountered: