![]() Normally these bindings do not conflict with the use of the Meta key as described for theĮightBitInput resource. PC-style bindings are analogous to PCTerm, but not the same thing. Use the Shift, Alt, Control and Meta keys as modifiers for function-keys and keypad (see the document Xterm Control Sequences for details). SunKeyboard set to false), xterm uses PC-style bindings for the function keys and keypad. so xterm emulates a DEC VT220 more accurately. and CTRL F1-F12 toį11-F20, depending on the setting of the ctrlFKeys resource. This causes the keypad '+' to be mapped to ','. Specifies whether or not Sun/PC keyboard layout should be assumed rather than DEC VT220. Specifies whether or not Sun Function Key escape codes should be generated for function keys instead of standard escape sequences. If the value of this resource is true, xterm sets up session manager callbacks for XtNdieCallback and XtNsaveCallback. Specifies whether or not SCP Function Key escape codes should be generated for function keys instead of standard escape sequences. In practice this should never be a problem. This has the advantage of preventing flicker and the disadvantage of requiring an extra round trip to the server to find out the previous If the value of this resource is true, xterm does not send title and icon name change requests when the request would have no effect: the name In either case, the result is applied to the TERMCAP Its own configuration, using the kb string from the termcap entry as a reference, if available. If false, xterm will set the stty erase value to match ![]() If true, xterm will use the pseudo- terminal's sense of the stty erase value. If true, xterm will perform handshaking during initialization to ensure that the parent and child processes update the utmp and Specify the minimum size of the input buffer, i.e., the amount of data that xterm requests on each read. Specifies whether write access to the terminal is allowed initially. MaxBufSize and minBufSize resource values to achieve better performance if the operating system prefers larger buffer sizes. On some systems you may want to increase one or both of the Increased as needed to make that value evenly divide this one. You cannot set this to a value less than the minBufSize resource. Specify the maximum size of the input buffer. The individual resources are provided for legacy support this resource The resource's value should be one of the corresponding strings hp, sco, sun or vt220. The default is the application name.Įnables one (or none) of the various keyboard-type resources: hpFunctionKeys, scoFunctionKeys, sunFunctionKeys and sunKeyboard. It is not necessarily obeyed by all window managers. Specifies the preferred size and position of the application when iconified. Specifies whether or not HP Function Key escape codes should be generated for function keys instead of standard escape sequences. Resizing the display will lose data, however, since this involves interaction with the shell which is no longer running. You may scroll back, select text, etc., to perform most It will wait until you use the window manager toĭestroy/kill the window, or if you use the menu entries that send a signal, e.g., HUP or KILL. If true, xterm will not immediately destroy its window when the shell command completes. The default is false, which disables this feature. Tie the VTxxx backarrowKey and ptyInitialErase resources together by setting the DECBKM state according to whether the initial value of sttyĮrase is a backspace (8) or delete (127) character. NAME") follow:īackarrowKeyIsErase (class BackarrowKeyIsErase) The program understands all of the core X Toolkit resource names and classes.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |