Essa fonte deve ter a mesma altura e largura da fonte normal, caso contrário, será ignorada. Se apenas uma das fontes normais ou em negrito for especificada, ela será usada como a fonte normal e a fonte em negrito será produzida pela sobreposição dessa fonte.

Veja também a discussão de boldMode e alwaysBoldMode recursos.

See also the renderFont resource, which combines with this to determine whether FreeType fonts are initially active.

See also the iconFont resource.

See also the discussion of the ximFont resource.

The value “unknown“, causes the corresponding resource to be ignored.

The value “default“, suppresses the associated resources hpFunctionKeys, scoFunctionKeys, sunFunctionKeys, tcapFunctionKeys and sunKeyboard, using the Sun/PC keyboard layout.

XtermLog.XXXXXX

or

Xterm.log.hostname.yyyy.mm.dd.hh.mm.ss.XXXXXX

…depending on how xterm was built.

The actual list of encodings that are supported is determined by luit. Consult the luit manual page for further details.

See also the -u8 option which supports UTF-8 locales.

The -ls flag and the loginShell resource are ignored if -e is also given, because xterm does not know how to make the shell start the given command after whatever it does when it is a login shell; the user’s shell of choice need not be a Bourne shell after all. Also, xterm -e is supposed to provide a consistent functionality for other applications that need to start text-mode programs in a window, and if loginShell were not ignored, the result of ~/.profile might interfere with that.

If you do want the effect of -ls and -e simultaneously, you may use something like

xterm -e /bin/bash -l -c "my command here"

Finally, -ls is not completely ignored, because xterm -ls -e does write a /var/log/wtmp entry (if configured to do so), whereas xterm -e does not.

Maximizing is not the reverse of iconifying; it is possible to do both with certain window managers.

This option and the utf8 resource are overridden by the -lc and -en options and locale resource. That is, if xterm has been compiled to support luit, and the locale resource is not “false” this option is ignored. We recommend using the -lc option or the “locale: true” resource in UTF-8 locales when your operating system supports locale, or -en UTF-8 option or the “locale: UTF-8” resource when your operating system does not support locale.

-S/dev/pts/123/45
-S123/45
-Sab34

Note that xterm does not close any file descriptor which it did not open for its own use. It is possible (though probably not portable) to have an application which passes an open file descriptor down to xterm past the initialization or the -S option to a process running in the xterm.

This appears to be a legacy of older X releases. It sets the borderWidth resource of the shell widget, and may provide advice to your window manager to set the thickness of the window frame. Most window managers do not use this information. See the -b option, which controls the inner border of the xterm window.

The default is “false“.

The default is “unknown“, i.e., none of the associated resources are set via this resource.

On some systems you may want to increase one or both of the maxBufSize and minBufSize resource values to achieve better performance if the operating system prefers larger buffer sizes.

To use the current locale (only useful if you have localized the resource settings for the menu entries), set the resource to an empty string.

See also waitForMap which waits for the pseudo-terminal’s notion of the screen size, and ptySttySize which resets the screen size after other terminal initialization is complete. The default is “true“.

See also the ttyModes resource, which may modify this. The default is “false“.

See also waitForMap which waits for a handshake-message giving the pseudo-terminal’s notion of the screen size. The default is “false” on Linux and OS X systems, “true” otherwise.

While this resource applies to either bitmap or TrueType fonts, its main purpose is to help work around incompatible changes in the Xft library’s font metrics. Xterm checks the font metrics to find what the library claims are the bounding boxes for each glyph (character). However, some of Xft‘s features (such as the autohinter) can cause the glyphs to be scaled larger than the bounding boxes, and be partly overwritten by the next row.

See useClipping for a related resource.

See also the keyboardType resource.

See also the keyboardType resource.

PC-style bindings use the Shift, Alt, Control and Meta keys as modifiers for function-keys and keypad. The PC-style bindings are analogous to PCTerm, but not the same thing. Normally these bindings do not conflict with the use of the Meta key as described for the eightBitInput resource. If they do, note that the PC-style bindings are evaluated first.

See also the keyboardType resource.

See also the keyboardType resource.

This is very useful for overriding the default terminal settings without having to do an stty every time an xterm is started. Note, however, that the stty program on a given host may use different keywords; xterm‘s table is built-in.

If the ttyModes resource specifies a value for erase, that overrides the ptyInitialErase resource setting, i.e., xterm initializes the terminal to match that value.

When this feature is enabled, xterm will sense the state of the Scroll Lock key each time it acquires focus. Pressing the Scroll Lock key toggles xterm‘s internal state, as well as toggling the associated LED. While the Scroll Lock is active, xterm attempts to keep a viewport on the same set of lines. If the current viewport is scrolled past the limit set by the saveLines resource, then Scroll Lock has no further effect.

The reason for setting the default to “false” is to avoid user surprise. This key is generally unused in keyboard configurations, and has not acquired a standard meaning even when it is used in that manner. Consequently, users have assigned it for ad hoc purposes.

A few programs, e.g., vim, use this feature to get an accurate description of the terminal’s capabilities, independent of the termcap/terminfo setting:

1. xterm can tell the querying program how many colors it supports. This is a constant, depending on how it is compiled, typically 16. It does not change if you alter resource settings, e.g., the boldColors resource.

2. xterm can tell the querying program what strings are sent by modified (shift-, control-, alt-) function- and keypad-keys. Reporting control- and alt-modifiers is a feature that relies on the ncurses extended naming.

· If “true“, Alt characters (a character combined with the modifier associated with left/right Alt-keys) are converted into a two- character sequence with the character itself preceded by Esc. This applies as well to function key control sequences, unless xterm sees that Alt is used in your key translations.

· If “false“, Alt characters input from the keyboard cause a shift to 8-bit characters (just like metaSendsEscape). By combining the Alt- and Meta-modifiers, you can create corresponding combinations of Esc-prefix and 8-bit characters. The default is “false“.

xterm provides a menu option for toggling this resource.

As an alternative, setting the allowBoldFonts resource to “false” overrides both the alwaysBoldMode and the boldMode resources.

This font must be the same height and width as the normal font, otherwise it is ignored. If only one of the normal or bold fonts is specified, it will be used as the normal font and the bold font will be produced by overstriking this font.

See also the discussion of boldMode and alwaysBoldMode resources.

Note that xterm has one bold font which you may set explicitly. xterm attempts to derive a bold font for the other font selections (font1 through font6). If it cannot find a bold font, it will use the normal font. In each case (whether the explicit resource or the derived font), if the normal and bold fonts are distinct, this resource has no effect. The default is “true“.

See the alwaysBoldMode resource which can modify the behavior of this resource.

Although xterm attempts to derive a bold font for other font selections, the font server may not cooperate. Since X11R6, bitmap fonts have been scaled. The font server claims to provide the bold font that xterm requests, but the result is not always readable. XFree86 introduced a feature which can be used to suppress the scaling. In the X server’s configuration file (e.g., “/etc/X11/XFree86“), you can add “:unscaled” to the end of the directory specification for the “misc” fonts, which comprise the fixed-pitch fonts that are used by xterm. For example

FontPath "/usr/lib/X11/fonts/misc/"

would become

FontPath "/usr/lib/X11/fonts/misc/:unscaled"

Depending on your configuration, the font server may have its own configuration file. The same “:unscaled” can be added to its configuration file at the end of the directory specification for “misc“.

The bitmap scaling feature is also used by xterm to implement VT102 double-width and double-height characters.

xterm‘s state parser recognizes several types of control strings which can contain text, e.g.,

APC (Application Program Command),

DCS (Device Control String),

OSC (Operating System Command),

PM (Privacy Message), and

SOS (Start of String)

Each should end with a string-terminator (a special character which cannot appear in these strings). Ordinary control characters found within the string are not ignored; they are processed without interfering with the process of accumulating the control string’s content. xterm recognizes these controls in all modes, although some of the functions may be suppressed after parsing the control.

When enabled, this feature allows the user to exit from an unterminated control string when any of these ordinary control characters are found:

control/D (used as an end of file in many shells),

control/H (backspace),

control/I (tab-feed),

control/J (line feed aka newline),

control/K (vertical tab),

control/L (form feed),

control/M (carriage return),

control/N (shift-out),

control/O (shift-in),

control/Q (XOFF),

control/X (cancel)

Resources past color15 are available as a compile-time option. Due to a hardcoded limit in the X libraries on the total number of resources (to 400), the resources for 256-colors are omitted when wide-character support and luit are enabled. Besides inconsistent behavior if only part of the resources were allowed, determining the exact cutoff is difficult, and the X libraries tend to crash if the number of resources exceeds the limit. The color palette is still initialized to the same default values, and can be modified via control sequences.

On the other hand, the resource limit does permit including the entire range for 88-colors.

Setting this resource overrides most of xterm‘s adjustments to cursor color. It will still use reverse-video to disallow some cases, such as a black cursor on a black background.

If the undisplayable text would be double-width, xterm will add a space after the “#” character, to give roughly the same layout on the screen as the original text.

The names are listed below. xterm ignores capitalization, but they are shown in mixed-case for clarity.

The names are listed below. xterm ignores capitalization, but they are shown in mixed-case for clarity.

The names are listed below. xterm ignores capitalization, but they are shown in mixed-case for clarity.

The names are listed below. xterm ignores capitalization, but they are shown in mixed-case for clarity. Where a number can be used as an alternative, it is given after the name.

The metaSendsEscape and altSendsEscape resources may override this feature. Generally keyboards do not have a key labeled “Meta”, but “Alt” keys are common, and they are conventionally used for “Meta”. If they were synonymous, it would have been reasonable to name this resource “altSendsEscape“, reversing its sense. For more background on this, see the meta function in curses.

Note that the Alt key is not necessarily the same as the Meta modifier. xmodmap lists your key modifiers. X defines modifiers for shift, (caps) lock and control, as well as 5 additional modifiers that are generally used to configure key modifiers. xterm inspects the same information to find the modifier associated with either Meta key (left or right), and uses that key as the Meta modifier. It also looks for the NumLock key, to recognize the modifier that is associated with that.

If your xmodmap configuration uses the same keycodes for Alt- and Meta-keys, xterm will only see the Alt-key definitions, since those are tested before Meta-keys. NumLock is tested first. It is important to keep these keys distinct; otherwise some of xterm‘s functionality is not available.

The eightBitInput resource is tested at startup time. If “true“, the xterm tries to put the terminal into 8-bit mode. If “false“, on startup, xterm tries to put the terminal into 7-bit mode. For some configurations this is unsuccessful; failure is ignored. After startup, xterm does not change the terminal between 8-bit and 7-bit mode.

