[3.13] Term types wrong
[3.13] Term types wrong
Mon, 02/01/2010 - 1:50am
#1
Looks like in the latest version the TERM types have all be capitalised i.e. we now have XTERM rather than xterm etc and thus display breaks.
Mon, 02/01/2010 - 10:16am
#2
That is correct. According to the Telnet Option RFC spec, the values of telnet options are not case sensitive. Here is a quote from RFC 1091 on the TermType telnet option:
Within this string, upper and lower case are considered equivalent.
So servers should recognize a terminal regardless of having it capitalized or not. TeSSH 3.13 switched to the capitalized versions because that is how they are listed in the Assigned Numbers RFC (RFC 1010)
But remember that you can always type over the existing value. The drop-down box just gives the default suggestions. But the text field is editable, so just enter "xterm" in lower case if needed.
Mon, 02/01/2010 - 2:09pm
#3
But remember that you can always type over the existing value. The drop-down box just gives the default suggestions. But the text field is editable, so just enter "xterm" in lower case if needed.
I tried this but encountered a problem... Opened the General Preferences GUI, went into Session -> Emulation, typed "xterm" in the Terminal Type drop down combo box, clicked the Apply button and the text changed back to "XTERM".
Typing anything else, that is not already in the default list, is accepted ok.
Mon, 02/01/2010 - 2:19pm
#4
So servers should recognize a terminal regardless of having it capitalized or not. TeSSH 3.13 switched to the capitalized versions because that is how they are listed in the Assigned Numbers RFC (RFC 1010)
Currently connecting to HP-UX 11, SLES 9/10 and Solaris 10 servers and they all do not like XTERM as a display type. So the RFC may say it can be either way but my 3 main OS's do not like it.
Mon, 02/01/2010 - 5:08pm
#5
Thanks for reporting this. Apparently the combo-box control that I am using is trying to be helpful and is auto-filling/correcting your input based upon the existing entry in the list.
Sad that nobody seems to pay attention to the actual standards these days. Since this change seemed to have broken more than it fixed, I'll change it back to lower case and will also add both upper and lower case values to the drop-down list so the auto-correction won't change what you type.
Wed, 02/03/2010 - 5:42pm
#6
The way I have fixed this in the next version is to add a new option beneath the Terminal Type dropdown preference called "Send lowercase terminal type". This option is ENABLED by default. I just didn't like the idea of duplicating each terminal type with both a lowercase and uppercase value. When you check this option, it will automatically change the case of the values in the Terminal Type drop-down box.
Mon, 02/08/2010 - 3:27am
#7
The way I have fixed this in the next version is to add a new option beneath the Terminal Type dropdown preference called "Send lowercase terminal type". This option is ENABLED by default.
Installed 3.14 and found that on a clean install, with no session imported, it still thinks the TERM is set to XTERM even though the General Settings GUI tells me that it should be "xterm". I had to press the "Set as defaults" button before it set itself properly to what was set in the Settings GUI.
Mon, 02/08/2010 - 10:40am
#8
Just clicking the "Use lowercase for terminal type" option off and on again should have also fixed it. TeSSH doesn't change the value that was stored in your previous session.
Tue, 02/09/2010 - 4:11am
#9
TeSSH doesn't change the value that was stored in your previous session.
Thats the thing... I did not have a previous session and it thought the term type was XTERM (on clean install) even though the GUI said it was lowercase xterm.
Tue, 02/09/2010 - 10:48am
#10
Yep, I see it in the code now. TeSSH is initializing the default terminal type to "XTERM". I'll fix that in the next version.
Copyright © 2024 by 