Back to product page

TerminalEmulation property


Determines emulation codes to be sent to the client.

Type

A TerminalEmulationsEnum enumeration.

Syntax

  • Basic
object.TerminalEmulation [= value]  
The TerminalEmulation(object,value) syntax has these parts:
objectAn expression evaluating to an object of type wodSSHD.
valueA TerminalEmulationsEnum enumeration, as described in settings.

Remarks

The settings for value are:

Constant Value Description
NoEmulation0 No emulation codes are sent.
VT100Emulation 1 VT100 emulation codes are sent.
CommandLineEmulation2 Command line codes are sent.


This property holds default value for all new connections. You can also change TerminalEmulation on per-user basis.

When client connects to your SSH server using console access (such as command-line telnet, Putty, CRT or other apps), he receives command prompt and can type commands to his console - just as if he would actually sit in front of the keyboard on your PC.

However, certain commands are needed to be sent to the client while he executes commands - such as codes to clear screen, to move cursor, etc.. wodSSHServer prior to 2.0.0 were unable to send such codes to the client, but now you can set TerminalEmulation property to VT100 and clients will have FULL experience of console access - including cursor movements, colors, graphics, etc.. You can run 'edit.exe', 'ftp.exe' and other command-line applications normally.

For easier typing of commands in command line you can use CommandLineEmulation. CommandLineEmulation emulates common keys that are used in command-line mode. Such as intercepting delete, backspace, up/down/left/right and other.

If he sets this property to NoEmulation, then wodSSHServer behaves as before, does not send any ANSI sequences.

Platforms

Windows