community 
What is XTERM mode?
In computing, xterm is the standard terminal emulator for the X Window System. A user can have many different invocations of xterm running at once on the same display, each of which provides independent input/output for the process running in it (normally the process is a Unix shell).
xterm originated prior to the X Window System. It was originally written as a stand-alone terminal emulator for the VAXStation 100 (VS100) by Mark Vandevoorde, a student of Jim Gettys, in the summer of 1984, when work on X started. It rapidly became clear that it would be more useful as part of X than as a standalone program, so it was retargeted to X. As Gettys tells the story, "part of why xterm's internals are so horrifying is that it was originally intended that a single process be able to drive multiple VS100 displays."[2]
After many years as part of the X reference implementation, around 1996 the main line of development then shifted to XFree86 (which itself forked from X11R6.3), and it is presently actively maintained byThomas Dickey.
Many xterm variants are also available.[3] Most terminal emulators for X started as variations on xterm.
https://en.wikipedia.org/wiki/Xterm
How can this help in Studio?
Sometimes when we run the same telnet command from Studio and putty, the output could have a different structures.
Studio:
03/31/2014 12:34 PM
<DIR> .
03/31/2014 12:34 PM
<DIR> ..
03/31/2014 10:46 AM
<DIR> Contacts
04/30/2014 01:01 PM
<DIR> Desktop
05/05/2014 09:43 AM
<DIR> Documents
05/05/2014 07:41 AM
<DIR> Downloads
Putty:
03/31/2014 12:34 PM <DIR> .
03/31/2014 12:34 PM <DIR> ..
03/31/2014 10:46 AM <DIR> Contacts
04/30/2014 01:01 PM <DIR> Desktop
05/05/2014 09:43 AM <DIR> Documents
05/05/2014 07:41 AM <DIR> Downloads
Setting the Studio telnet client to work in XTERM mode may solve the issue. In order to do so, the attached test, developed on TestShell 5.1 patch 3 will apply the following key to customer.config and QsDllHost.config.exe in the Studio\Runner\Runtime\Server\Driver Builder folders.
<add key="TelnetTerminalType" value="xterm"/>
Since 6.2.3, you can set the terminal type in the set session itself.
The key mentioned above is still valid and will set the default behavior, but if you need to control the terminal type per device/session then using the session settings is what you need to use.
When you open the "more settings" area or the set session step, you'll see this marked field. This is a text field that gets the values as the key does (for example, vt100,xterm..). If it kept empty, it will take the value from the mentioned key. When the key is not set, the default is vt100.
About the key, there is also one that sets the default ssh terminal type: <add key="SSHTerminalType" value="xterm"/>
Contributors
