|
WSupported on Windows
|
USupported on Unix
|
VSupported on OpenVMS
|
NSupported in Synergy .NET
|
The DTKTERM environment variable defines the key map’s terminal type, identifying the key map to use.
Value
The type of terminal you are using. This can be a user-defined name for a key map that you’ve created or one of the following distributed key maps:
|
ansi |
Unix console |
|
generic |
Unknown terminal type |
|
hft |
IBM high-function terminal |
|
ibmpc |
PC |
|
mswindows |
Windows |
|
vt100 |
VTxxx terminal |
|
wy60 |
Wyse-60 and compatibles |
|
xterm |
X-Windows terminals |
Discussion
A key map file contains key maps for one or more terminal types. When you install Synergy/DE, you assign your default terminal type to the DTKTERM environment variable. Then, when the U_START subroutine initializes the window system, it opens the key map file and loads the key map for the terminal type defined in DTKTERM.
If DTKTERM is not set, the value of TERM is used instead.
|
Although DTKTERM is ignored for .NET development, it does work for .NET terminal applications (Windows and Linux). However, since ibmpc and mswindows don’t work the same way with .NET terminal applications as they do with traditional Synergy programs on Windows, we recommend setting DTKTERM to vt100 for terminal applications (if you set DTKTERM at all). |
Setting location
The environment. On Windows, this environment variable can also be set in the [synergy], [dbr], or [myprog] section of synergy.ini (where myprog is any .dbr file).
Used by
UI Toolkit, Repository, ReportWriter
See also
Customizing key mapping for menu shortcuts for more information about terminal types
Examples
On Unix,
DTKTERM=ansi ;export DTKTERM
