Back to product page
- Introduction
- Overview
- License Agrement
- Getting Started
- Objects
- Enumerations
- wodSSH
- Methods
- Properties
- AllocatePty
- Authentication
- Blocking
- ClientName
- Columns
- Command
- Compression
- DataOut
- DataReady
- Encoding
- Encryption
- EncryptionList
- ErrorText
- ExitSignal
- ExitStatus
- FIPS
- ForwardHost
- ForwardPort
- HMacList
- Hostname
- KeepAlives
- KeyExchangeList
- KeyForward
- KeySignatureList
- LastError
- Login
- MyHostname
- MyIP
- Notification
- Password
- Port
- PrivateKey
- Prompt
- Protocol
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- RemoteIdentification
- Rows
- ShowStdErrorMessages
- State
- StateText
- StripANSI
- StripNull
- Subsystem
- TerminalSpeed
- TerminalType
- Timeout
- UseIPv6
- Version
- Events
- IwodSSHNotify
- How to get support?
- Technical information
- Fast notifications interface
- Error list
TerminalType property
Selects the terminal type that is reported to the server.
Type
A String value. Determines terminal type reported to the server.Syntax
- Basic
object.TerminalType [= value]
The TerminalType(object,value) syntax has these parts:
The TerminalType(object,value) syntax has these parts:
object | An expression evaluating to an object of type wodSSH. |
value | A String value. |
Remarks
Telnet and SSH protocol specifications define that clients should identify the emulation that will be used with the connection. Most commonly, if a client is able to handle cursor-movements and similar console actions it should implement 'vt100' emulation. Almost all servers support vt100, so this is used as the default value.Note that in wodSSH, the terminal type does not really have any affect on the local side - because there is no GUI. However, changing it from 'vt100' to something else may cause the server to send different data. For example, you can stop it from sending ANSI escape sequences since you don't really need them.