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.

Sign up for GitHub

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

Jump to bottom

Thoughts on forcing $TERM string #32

Open
ghost opened this issue Feb 9, 2014 · 1 comment
Open

Thoughts on forcing $TERM string #32

ghost opened this issue Feb 9, 2014 · 1 comment

Comments

@ghost
Copy link

ghost commented Feb 9, 2014

According to http://blog.sanctum.geek.nz/term-strings/, forcing a $TERM string can cause unexpected results. Hoping to open a conversation about any noticeable instances where this has caused problems.
iamnewton referenced this issue Feb 9, 2014
@necolas
shell: minor tidy up of bash_profile
b866ad8
@iamnewton
Copy link

First off let me just say, I assume the reason for forcing the $TERM string is to get 256 colors. If there is any other reason, I'm curious to know.

Second, I've shied away from implementing this as I haven't found any term clients that don't support 256 colors. Do you have any?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@iamnewton