change TERM to xterm #56
Conversation
|
The million dollar question is: But will it break something else? |
|
A safer option might be: screen-16color, or similar. |
|
I've left it as xterm for a few days now and everything seems to be ok. I'll maybe play with 'screen-16color', I've also seen 'cygwin' suggested. |
|
@MrException I don't know a lot about Linux but I had been manually setting TERM=linux every time I ssh into my fortrabbit app to avoid problems caused by TERM msys not known. Is it better to use xterm? I changed mine in to xterm in init.bat and it works. Just don't know if all linux distributions have xterm or is linux a generic one that works with all of them? |
|
As far as I know, terminfo describes a terminal to correct your colour output, terminal size, handling of keys, and various pitfalls from legacy hardware. That's why using the wrong one can potentially create strange behaviour. It seems xterm suits cmder fine, though. Reading the files and what they describe of your terminal, however, isn't something I've done. So how xterm differs from 'linux' terminfo entry isn't known to me. If you want, however, you can test by changing your terminfo (listed in /usr/share/terminfo/ in alphabetized folders) and starting a curses or ncurses program. (Such as weechat-curses) and seeing what happens, just to see that it has an effect. |
|
@Vivix thanks for the info. I can't test like that on a fortrabbit ssh session due to limited access to things but will definitely look at my local vagrant dev environment. You guys seem to know which one is best but just a FYI all three linux, xterm, and cygwin seem to work fine for me. Just went ahead and changed mine to cygwin. |
|
when i change term into xterm, then clear comman doesn't more work. Any solution ? |
Changing the TERM environment variable to xterm. This will allow you to ssh into another box and run tmux or screen properly.
This should fix #44 and #50.