As originally implemented in X11, the resource value did not change after startup. However (since patch #216 in 2006) xterm can modify eightBitInput after startup via a control sequence. The corresponding terminfo capabilities smm (set meta mode) and rmm (reset meta mode) have been recognized by bash for some time. Interestingly enough, bash’s notion of “meta mode” differs from the standard definition (in the terminfo manual), which describes the change to the eighth bit of a character. It happens that bash views “meta mode” as the Esc character that xterm puts before a character when a special meta key is pressed. bash‘s early documentation talks about the Esc character and ignores the eighth bit.

The resource value is a string, evaluated as a boolean after startup.

Except for the never choice, xterm honors the terminfo capabilities smm (set meta mode) and rmm (reset meta mode), allowing the feature to be turned on or off dynamically.

If eightBitMeta is enabled when the locale uses UTF-8, xterm encodes the value as UTF-8 (since patch #183 in 2003).

If not specified, or if there is no match for both normal and bold fonts, xterm uses the bitmap font and related resources.

It is possible to select suitable bitmap fonts using a script such as this:

#!/bin/sh
FONT=`xfontsel -print`
test -n "$FONT" && xfd -fn "$FONT"

However (even though xfd accepts a “-fa” option to denote FreeType fonts), xfontsel has not been similarly extended. As a workaround, you may try

fc-list :scalable=true:spacing=mono: family

to find a list of scalable fixed-pitch fonts which may be used for the faceName resource value.

If the application uses double-wide characters and this resource is not given, xterm will use a scaled version of the font given by faceName.

Although the default is “14.0”, this may not be the same as the pointsize for the default bitmap font, i.e., that assigned with the -fn option, or the font resource. For example, the “fixed” font usually has a pointsize of “8.0”. If you set faceSize to match the size of the bitmap font, then switching between bitmap and TrueType fonts via the font menu gives comparable sizes for the window.

You can specify the pointsize for TrueType fonts selected with the other size-related menu entries such as Medium, Huge, etc., by using one of the following resource values. If you do not specify a value, they default to “0.0”, which causes xterm to use the ratio of font sizes from the corresponding bitmap font resources to obtain a TrueType pointsize.

If all of the faceSize resources are set, then xterm will use this information to determine the next smaller/larger TrueType font for the larger-vt-font() and smaller-vt-font() actions. If any are not set, xterm will use only the areas of the bitmap fonts.

See the discussion of the locale resource, which describes how this font may be overridden.

Note that some resource files use patterns such as

*font: fixed

…which are overly broad, affecting both

xterm.vt100.font

and

xterm.vt100.utf8Fonts.font

…which is probably not what you intended.

The default is “1“.

The fixed-pitch ISO-8859-*-encoded fonts used by xterm normally have the VT100 line-drawing glyphs in cells 1-31. Other fixed-pitch fonts may be more attractive, but lack these glyphs.

When using an ISO-10646-1 font and the wideChars resource is true, xterm uses the Unicode glyphs which match the VT100 line-drawing glyphs.

If “false“, xterm checks for missing glyphs in the font and makes line-drawing characters directly as needed. If “true“, xterm assumes the font does not contain the line-drawing characters, and draws them directly. The default is “false“.

A tabela a seguir mostra a interacção dos recursos destacando, abreviados como se segue:

HCM : highlightColorMode

RH : highlightReverse

HBG : highlightcolor

HFG : highlightTextColor

Dependendo da maneira como seus aplicativos gravam na tela, pode haver espaços em branco à direita em uma linha. O xterm armazena dados como são mostrados na tela. Apagar a exibição altera o estado interno de cada célula para que não seja considerado um espaço em branco para fins de seleção. Os espaços em branco escritos desde a última exclusão são selecionáveis. Se não desejar ter espaços em branco à direita em uma seleção, use o recurso trimSelection .

Regardless of your locale and encoding, you need an ISO-10646-1 font to display the result. Your configuration may not include this font, or locale-support by xterm may not be needed. At startup, xterm uses a mechanism equivalent to the load-vt-fonts(utf8Fonts, Utf8Fonts) action to load font name subresources of the VT100 widget. That is, resource patterns such as “*vt100.utf8Fonts.font” will be loaded, and (if this resource is enabled), override the normal fonts. If no subresources are found, the normal fonts such as “*vt100.font“, etc., are used. The resource files distributed with xterm use ISO-10646-1 fonts, but do not rely on them unless you are using the locale mechanism.

If the encoding converter requires command-line parameters, you can add those after the command, e.g.,

*localeFilter: xterm-filter -p

Alternatively, you may put those parameter within a shell script to execute the converter, and set this resource to point to the shell script.

Here is a summary of the resources which control the choice of wide character width calculation:

Set it to 0 to use the old/obsolete behavior.

Set it to 1 to prefix modified sequences with CSI.

Set it to 2 to force the modifier to be the second parameter if it would otherwise be the first.

Set it to 3 to mark the sequence with a “>” to hint that it is private.

Set it to -1 to permit the user to use shift- and control-modifiers to construct function-key strings using the normal encoding scheme.

Set it to 0 to use the old/obsolete behavior.

Set it to 1 to prefix modified sequences with CSI.

Set it to 2 to force the modifier to be the second parameter if it would otherwise be the first.

Set it to 3 to mark the sequence with a “>” to hint that it is private.

If modifyFunctionKeys is zero, xterm uses Control- and Shift-modifiers to allow the user to construct numbered function-keys beyond the set provided by the keyboard:

As a special case, legacy (when oldFunctionKeys is true) or vt220 (when sunKeyboard is true) keyboards interpret only the Control-modifier when constructing numbered function-keys. This is done to provide compatible keyboards for DEC VT220 and related terminals that implement user-defined keys (UDK).

The default values for on2Clicks and on3Clicks are “word” and “line“, respectively. There is no default value for on4Clicks or on5Clicks, making those inactive. On startup, xterm determines the maximum number of clicks by the onXClicks resource values that are set.

If the window is iconified, this has no effect. However, the zIconBeep resource provides you with the ability to see which iconified windows have sounded a bell.

“0” disables the attributes.

“1” prints the normal set of attributes (bold, underline, inverse and blink) as VT100-style control sequences.

“2” prints ANSI color attributes as well.

The default is “1“.

The default is an empty string, i.e., “”, However, when the print-immediate action is invoked, if the string is empty, then “XTerm” is used.

The default is an empty string, i.e., “”, which disables this feature. However, when the print-on-error action is invoked, if the string is empty, then “XTermError” is used.

These error codes are handled: ERROR_XERROR, ERROR_XIOERROR and ERROR_ICEERROR.

· If zero (0), then this selects the current (visible screen) plus the saved lines, except if the alternate screen is being used. In that case, only the alternate screen is selectd.

· If nonzero, the bits of this resource value (checked in descending order) select the range:

8 selects the saved lines.

4 selects the alternate screen.

2 selects the normal screen.

1 selects the current screen, which can be either the normal or alternate screen.

The default is “9“, which selects the current visible screen plus saved lines, with no special case for the alternated screen.

The default is “9“, which selects the current visible screen plus saved lines, with no special case for the alternated screen.

The resource values are strings, evaluated as booleans after startup.

There are several aspects to reverse video in xterm:

· The command-line -rv option tells the X libraries to reverse the foreground and background colors. xterm‘s command-line options set resource values. In particular, the X Toolkit sets the reverseVideo resource when the -rv option is used.

· If the user has also used command-line options -fg or -bg to set the foreground and background colors, xterm does not see these options directly. Instead, it examines the resource values to reconstruct the command-line options, and determine which of the colors is the user’s intended foreground, etc. Their actual values are irrelevant to the reverse video function; some users prefer the X defaults (black text on a white background), others prefer white text on a black background.

· After startup, the user can toggle the “Enable Reverse Video” menu entry. This exchanges the current foreground and background colors of the VT100 widget, and repaints the screen. Because of the X resource hierarchy, the reverseVideo resource applies to more than the VT100 widget.

Programs running in an xterm can also use control sequences to enable the VT100 reverse video mode. These are independent of the reverseVideo resource and the menu entry. xterm exchanges the current foreground and background colors when drawing text affected by these control sequences.

Other control sequences can alter the foreground and background colors that are used:

· Programs can also use the ANSI color control sequences to set the foreground and background colors.

· Extensions to the ANSI color controls (such as 16-, 88- or 256-colors) are treated similarly to the ANSI control.

· Using other control sequences (the “dynamic colors” feature), a program can change the foreground and background colors.

Each bit (bit “0” is 1, bit “1” is 2, etc.) corresponds to one of the parameters set by the title modes control sequence:

xterm accepts either a keyword (ignoring case) or the number shown:

xterm accepts either a keyword (ignoring case) or the number shown:

However, some users may want to write a title string encoded in UTF-8. The window manager is responsible for drawing window titles. Some window managers (not all) support UTF-8 encoding of window titles. Set this resource to “true” to allow UTF-8 encoded title strings. That cancels the translation to UTF-8, allowing UTF-8 strings to be displayed as is.

This feature is available as a menu entry, since it is related to the particular applications you are running within xterm. You can also use a control sequence (see the discussion of “Title Modes” in the control sequences document), to set an equivalent flag. The titleModes resource sets the same value, which overrides this resource.

The default is “false“.

1 for reverse,

2 for underline,

4 for bold and

8 for blink.

The default is “0“.

As a special case, the XON / XOFF keys (control/S and control/Q) are ignored.

Initially the checkmark is set according to both the utf8 and utf8Fonts resource values. If the latter is set to “always“, the checkmark is disabled. Likewise, if there are no fonts given in the utf8Fonts subresources, then the checkmark also is disabled.

The standard XTerm app-defaults file defines both sets of fonts, while the UXTerm app-defaults file defines only one set. Assuming the standard app-defaults files, this command will launch xterm able to switch between UTF-8 and ISO-8859-1 encoded fonts:

uxterm -class XTerm

*VT100*translations:    #override \n\
     Meta <KeyPress> /:dabbrev-expand()

^X Esc G <line+" "> <col+" ">

The term “eight-bit” is misleading: xterm checks if the key is in the range 128 to 255 (the eighth bit is set). If the value is in that range, depending on the resource values, xterm may then do one of the following:

· add 128 to the value, setting its eighth bit,

· send an Esc byte before the key, or

· send the key unaltered.

The format parameter allows these substitutions:

After constructing the command-string, xterm forks a subprocess and executes the command, which completes independently of xterm.

Unlike set-vt-font(), this does not affect the escape- and select-fonts, since those are not based on resource values. It does affect the fonts loosely organized under the “Default” menu entry, including font, boldFont, wideFont and wideBoldFont.

The action accepts optional parameters, which temporarily override resource settings. The parameter values are matched ignoring case:

The count argument indicates the number of units (which may be page, halfpage, pixel, or line) by which to scroll.

An adjustment can be specified for these values by appending a “+” or “–” sign followed by a number, e.g., page-2 to specify 2 lines less than a page.

If the third parameter mouse is given, the action is ignored when mouse reporting is enabled.

d ou D indicam a fonte padrão (a fonte usada inicialmente quando o xterm foi iniciado),

1 a 6 indicam as fontes especificadas pela fonte1 até os recursos da fonte6 ,

e ou E indique as fontes normais e em negrito que foram definidas por meio de códigos de escape (ou especificados como o segundo e o terceiro argumentos de ação, respectivamente)

es ou S indicam a seleção de fonte indicada pelo segundo argumento de ação.

E seO xterm está configurado para suportar caracteres largos; dois parâmetros opcionais adicionais são reconhecidos para o argumento e: fonte larga e fonte em negrito .

Use a entrada do processo ” cwd “, por exemplo, / proc / 12345 / cwd para obter o diretório de trabalho do processo que está sendo executado no xterm atual .

Nos sistemas que possuem a entrada de processo ” exe “, por exemplo, / proc / 12345 / exe , use-a para obter o executável real. Caso contrário, use a variável $ PATH para encontrar o xterm .

Se os parâmetros forem fornecidos na ação, passe-os para o novo processo xterm .

Esc ^P

or

Esc ^N

…according to whether the event is before, or after the current line, respectively. The ^N (or ^P) is repeated once for each line that the event differs from the current line. The control sequence is omitted altogether if the button event is on the current line.

*customization: -color

…in your .Xdefaults file to automatically use this resource file rather than /etc/X11/app-defaults/XTerm. If you do not do this, xterm uses its compiled-in default resource settings for colors.