Skip to content
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

Set TERM environment variable in shell process. #19

Conversation

ian-h-chamberlain
Copy link

Fixes #16. Some shells like fish require the TERM environment variable to be set to
determine whether a terminal emulator has color support, etc. Since DTerm has
support for colors, set the value to xterm-256color for maximum support.

I have not actually been able to get color working correctly from fish yet, but this at least silences the warning at the beginning of the prompt and should improve support from other commands that look for $TERM in their environment. If I am able to improve color support more I will open another PR.

Some shells like `fish` require the TERM environment variable to be set to
determine whether a terminal emulator has color support, etc. Since DTerm has
support for colors, set the value to `xterm-256color` for maximum support.
@gensth
Copy link

gensth commented Jul 10, 2020

This fix might also help when dterm is calling a shell script which uses the tput command (which also requires a set $TERM variable, e.g.: set -eu; green=$(tput setaf 10)).
Looking forward for a release. Thanks for all your efforts and energy you put into this great tool.

ethanliu added a commit to ethanliu/dterm that referenced this pull request Nov 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fish: TERM environment variable not set
2 participants