Edward Moy
University of California, Berkeley
Revised by
Stephen Gildea
X Consortium (1994)
Thomas Dickey
XFree86 Project (1996-2006)
invisible-island.net (2006-2013)
updated for XTerm Patch #305 (2014/05/26)
|
c |
The literal character c. |
|
|
C |
A single (required) character. |
|
|
P s |
A single (usually optional) numeric parameter, composed of one of more digits. |
|
|
P m |
A multiple numeric parameter composed of any number of single numeric parameters, separated by ; character(s). Individual values for the parameters are listed with P s . |
|
|
P t |
A text parameter composed of printable characters. |
The xterm program recognizes both 8-bit and 7-bit control characters. It generates 7-bit controls (by default) or 8-bit if S8C1T is enabled. The following pairs of 7-bit and 8-bit control characters are equivalent:
|
ESC D |
Index ( IND is 0x84). |
|
ESC E |
Next Line ( NEL is 0x85). |
|
ESC H |
Tab Set ( HTS is 0x88). |
|
ESC M |
Reverse Index ( RI is 0x8d). |
|
ESC N |
Single Shift Select of G2 Character Set ( SS2 is 0x8e). This affects next character only. |
|
ESC O |
Single Shift Select of G3 Character Set ( SS3 is 0x8f). This affects next character only. |
|
ESC P |
Device Control String ( DCS is 0x90). |
|
ESC V |
Start of Guarded Area ( SPA is 0x96). |
|
ESC W |
End of Guarded Area ( EPA is 0x97). |
|
ESC X |
Start of String ( SOS is 0x98). |
|
ESC Z |
Return Terminal ID (DECID is 0x9a). Obsolete form of CSI c (DA). |
|
ESC [ |
Control Sequence Introducer ( CSI is 0x9b). |
|
ESC \ |
String Terminator ( ST is 0x9c). |
|
ESC ] |
Operating System Command ( OSC is 0x9d). |
|
ESC ^ |
Privacy Message ( PM is 0x9e). |
|
ESC _ |
Application Program Command ( APC is 0x9f). |
These control characters are used in the vtXXX emulation.
Most of these control sequences are standard
VT102 control sequences, but there is support for later DEC VT terminals
(i.e., VT220, VT320, VT420, VT510), as well as ISO 6429 and aixterm
color controls. The only VT102 feature not supported is auto-repeat,
since the only way X provides for this will affect all windows.
There are additional control sequences to provide xterm-dependent
functions, such as the scrollbar or window size. Where the function is
specified by DEC or ISO 6429, the code assigned to it is given in
parentheses.
The escape codes to designate and invoke character sets are specified by
ISO 2022 (see that document for a discussion of character sets).
Many of the features are optional; xterm can be configured and built without support for them.
Single-character functions
|
BEL |
Bell (Ctrl-G). |
|
|
BS |
Backspace (Ctrl-H). |
|
|
CR |
Carriage Return (Ctrl-M). |
|
|
ENQ |
Return Terminal Status (Ctrl-E). Default response is an empty string, but may be overridden by a resource answerbackString. |
|
|
FF |
Form Feed or New Page (NP). Ctrl-L is treated the same as LF. |
|
|
LF |
Line Feed or New Line (NL). (LF is Ctrl-J). |
|
|
SI |
Shift In (Ctrl-O) → Switch to Standard Character Set. This invokes the G0 character set (the default). |
|
|
SO |
Shift Out (Ctrl-N) → Switch to Alternate Character Set. This invokes the G1 character set. |
|
|
SP |
Space. |
|
|
TAB |
Horizontal Tab (HT) (Ctrl-I). |
|
|
VT |
Vertical Tab (Ctrl-K). This is treated the same as LF. |
Controls beginning with ESC
This excludes controls where ESC is part of a 7-bit equivalent to 8-bit C1 controls, ordered by the final character(s).
|
ESC SP F |
7-bit controls (S7C1T). |
|
|
ESC SP G |
8-bit controls (S8C1T). |
|
|
ESC SP L |
Set ANSI conformance level 1 (dpANS X3.134.1). |
|
|
ESC SP M |
Set ANSI conformance level 2 (dpANS X3.134.1). |
|
|
ESC SP N |
Set ANSI conformance level 3 (dpANS X3.134.1). |
|
|
ESC # 3 |
DEC double-height line, top half (DECDHL). |
|
|
ESC # 4 |
DEC double-height line, bottom half (DECDHL). |
|
|
ESC # 5 |
DEC single-width line (DECSWL). |
|
|
ESC # 6 |
DEC double-width line (DECDWL). |
|
|
ESC # 8 |
DEC Screen Alignment Test (DECALN). |
|
|
ESC % @ |
Select default character set. That is ISO 8859-1 (ISO 2022). |
|
|
ESC % G |
Select UTF-8 character set (ISO 2022). |
|
|
ESC ( C |
Designate G0 Character Set (ISO 2022, VT100). |
Final character C for designating
94-character sets. In this list, 0 , A and B apply to VT100 and up, the
remainder to VT220 and up. The VT220 character sets, together with the
Portuguese character set are activated by the National Replacement
Character controls. The A is a special case, since it is also activated
by the VT300-control for British Latin-1 separately from the National
Replacement Character controls.
C = 0 → DEC Special Character and Line Drawing Set.
C = < → DEC Supplementary (VT200).
C = % 5 → DEC Supplementary Graphics (VT300).
C = > → DEC Technical (VT300).
C = A → United Kingdom (UK).
C = B → United States (USASCII).
C = 4 → Dutch.
C = C or 5 → Finnish.
C = R or f → French.
C = Q or 9 → French Canadian (VT200, VT300).
C = K → German.
C = Y → Italian.
C = ` , E or 6 → Norwegian/Danish.
C = % 6 → Portuguese (VT300).
C = Z → Spanish.
C = H or 7 → Swedish.
C = = → Swiss.
|
ESC ) C |
Designate G1 Character Set (ISO 2022, VT100). |
The same character sets apply as for ESC ( C.
|
ESC * C |
Designate G2 Character Set (ISO 2022, VT220). |
The same character sets apply as for ESC ( C.
|
ESC + C |
Designate G3 Character Set (ISO 2022, VT220). |
The same character sets apply as for ESC ( C.
|
ESC - C |
Designate G1 Character Set (VT300). |
The same character sets apply as for ESC ( C.
|
ESC . C |
Designate G2 Character Set (VT300). |
The same character sets apply as for ESC ( C.
|
ESC / C |
Designate G3 Character Set (VT300). |
These work for 96-character sets only.
C = A → ISO Latin-1 Supplemental.
|
ESC 6 |
Back Index (DECBI), VT420 and up. |
|
|
ESC 7 |
Save Cursor (DECSC). |
|
|
ESC 8 |
Restore Cursor (DECRC). |
|
|
ESC 9 |
Forward Index (DECFI), VT420 and up. |
|
|
ESC = |
Application Keypad (DECKPAM). |
|
|
ESC > |
Normal Keypad (DECKPNM). |
|
|
ESC F |
Cursor to lower left corner of screen. This is enabled by the hpLowerleftBugCompat resource. |
|
|
ESC c |
Full Reset (RIS). |
|
|
ESC l |
Memory Lock (per HP terminals). Locks memory above the cursor. |
|
|
ESC m |
Memory Unlock (per HP terminals). |
|
|
ESC n |
Invoke the G2 Character Set as GL (LS2). |
|
|
ESC o |
Invoke the G3 Character Set as GL (LS3). |
|
|
ESC | |
Invoke the G3 Character Set as GR (LS3R). |
|
|
ESC } |
Invoke the G2 Character Set as GR (LS2R). |
|
|
ESC ~ |
Invoke the G1 Character Set as GR (LS1R). |
Application Program-Control functions
|
APC P t ST |
None. xterm implements no APC functions; P t is ignored. P t need not be printable characters. |
Device-Control functions
|
DCS P s ; P s | P t ST |
User-Defined Keys (DECUDK). The first parameter:
P s = 0 → Clear all UDK definitions before starting (default).
P s = 1 → Erase Below (default).
The second parameter:
P s = 0 ← Lock the keys (default).
P s = 1 ← Do not lock.
The third parameter is a ’;’-separated list of strings denoting the
key-code separated by a ’/’ from the hex-encoded key value. The key
codes correspond to the DEC function-key codes (e.g., F6=17).
|
DCS $ q P t ST |
Request Status String (DECRQSS). The string following the "q" is one of the following:
“ q
|
→ DECSCA |
||||
|
→ DECSCL |
||||
|
→ DECSTBM |
||||
|
→ SGR |
||||
|
→ DECSCUSR |
xterm responds with DCS 1 $ r P t ST for valid requests, replacing the P t with the corresponding CSI string, or DCS 0 $ r P t ST for invalid requests.
|
DCS + p P t ST |
Set Termcap/Terminfo Data (xterm, experimental). The string following the "p" is a name to use for retrieving data from the terminal database. The data will be used for the "tcap" keyboard configuration’s function- and special-keys, as well as by the Request Termcap/Terminfo String control.
|
DCS + q P t ST |
Request Termcap/Terminfo String (xterm,
experimental). The string following the "q" is a list of names encoded
in hexadecimal (2 digits per character) separated by ; which correspond
to termcap or terminfo key names.
Two special features are also recognized, which are not key names: Co for termcap colors (or colors for terminfo colors), and TN for termcap name (or name for terminfo name).
xterm responds with DCS 1 + r P t ST for valid requests, adding to P t an = , and the value of the corresponding string that xterm would send, or DCS 0 + r P t ST for invalid requests. The strings are encoded in hexadecimal (2 digits per character).

P s = 1 → Erase Above.
P s = 2 → Erase All.
P s = 3 → Erase Saved Lines (xterm).
|
CSI ? P s J |
Erase in Display (DECSED). |
P s = 0 → Selective Erase Below (default).
P s = 1 → Selective Erase Above.
P s = 2 → Selective Erase All.
|
CSI P s K |
Erase in Line (EL). |
P s = 0 → Erase to Right (default).
P s = 1 → Erase to Left.
P s = 2 → Erase All.
|
CSI ? P s K |
Erase in Line (DECSEL). |
P s = 0 → Selective Erase to Right (default).
P s = 1 → Selective Erase to Left.
P s = 2 → Selective Erase All.
|
CSI P s L |
Insert P s Line(s) (default = 1) (IL). |
||
|
CSI P s M |
Delete P s Line(s) (default = 1) (DL). |
||
|
CSI P s P |
Delete P s Character(s) (default = 1) (DCH). |
||
|
CSI P s S |
Scroll up P s lines (default = 1) (SU). |
||
|
CSI ? P i ; |
P a ; P v S
|
If configured to support either Sixel Graphics or ReGIS Graphics, xterm accepts a three-parameter control sequence, where P i , P a and P v are the item, action and value. |
P i = 1 → item (color registers)
P a = 1 → read the number of color registers
P a = 2 → reset the number of color registers
P a = 3 → set the number of color registers to the value P v
The control sequence returns a response using the same form:
CSI ?  Parameters are [func;startx;starty;firstrow;lastrow]. See the section Mouse Tracking. |
||
|
CSI > P s ; |
P s T
|
Reset one or more features of the title modes to the default value. Normally, "reset" disables the feature. It is possible to disable the ability to reset features by compiling a different default for the title modes into xterm. |
P s = 0 → Do not set window/icon labels using hexadecimal.
P s = 1 → Do not query window/icon labels using hexadecimal.
P s = 2 → Do not set window/icon labels using UTF-8.
P s = 3 → Do not query window/icon labels using UTF-8. (See discussion of "Title Modes").
|
CSI P s X |
Erase P s Character(s) (default = 1) (ECH). |
|
|
CSI P s Z |
Cursor Backward Tabulation P s tab stops (default = 1) (CBT). |
|
|
CSI P m ` |
Character Position Absolute [column] (default = [row,1]) (HPA). |
|
|
CSI P m a |
Character Position Relative [columns] (default = [row,col+1]) (HPR). |
|
|
CSI P s b |
Repeat the preceding graphic character P s times (REP). |
|
|
CSI P s c |
Send Device Attributes (Primary DA). |
P s = 0 or omitted → request attributes from terminal. The response depends on the decTerminalID resource setting.
→ CSI ? 1 ; 2 c (‘‘VT100 with Advanced Video Option’’)
→ CSI ? 1 ; 0 c (‘‘VT101 with No Options’’)
→ CSI ? 6 c (‘‘VT102’’)
→ CSI ? 6 2 ; P s c (‘‘VT220’’)
→ CSI ? 6 3 ; P s c (‘‘VT320’’)
→ CSI ? 6 4 ; P s c (‘‘VT420’’)
The VT100-style response parameters do not mean anything by themselves.
VT220 (and higher) parameters do, telling the host what features the
terminal supports:
P s = 1 → 132-columns.
P s = 2 → Printer.
P s = 3 → ReGIS graphics.
P s = 4 → Sixel graphics.
P s = 6 → Selective erase.
P s = 8 → User-defined keys.
P s = 9 → National Replacement Character sets.
P s = 1 5 → Technical characters.
P s = 1 8 → User windows.
P s = 2 1 → Horizontal scrolling.
P s = 2 2 → ANSI color, e.g., VT525.
P s = 2 9 → ANSI text locator (i.e., DEC Locator mode).
|
CSI > P s c |
Send Device Attributes (Secondary DA). |
P s = 0 or omitted → request the terminal’s identification code. The response depends on the decTerminalID resource setting. It should apply only to VT220 and up, but xterm extends this to VT100.
→ CSI > P p ; P v ; P c c
where P p denotes the terminal type
P p = 0 → ‘‘VT100’’.
P p = 1 → ‘‘VT220’’.
P p = 2 → ‘‘VT240’’.
P p = 1 8 → ‘‘VT330’’.
P p = 1 9 → ‘‘VT340’’.
P p = 2 4 → ‘‘VT320’’.
P p = 4 1 → ‘‘VT420’’.
P p = 6 1 → ‘‘VT510’’.
P p = 6 4 → ‘‘VT520’’.
P p = 6 5 → ‘‘VT525’’.
and P v is the firmware version (for xterm, this was originally the XFree86 patch number, starting with 95). In a DEC terminal, P c indicates the ROM cartridge registration number and is always zero.
|
CSI P m d |
Line Position Absolute [row] (default = [1,column]) (VPA). |
|
CSI P m e |
Line Position Relative [rows] (default = [row+1,column]) (VPR). |
|
CSI P s ; P |
s f
|
Horizontal and Vertical Position [row;column] (default = [1,1]) (HVP). |
||
|
CSI P s g |
Tab Clear (TBC). |
P s = 0 → Clear Current Column (default).
P s = 3 → Clear All.
|
CSI P m h |
Set Mode (SM). |
P s = 2 → Keyboard Action Mode (AM).
P s = 4 → Insert Mode (IRM).
P s = 1 2 → Send/receive (SRM).
P s = 2 0 → Automatic Newline (LNM).
|
CSI ? P m h |
DEC Private Mode Set (DECSET). |
P s = 1 → Application Cursor Keys (DECCKM).
P s = 2 → Designate USASCII for character sets G0-G3 (DECANM), and set VT100 mode.
P s = 3 → 132 Column Mode (DECCOLM).
P s = 4 → Smooth (Slow) Scroll (DECSCLM).
P s = 5 → Reverse Video (DECSCNM).
P s = 6 → Origin Mode (DECOM).
P s = 7 → Wraparound Mode (DECAWM).
P s = 8 → Auto-repeat Keys (DECARM).
P s = 9 → Send Mouse X & Y on button press. See the section Mouse Tracking. This is the X10 xterm mouse protocol.
P s = 1 0 → Show toolbar (rxvt).
P s = 1 2 → Start Blinking Cursor (att610).
P s = 1 8 → Print form feed (DECPFF).
P s = 1 9 → Set print extent to full screen (DECPEX).
P s = 2 5 → Show Cursor (DECTCEM).
P s = 3 0 → Show scrollbar (rxvt).
P s = 3 5 → Enable font-shifting functions (rxvt).
P s = 3 8 → Enter Tektronix Mode (DECTEK).
P s = 4 0 → Allow 80 → 132 Mode.
P s = 4 1 → more(1) fix (see curses resource).
P s = 4 2 → Enable National Replacement Character sets (DECNRCM).
P s = 4 4 → Turn On Margin Bell.
P s = 4 5 → Reverse-wraparound Mode.
P s = 4 6 → Start Logging. This is normally disabled by a compile-time option.
P s = 4 7 → Use Alternate Screen Buffer. (This may be disabled by the titeInhibit resource).
P s = 6 6 → Application keypad (DECNKM).
P s = 6 7 → Backarrow key sends backspace (DECBKM).
P s = 6 9 → Enable left and right margin mode (DECLRMM), VT420 and up.
P s = 9 5 → Do not clear screen when DECCOLM is set/reset (DECNCSM), VT510 and up.
P s = 1 0 0 0 → Send Mouse X & Y on button press and release. See the section Mouse Tracking. This is the X11 xterm mouse protocol.
P s = 1 0 0 1 → Use Hilite Mouse Tracking.
P s = 1 0 0 2 → Use Cell Motion Mouse Tracking.
P s = 1 0 0 3 → Use All Motion Mouse Tracking.
P s = 1 0 0 4 → Send FocusIn/FocusOut events.
P s = 1 0 0 5 → Enable UTF-8 Mouse Mode.
P s = 1 0 0 6 → Enable SGR Mouse Mode.
P s = 1 0 0 7 → Enable Alternate Scroll Mode.
P s = 1 0 1 0 → Scroll to bottom on tty output (rxvt).
P s = 1 0 1 1 → Scroll to bottom on key press (rxvt).
P s = 1 0 1 5 → Enable urxvt Mouse Mode.
P s = 1 0 3 4 → Interpret "meta" key, sets eighth bit. (enables the eightBitInput resource).
P s = 1 0 3 5 → Enable special modifiers for Alt and NumLock keys. (This enables the numLock resource).
P s = 1 0 3 6 → Send ESC when Meta modifies a key. (This enables the metaSendsEscape resource).
P s = 1 0 3 7 → Send DEL from the editing-keypad Delete key.
P s = 1 0 3 9 → Send ESC when Alt modifies a key. (This enables the altSendsEscape resource).
P s = 1 0 4 0 → Keep selection even if not highlighted. (This enables the keepSelection resource).
P s = 1 0 4 1 → Use the CLIPBOARD selection. (This enables the selectToClipboard resource).
P s = 1 0 4 2 → Enable Urgency window manager hint when Control-G is received. (This enables the bellIsUrgent resource).
P s = 1 0 4 3 → Enable raising of the window when Control-G is received. (enables the popOnBell resource).
P s = 1 0 4 7 → Use Alternate Screen Buffer. (This may be disabled by the titeInhibit resource).
P s = 1 0 4 8 → Save cursor as in DECSC. (This may be disabled by the titeInhibit resource).
P s = 1 0 4 9 → Save cursor as in DECSC and use Alternate Screen Buffer, clearing it first. (This may be disabled by the titeInhibit
resource). This combines the effects of the 1 0 4 7 and 1 0 4 8 modes.
Use this with terminfo-based applications rather than the 4 7 mode.
P s = 1 0 5 0 → Set terminfo/termcap function-key mode.
P s = 1 0 5 1 → Set Sun function-key mode.
P s = 1 0 5 2 → Set HP function-key mode.
P s = 1 0 5 3 → Set SCO function-key mode.
P s = 1 0 6 0 → Set legacy keyboard emulation (X11R6).
P s = 1 0 6 1 → Set VT220 keyboard emulation.
P s = 2 0 0 4 → Set bracketed paste mode.
|
CSI P m i |
Media Copy (MC). |
P s = 0 → Print screen (default).
P s = 4 → Turn off printer controller mode.
P s = 5 → Turn on printer controller mode.
|
CSI ? P m i |
Media Copy (MC, DEC-specific). |
P s = 1 → Print line containing cursor.
P s = 4 → Turn off autoprint mode.
P s = 5 → Turn on autoprint mode.
P s = 1 0 → Print composed display, ignores DECPEX.
P s = 1 1 → Print all pages.
|
CSI P m l |
Reset Mode (RM). |
P s = 2 → Keyboard Action Mode (AM).
P s = 4 → Replace Mode (IRM).
P s = 1 2 → Send/receive (SRM).
P s = 2 0 → Normal Linefeed (LNM).
|
CSI ? P m l |
DEC Private Mode Reset (DECRST). |
P s = 1 → Normal Cursor Keys (DECCKM).
P s = 2 → Designate VT52 mode (DECANM).
P s = 3 → 80 Column Mode (DECCOLM).
P s = 4 → Jump (Fast) Scroll (DECSCLM).
P s = 5 → Normal Video (DECSCNM).
P s = 6 → Normal Cursor Mode (DECOM).
P s = 7 → No Wraparound Mode (DECAWM).
P s = 8 → No Auto-repeat Keys (DECARM).
P s = 9 → Don’t send Mouse X & Y on button press.
P s = 1 0 → Hide toolbar (rxvt).
P s = 1 2 → Stop Blinking Cursor (att610).
P s = 1 8 → Don’t print form feed (DECPFF).
P s = 1 9 → Limit print to scrolling region (DECPEX).
P s = 2 5 → Hide Cursor (DECTCEM).
P s = 3 0 → Don’t show scrollbar (rxvt).
P s = 3 5 → Disable font-shifting functions (rxvt).
P s = 4 0 → Disallow 80 → 132 Mode.
P s = 4 1 → No more(1) fix (see curses resource).
P s = 4 2 → Disable National Replacement Character sets (DECNRCM).
P s = 4 4 → Turn Off Margin Bell.
P s = 4 5 → No Reverse-wraparound Mode.
P s = 4 6 → Stop Logging. (This is normally disabled by a compile-time option).
P s = 4 7 → Use Normal Screen Buffer.
P s = 6 6 → Numeric keypad (DECNKM).
P s = 6 7 → Backarrow key sends delete (DECBKM).
P s = 6 9 → Disable left and right margin mode (DECLRMM), VT420 and up.
P s = 9 5 → Clear screen when DECCOLM is set/reset (DECNCSM), VT510 and up.
P s = 1 0 0 0 → Don’t send Mouse X & Y on button press and release. See the section Mouse Tracking.
P s = 1 0 0 1 → Don’t use Hilite Mouse Tracking.
P s = 1 0 0 2 → Don’t use Cell Motion Mouse Tracking.
P s = 1 0 0 3 → Don’t use All Motion Mouse Tracking.
P s = 1 0 0 4 → Don’t send FocusIn/FocusOut events.
P s = 1 0 0 5 → Disable UTF-8 Mouse Mode.
P s = 1 0 0 6 → Disable SGR Mouse Mode.
P s = 1 0 0 7 → Disable Alternate Scroll Mode.
P s = 1 0 1 0 → Don’t scroll to bottom on tty output (rxvt).
P s = 1 0 1 1 → Don’t scroll to bottom on key press (rxvt).
P s = 1 0 1 5 → Disable urxvt Mouse Mode.
P s = 1 0 3 4 → Don’t interpret "meta" key. (This disables the eightBitInput resource).
P s = 1 0 3 5 → Disable special modifiers for Alt and NumLock keys. (This disables the numLock resource).
P s = 1 0 3 6 → Don’t send ESC when Meta modifies a key. (This disables the metaSendsEscape resource).
P s = 1 0 3 7 → Send VT220 Remove from the editing-keypad Delete key.
P s = 1 0 3 9 → Don’t send ESC when Alt modifies a key. (This disables the altSendsEscape resource).
P s = 1 0 4 0 → Do not keep selection when not highlighted. (This disables the keepSelection resource).
P s = 1 0 4 1 → Use the PRIMARY selection. (This disables the selectToClipboard resource).
P s = 1 0 4 2 → Disable Urgency window manager hint when Control-G is received. (This disables the bellIsUrgent resource).
P s = 1 0 4 3 → Disable raising of the window when Control-G is received. (This disables the popOnBell resource).
P s = 1 0 4 7 → Use Normal Screen Buffer, clearing screen first if in the Alternate Screen. (This may be disabled by the titeInhibit resource).
P s = 1 0 4 8 → Restore cursor as in DECRC. (This may be disabled by the titeInhibit resource).
P s = 1 0 4 9 → Use Normal Screen Buffer and restore cursor as in DECRC. (This may be disabled by the titeInhibit
resource). This combines the effects of the 1 0 4 7 and 1 0 4 8 modes.
Use this with terminfo-based applications rather than the 4 7 mode.
P s = 1 0 5 0 → Reset terminfo/termcap function-key mode.
P s = 1 0 5 1 → Reset Sun function-key mode.
P s = 1 0 5 2 → Reset HP function-key mode.
P s = 1 0 5 3 → Reset SCO function-key mode.
P s = 1 0 6 0 → Reset legacy keyboard emulation (X11R6).
P s = 1 0 6 1 → Reset keyboard emulation to Sun/PC style.
P s = 2 0 0 4 → Reset bracketed paste mode.
|
CSI P m m |
Character Attributes (SGR). |
P s = 0 → Normal (default).
P s = 1 → Bold.
P s = 2 → Faint, decreased intensity (ISO 6429).
P s = 3 → Italicized (ISO 6429).
P s = 4 → Underlined.
P s = 5 → Blink (appears as Bold).
P s = 7 → Inverse.
P s = 8 → Invisible, i.e., hidden (VT300).
P s = 9 → Crossed-out characters (ISO 6429).
P s = 2 1 → Doubly-underlined (ISO 6429).
P s = 2 2 → Normal (neither bold nor faint).
P s = 2 3 → Not italicized (ISO 6429).
P s = 2 4 → Not underlined.
P s = 2 5 → Steady (not blinking).
P s = 2 7 → Positive (not inverse).
P s = 2 8 → Visible, i.e., not hidden (VT300).
P s = 2 9 → Not crossed-out (ISO 6429).
P s = 3 0 → Set foreground color to Black.
P s = 3 1 → Set foreground color to Red.
P s = 3 2 → Set foreground color to Green.
P s = 3 3 → Set foreground color to Yellow.
P s = 3 4 → Set foreground color to Blue.
P s = 3 5 → Set foreground color to Magenta.
P s = 3 6 → Set foreground color to Cyan.
P s = 3 7 → Set foreground color to White.
P s = 3 9 → Set foreground color to default (original).
P s = 4 0 → Set background color to Black.
P s = 4 1 → Set background color to Red.
P s = 4 2 → Set background color to Green.
P s = 4 3 → Set background color to Yellow.
P s = 4 4 → Set background color to Blue.
P s = 4 5 → Set background color to Magenta.
P s = 4 6 → Set background color to Cyan.
P s = 4 7 → Set background color to White.
P s = 4 9 → Set background color to default (original).
If 16-color support is compiled, the following apply. Assume that xterm’s resources are set so that the ISO color codes are the first 8 of a set of 16. Then the aixterm colors are the bright versions of the ISO colors:
P s = 9 0 → Set foreground color to Black.
P s = 9 1 → Set foreground color to Red.
P s = 9 2 → Set foreground color to Green.
P s = 9 3 → Set foreground color to Yellow.
P s = 9 4 → Set foreground color to Blue.
P s = 9 5 → Set foreground color to Magenta.
P s = 9 6 → Set foreground color to Cyan.
P s = 9 7 → Set foreground color to White.
P s = 1 0 0 → Set background color to Black.
P s = 1 0 1 → Set background color to Red.
P s = 1 0 2 → Set background color to Green.
P s = 1 0 3 → Set background color to Yellow.
P s = 1 0 4 → Set background color to Blue.
P s = 1 0 5 → Set background color to Magenta.
P s = 1 0 6 → Set background color to Cyan.
P s = 1 0 7 → Set background color to White.
If xterm is compiled with the 16-color support disabled, it supports the following, from rxvt:
P s = 1 0 0 → Set foreground and background color to default.
Xterm maintains a color palette whose entries are identified by an index beginning with zero. If 88- or 256-color support is compiled, the following apply:
|
• |
All parameters are decimal integers. |
||
|
• |
RGB values range from zero (0) to 255. |
||
|
• |
ISO-8613-3 can be interpreted in more than one way; xterm allows the semicolons in this control to be replaced by colons (but after the first colon, colons must be used). |
These ISO-8613-3 controls are supported:
P s = 3 8 ; 2 ; P r ; P g ; P b → Set foreground color to the closest match in xterm’s palette for the given RGB P r /P g /P b .
P s = 3 8 ; 5 ; P s → Set foreground color to the second P s .
P s = 4 8 ; 2 ; P r ; P g ; P b → Set background color to the closest match in xterm’s palette for the given RGB P r /P g /P b .
P s = 4 8 ; 5 ; P s → Set background color to the second P s .
|
CSI > P s ; P s m |
Set or reset resource-values used by xterm
to decide whether to construct escape sequences holding information
about the modifiers pressed with a given key. The first parameter
identifies the resource to set/reset. The second parameter is the value
to assign to the resource. If the second parameter is omitted, the
resource is reset to its initial value.
P s = 0 → modifyKeyboard.
P s = 1 → modifyCursorKeys.
P s = 2 → modifyFunctionKeys.
P s = 4 → modifyOtherKeys.
If no parameters are given, all resources are reset to their initial values.
|
CSI P s n |
Device Status Report (DSR). |
P s = 5 → Status Report. Result (‘‘OK’’) is
CSI 0 n
P s = 6 → Report Cursor Position (CPR) [row;column]. Result is
CSI r ; c R
Note: it is possible
for this sequence to be sent by a function key. For example, with the
default keyboard configuration the shifted F1 key may send (with shift-,
control-, alt-modifiers)
CSI 1 ; 2 R , or
CSI 1 ; 5 R , or
CSI 1 ; 6 R , etc.
The second parameter encodes the modifiers; values range from 2 to 16. See the section PC-Style Function Keys for the codes. The modifyFunctionKeys and modifyKeyboard resources can change the form of the string sent from the modified F1 key.
|
CSI > P s n |
Disable modifiers which may be enabled via the CSI > P s ; P s m sequence. This corresponds to a resource value of "-1", which cannot be set with the other sequence. The parameter identifies the resource to be disabled: |
P s = 0 → modifyKeyboard.
P s = 1 → modifyCursorKeys.
P s = 2 → modifyFunctionKeys.
P s = 4 → modifyOtherKeys.
If the parameter is omitted, modifyFunctionKeys is disabled. When modifyFunctionKeys is disabled, xterm
uses the modifier keys to make an extended sequence of functions rather
than adding a parameter to each function key to denote the modifiers.
|
CSI ? P s n |
Device Status Report (DSR, DEC-specific). |
P s = 6 → Report Cursor Position (DECXCPR) [row;column] as CSI ? r ; c R (assumes the default page, i.e., "1").
P s = 1 5 → Report Printer status as CSI ? 1 0 n (ready). or CSI ? 1 1 n (not ready).
P s = 2 5 → Report UDK status as CSI ? 2 0 n (unlocked) or CSI ? 2 1 n (locked).
P s = 2 6 → Report Keyboard status as
CSI ? 2 7 ; 1 ; 0 ; 0 n (North American).
The last two parameters apply to VT400 & up, and denote keyboard ready and LK01 respectively.
P s = 5 3 → Report Locator status as CSI ? 5 3 n Locator available, if compiled-in, or CSI ? 5 0 n No Locator, if not.
P s = 5 5 → Report Locator status as CSI ? 5 3 n Locator available, if compiled-in, or CSI ? 5 0 n No Locator, if not.
P s = 5 6 → Report Locator type as CSI ? 5 7 ; 1 n Mouse, if compiled-in, or CSI ? 5 7 ; 0 n Cannot identify, if not.
P s = 6 2 → Report macro space (DECMSR) as CSI P n \* {
P s = 6 3 → Report memory checksum (DECCKSR) as DCS P t ! x x x x ST
P t is the request id (from an optional parameter to the request).
The x’s are hexadecimal digits 0-9 and A-F.
P s = 7 5 → Report data integrity as CSI ? 7 0 n (ready, no errors)
P s = 8 5 → Report multi-session configuration as CSI ? 8 3 n (not configured for multiple-session operation).
|
CSI > P s p |
Set resource value pointerMode. This is used by xterm to decide whether to hide the pointer cursor as the user types. Valid values for the parameter: |
P s = 0 → never hide the pointer.
P s = 1 → hide if the mouse tracking mode is not enabled.
P s = 2 → always hide the pointer, except when leaving the window.
P s = 3 → always hide the pointer, even if leaving/entering the window. If no parameter is given, xterm uses the default, which is 1 .
|
CSI ! p |
Soft terminal reset (DECSTR). |
|
CSI P s $ p |
Request ANSI mode (DECRQM). For VT300 and up, reply is |
CSI P s ; P m $ y
where P s is the mode number as in RM, and P m is the mode value:
0 - not recognized
1 - set
2 - reset
3 - permanently set
4 - permanently reset
|
CSI ? P s $ p |
Request DEC private mode (DECRQM). For VT300 and up, reply is
CSI ?  Valid values for the first parameter:
P s = 6 1 → VT100.
P s = 6 2 → VT200.
P s = 6 3 → VT300.
Valid values for the second parameter:
P s = 0 → 8-bit controls.
P s = 1 → 7-bit controls (always set for VT100).
P s = 2 → 8-bit controls.
|
CSI P s q |
Load LEDs (DECLL). |
P s = 0 → Clear all LEDS (default).
P s = 1 → Light Num Lock.
P s = 2 → Light Caps Lock.
P s = 3 → Light Scroll Lock.
P s = 2 1 → Extinguish Num Lock.
P s = 2 2 → Extinguish Caps Lock.
P s = 2 3 → Extinguish Scroll Lock.
|
CSI P s SP q |
Set cursor style (DECSCUSR, VT520).
P s = 0 → blinking block.
P s = 1 → blinking block (default).
P s = 2 → steady block.
P s = 3 → blinking underline.
P s = 4 → steady underline.
P s = 5 → blinking bar (xterm).
P s = 6 → steady bar (xterm).
|
CSI P s “ q |
Select character protection attribute (DECSCA). Valid values for the parameter: |
P s = 0 → DECSED and DECSEL can erase (default).
P s = 1 → DECSED and DECSEL cannot erase.
P s = 2 → DECSED and DECSEL can erase.
|
CSI P s ; P s r |
Set Scrolling Region [top;bottom] (default = full size of window) (DECSTBM).
|
CSI ? P m r |
Restore DEC Private Mode Values. The value of P s previously saved is restored.
P s denotes the SGR attributes to change: 0, 1, 4, 5, 7.
|
CSI P l ; P r s |
Set left and right margins (DECSLRM), available only when DECLRMM is enabled (VT420 and up).
|
CSI s |
Save cursor (ANSI.SYS), available only when DECLRMM is disabled. |
|
CSI ? P m s |
Save DEC Private Mode Values. P s values are the same as for DECSET. |
|
CSI P s ; P |
s ; P s t
|
Window manipulation (from dtterm, as well as extensions). These controls may be disabled using the allowWindowOps resource. Valid values for the first (and any additional parameters) are: |
P s = 1 → De-iconify window.
P s = 2 → Iconify window.
P s = 3 ; x ; y → Move window to [x, y].
P s = 4 ; height ; width → Resize the xterm
window to given height and width in pixels. Omitted parameters reuse
the current height or width. Zero parameters use the display’s height or
width.
P s = 5 → Raise the xterm window to the front of the stacking order.
P s = 6 → Lower the xterm window to the bottom of the stacking order.
P s = 7 → Refresh the xterm window.
P s = 8 ; height ; width → Resize the text
area to given height and width in characters. Omitted parameters reuse
the current height or width. Zero parameters use the display’s height or
width.
P s = 9 ; 0 → Restore maximized window.
P s = 9 ; 1 → Maximize window (i.e., resize to screen size).
P s = 9 ; 2 → Maximize window vertically.
P s = 9 ; 3 → Maximize window horizontally.
P s = 1 0 ; 0 → Undo full-screen mode.
P s = 1 0 ; 1 → Change to full-screen.
P s = 1 0 ; 2 → Toggle full-screen.
P s = 1 1 → Report xterm window state. If the xterm window is open (non-iconified), it returns CSI 1 t . If the xterm window is iconified, it returns CSI 2 t .
P s = 1 3 → Report xterm window position. Result is CSI 3 ; x ; y t
P s = 1 4 → Report xterm window in pixels. Result is CSI 4 ; height ; width t
P s = 1 8 → Report the size of the text area in characters. Result is CSI 8 ; height ; width t
P s = 1 9 → Report the size of the screen in characters. Result is CSI 9 ; height ; width t
P s = 2 0 → Report xterm window’s icon label. Result is OSC L label ST
P s = 2 1 → Report xterm window’s title. Result is OSC l label ST
P s = 2 2 ; 0 → Save xterm icon and window title on stack.
P s = 2 2 ; 1 → Save xterm icon title on stack.
P s = 2 2 ; 2 → Save xterm window title on stack.
P s = 2 3 ; 0 → Restore xterm icon and window title from stack.
P s = 2 3 ; 1 → Restore xterm icon title from stack.
P s = 2 3 ; 2 → Restore xterm window title from stack.

P s denotes the attributes to reverse, i.e., 1, 4, 5, 7.
|
CSI > P s ; P s t |
Set one or more features of the title modes. Each parameter enables a single feature.
P s = 0 → Set window/icon labels using hexadecimal.
P s = 1 → Query window/icon labels using hexadecimal.
P s = 2 → Set window/icon labels using UTF-8.
P s = 3 → Query window/icon labels using UTF-8. (See discussion of "Title Modes")
|
CSI P s SP t |
Set warning-bell volume (DECSWBV, VT520).
P s = 0 or 1 → off.
P s = 2 , 3 or 4 → low.
P s = 5 , 6 , 7 , or 8 → high.
|
CSI u |
Restore cursor (ANSI.SYS). |
||
|
CSI P s SP |
u
|
Set margin-bell volume (DECSMBV, VT520). |
P s = 1 → off.
P s = 2 , 3 or 4 → low.
P s = 0 , 5 , 6 , 7 , or 8 → high.
|
CSI P t ; P l ; P b ; P r ; P p ; P t ; P l ; P p $ v |
Copy Rectangular Area (DECCRA, VT400 and up).

P p denotes the source page.
P t ; P l denotes the target location.

Parameters are [top;left;bottom;right].
Defines the coordinates of a filter rectangle and activates it. Anytime
the locator is detected outside of the filter rectangle, an outside
rectangle event is generated and the rectangle is disabled. Filter
rectangles are always treated as "one-shot" events. Any parameters that
are omitted default to the current locator position. If all parameters
are omitted, any locator motion will be reported. DECELR always cancels
any prevous rectangle definition.
|
CSI P s x |
Request Terminal Parameters (DECREQTPARM). |
if P s is a "0" (default) or "1", and xterm is emulating VT100, the control sequence elicits a response of the same form whose parameters describe the terminal:
P s → the given P s incremented by 2.
P n = 1 ← no parity.
P n = 1 ← eight bits.
P n = 1 ← 2 8 transmit 38.4k baud.
P n = 1 ← 2 8 receive 38.4k baud.
P n = 1 ← clock multiplier.
P n = 0 ← STP flags.
|
CSI P s * x |
Select Attribute Change Extent (DECSACE). |
P s = 0 → from start to end position, wrapped.
P s = 1 → from start to end position, wrapped.
P s = 2 → rectangle (exact).
|
CSI P i ; P g ; P t ; P l ; P b ; P r * y |
Request Checksum of Rectangular Area (DECRQCRA), VT420 and up. Response is
DCS P t ! x x x x ST
P i is the request id.
P g is the page number.

The x’s are hexadecimal digits 0-9 and A-F.
|
CSI P c ; P t ; P l ; P b ; P r $ x |
Fill Rectangular Area (DECFRA), VT420 and up.
P c is the character to use.

Valid values for the first parameter:
P s = 0 → Locator disabled (default).
P s = 1 → Locator enabled.
P s = 2 → Locator enabled for one report, then disabled.
The second parameter specifies the coordinate unit for locator reports.
Valid values for the second parameter:
P u = 0 ← or omitted → default to character cells.
P u = 1 ← device physical pixels.
P u = 2 ← character cells.
|
CSI P t ; P l ; P b ; P r $ z |
Erase Rectangular Area (DECERA), VT400 and up.
P t ; P l ; P b ; P r denotes the rectangle.
|
CSI P m ’ { |
Select Locator Events (DECSLE). |
Valid values for the first (and any additional parameters) are:
P s = 0 → only respond to explicit host requests (DECRQLP).
(This is default). It also cancels any filter
rectangle.
P s = 1 → report button down transitions.
P s = 2 → do not report button down transitions.
P s = 3 → report button up transitions.
P s = 4 → do not report button up transitions.
|
CSI P t ; P l ; P b ; P r $ { |
Selective Erase Rectangular Area (DECSERA), VT400 and up.
P t ; P l ; P b ; P r denotes the rectangle.
|
CSI P s ’ | |
Request Locator Position (DECRQLP). |
Valid values for the parameter are:
P s = 0 , 1 or omitted → transmit a single DECLRP locator report.
If Locator Reporting has been enabled by a DECELR, xterm will respond with a DECLRP Locator Report. This report is also generated on button up and down events if they have been enabled with a DECSLE, or when the locator is detected outside of a filter rectangle, if filter rectangles have been enabled with a DECEFR.
→ CSI P e ; P b ; P r ; P c ; P p & w
Parameters are [event;button;row;column;page].
Valid values for the event:
P e = 0 → locator unavailable - no other parameters sent.
P e = 1 → request - xterm received a DECRQLP.
P e = 2 → left button down.
P e = 3 → left button up.
P e = 4 → middle button down.
P e = 5 → middle button up.
P e = 6 → right button down.
P e = 7 → right button up.
P e = 8 → M4 button down.
P e = 9 → M4 button up.
P e = 1 0 → locator outside filter rectangle.
‘‘button’’ parameter is a bitmask indicating which buttons are pressed:
P b = 0 ← no buttons down.
P b & 1 ← right button down.
P b & 2 ← middle button down.
P b & 4 ← left button down.
P b & 8 ← M4 button down.
‘‘row’’ and ‘‘column’’ parameters are the coordinates of the locator position in the xterm window, encoded as ASCII decimal.
The ‘‘page’’ parameter is not used by xterm, and will be omitted.
|
CSI P m ’ } |
Insert P s Column(s) (default = 1) (DECIC), VT420 and up. |
|
CSI P m ’ ~ |
Delete P s Column(s) (default = 1) (DECDC), VT420 and up. |
Operating System Controls
|
OSC P s ; P t ST |
|
|
OSC P s ; P t BEL |
Set Text Parameters. For colors and font, if P t
is a "?", the control sequence elicits a response which consists of the
control sequence which would set the corresponding value. The dtterm control sequences allow you to determine the icon name and window title.
P s = 0 → Change Icon Name and Window Title to P t .
P s = 1 → Change Icon Name to P t .
P s = 2 → Change Window Title to P t .
P s = 3 → Set X property on top-level window. P t should be in the form "prop=value", or just "prop" to delete the property
P s = 4 ; c ; spec → Change Color Number c to the color specified by spec. This can be a name or RGB specification as per XParseColor. Any number of c name
pairs may be given. The color numbers correspond to the ANSI colors
0-7, their bright versions 8-15, and if supported, the remainder of the
88-color or 256-color table.
If a "?" is given rather than a name or RGB specification, xterm replies with a control sequence of the same form which can be used to set the corresponding color. Because more than one pair of color number and specification can be given in one control sequence, xterm can make more than one reply.
P s = 5 ; c ; spec → Change Special Color Number c to the color specified by spec. This can be a name or RGB specification as per XParseColor. Any number of c name pairs may be given. The special colors can also be set by adding the maximum number of colors to these codes in an OSC 4 control:
P c = 0 ← resource colorBD (BOLD).
P c = 1 ← resource colorUL (UNDERLINE).
P c = 2 ← resource colorBL (BLINK).
P c = 3 ← resource colorRV (REVERSE).
The 10 colors (below) which may be set or queried using 1 0 through 1 9 are denoted dynamic colors, since the corresponding control sequences were the first means for setting xterm’s colors dynamically, i.e., after it was started. They are not the same as the ANSI colors. These controls may be disabled using the allowColorOps resource. At least one parameter is expected for P t . Each successive parameter changes the next color in the list. The value of P s tells the starting point in the list. The colors are specified by name or RGB specification as per XParseColor.
If a "?" is given rather than a name or RGB specification, xterm replies with a control sequence of the same form which can be used to set the corresponding dynamic color. Because more than one pair of color number and specification can be given in one control sequence, xterm can make more than one reply.
P s = 1 0 → Change VT100 text foreground color to P t .
P s = 1 1 → Change VT100 text background color to P t .
P s = 1 2 → Change text cursor color to P t .
P s = 1 3 → Change mouse foreground color to P t .
P s = 1 4 → Change mouse background color to P t .
P s = 1 5 → Change Tektronix foreground color to P t .
P s = 1 6 → Change Tektronix background color to P t .
P s = 1 7 → Change highlight background color to P t .
P s = 1 8 → Change Tektronix cursor color to P t .
P s = 1 9 → Change highlight foreground color to P t .
P s = 4 6 → Change Log File to P t . (This is normally disabled by a compile-time option).
P s = 5 0 → Set Font to P t . These controls may be disabled using the allowFontOps resource. If P t
begins with a "#", index in the font menu, relative (if the next
character is a plus or minus sign) or absolute. A number is expected but
not required after the sign (the default is the current entry for
relative, zero for absolute indexing).
The same rule (plus or minus sign, optional number) is used when querying the font. The remainder of P t is ignored.
A font can be specified after a "#" index expression, by adding a space and then the font specifier.
If the "TrueType Fonts" menu entry is set (the renderFont resource), then this control sets/queries the faceName resource.
P s = 5 1 (reserved for Emacs shell).
P s = 5 2 → Manipulate Selection Data. These controls may be disabled using the allowWindowOps resource. The parameter P t is parsed as
|
P c ; P d |
The first, P c , may
contain zero or more characters from the set c p s 0 1 2 3 4 5 6 7 . It
is used to construct a list of selection parameters for clipboard,
primary, select, or cut buffers 0 through 7 respectively, in the order
given. If the parameter is empty, xterm uses s 0 , to specify the configurable primary/clipboard selection and cut buffer 0.
The second parameter, P d , gives the selection
data. Normally this is a string encoded in base64. The data becomes the
new selection, which is then available for pasting by other
applications.
If the second parameter is a ? , xterm replies to the host with the selection data encoded using the same protocol.
If the second parameter is neither a base64 string nor ? , then the selection is cleared.
P s = 1 0 4 ; c → Reset Color Number c. It is reset to the color specified by the corresponding X resource. Any number of c parameters may be given. These parameters correspond to the ANSI colors 0-7, their bright versions 8-15, and if supported, the remainder of the 88-color or 256-color table. If no parameters are given, the entire table will be reset.
P s = 1 0 5 ; c → Reset Special Color Number c. It is reset to the color specified by the corresponding X resource. Any number of c parameters may be given. These parameters correspond to the special colors which can be set using an OSC 5 control (or by adding the maximum number of colors using an OSC 4 control).
The dynamic colors can also be reset to their default (resource) values:
P s = 1 1 0 → Reset VT100 text foreground color.
P s = 1 1 1 → Reset VT100 text background color.
P s = 1 1 2 → Reset text cursor color.
P s = 1 1 3 → Reset mouse foreground color.
P s = 1 1 4 → Reset mouse background color.
P s = 1 1 5 → Reset Tektronix foreground color.
P s = 1 1 6 → Reset Tektronix background color.
P s = 1 1 7 → Reset highlight color.
P s = 1 1 8 → Reset Tektronix cursor color.
P s = 1 1 9 → Reset highlight foreground color.
Privacy Message
|
PM P t ST |
xterm implements no PM functions; P t is ignored. P t need not be printable characters. |
Many keyboards have keys labeled "Alt". Few have keys labeled "Meta". However, xterm’s default translations use the Meta modifier. Common keyboard configurations assign the Meta modifier to an "Alt" key. By using xmodmap one may have the modifier assigned to a different key, and have "real" alt and meta keys. Here is an example:
! put meta on mod3 to distinguish it from alt keycode 64 = Alt_L clear mod1 add mod1 = Alt_L keycode 115 = Meta_L clear mod3 add mod3 = Meta_L
The metaSendsEscape resource (and altSendsEscape if altIsNotMeta is set) can be used to control the way the Meta modifier applies to ordinary keys unless the modifyOtherKeys resource is set:
- prefix a key with the ESC character.
- shift the key from codes 0-127 to 128-255 by adding 128.
The table shows the result for a given character "x" with modifiers according to the default translations with the resources set on or off. This assumes altIsNotMeta is set:
If xterm does minimal translation of the function keys, it usually does this with a PC-style keyboard, so PC-style function keys result. Sun keyboards are similar to PC keyboards. Both have cursor and scrolling operations printed on the keypad, which duplicate the smaller cursor and scrolling keypads.
X does not predefine NumLock (used for VT220 keyboards) or Alt (used as an extension for the Sun/PC keyboards) as modifiers. These keys are recognized as modifiers when enabled by the numLock resource, or by the "DECSET 1 0 3 5 " control sequence.
The cursor keys transmit the following escape sequences depending on the mode specified via the DECCKM escape sequence.
The home- and end-keys (unlike PageUp and other keys also on the 6-key editing keypad) are considered "cursor keys" by xterm. Their mode is also controlled by the DECCKM escape sequence:
The application keypad transmits the following escape sequences depending on the mode specified via the DECKPNM and DECKPAM escape sequences. Use the NumLock key to override the application mode.
Not all keys are present on the Sun/PC keypad (e.g., PF1, Tab), but are supported by the program.
They also provide 12 function keys, as well as a few other special-purpose keys:
Older versions of xterm implement different escape sequences for F1 through F4. These can be activated by setting the oldXtermFKeys resource. However, since they do not correspond to any hardware terminal, they have been deprecated. (The DEC VT220 reserves F1 through F5 for local functions such as Setup).
In normal mode, i.e., a Sun/PC keyboard when the sunKeyboard resource is false, xterm recognizes function key modifiers which are parameters appended before the final character of the control sequence.
For example, shift-F5 would be sent as CSI 1 5 ; 2 ~
If the alwaysUseMods resource is set, the Meta modifier also is recognized, making parameters 9 through 16.
However, xterm is most useful as a DEC VT102 or VT220 emulator. Set the sunKeyboard resource to true to force a Sun/PC keyboard to act like a VT220 keyboard.
The VT102/VT220 application keypad transmits unique escape sequences in application mode, which are distinct from the cursor and scrolling keypad:
The VT220 provides a 6-key editing keypad, which is analogous to that on the PC keyboard. It is not affected by DECCKM or DECKPNM/DECKPAM:
The VT220 provides 8 additional function keys. With a Sun/PC keyboard, access these keys by Control/F1 for F13, etc.
A VT52 does not have function keys, but it does have a numeric keypad and cursor keys. They differ from the other emulations by the prefix. Also, the cursor keys do not change:
The keypad is similar:
The xterm program provides support for Sun keyboards more directly, by a menu toggle that causes it to send Sun-style function key codes rather than VT220. Note, however, that the sun and VT100 emulations are not really compatible. For example, their wrap-margin behavior differs.
Only function keys are altered; keypad and cursor keys are the same. The emulation responds identically. See the xterm-sun terminfo entry for details.
Similarly, xterm can be compiled to support HP keyboards. See the xterm-hp terminfo entry for details.
Xterm maintains two screen buffers. The normal screen buffer allows you to scroll back to view saved lines of output up to the maximum set by the saveLines resource. The alternate screen buffer is exactly as large as the display, contains no additional saved lines. When the alternate screen buffer is active, you cannot scroll back to view saved lines. Xterm provides control sequences and menu entries for switching between the two.
Most full-screen applications use terminfo or termcap to obtain strings used to start/stop full-screen mode, i.e., smcup and rmcup for terminfo, or the corresponding ti and te for termcap. The titeInhibit resource removes the ti and te strings from the TERMCAP string which is set in the environment for some platforms. That is not done when xterm is built with terminfo libraries because terminfo does not provide the whole text of the termcap data in one piece. It would not work for terminfo anyway, since terminfo data is not passed in environment variables; setting an environment variable in this manner would have no effect on the application’s ability to switch between normal and alternate screen buffers. Instead, the newer private mode controls (such as 1 0 4 9 ) for switching between normal and alternate screen buffers simply disable the switching. They add other features such as clearing the display for the same reason: to make the details of switching independent of the application that requests the switch.
When bracketed paste mode is set, pasted text
is bracketed with control sequences so that the program can
differentiate pasted text from typed-in text. When bracketed paste mode
is set, the program will receive:
ESC [ 2 0 0 ~ ,
followed by the pasted text, followed by
ESC [ 2 0 1 ~ .
The window- and icon-labels can be set or queried using control sequences. As a VT220-emulator, xterm "should" limit the character encoding for the corresponding strings to ISO-8859-1. Indeed, it used to be the case (and was documented) that window titles had to be ISO-8859-1. This is no longer the case. However, there are many applications which still assume that titles are set using ISO-8859-1. So that is the default behavior.
If xterm is running with UTF-8 encoding, it is possible to use window- and icon-labels encoded using UTF-8. That is because the underlying X libraries (and many, but not all) window managers support this feature.
The utf8Title X resource setting tells xterm to disable a reconversion of the title string back to ISO-8859-1, allowing the title strings to be interpreted as UTF-8. The same feature can be enabled using the title mode control sequence described in this summary.
Separate from the ability to set the titles, xterm provides the ability to query the titles, returning them either in ISO-8859-1 or UTF-8. This choice is available only while xterm is using UTF-8 encoding.
Finally, the characters sent to, or returned by a title control are less constrained than the rest of the control sequences. To make them more manageable (and constrained), for use in shell scripts, xterm has an optional feature which decodes the string from hexadecimal (for setting titles) or for encoding the title into hexadecimal when querying the value.
The VT widget can be set to send the mouse position and other information on button presses. These modes are typically used by editors and other full-screen applications that want to make use of the mouse.
There are two sets of mutually exclusive modes:
|
• |
mouse protocol |
||
|
• |
protocol encoding |
The mouse protocols include DEC Locator mode, enabled by the DECELR CSI P s ; P s ’ z control sequence, and is not described here (control sequences are summarized above). The remaining five modes of the mouse protocols are each enabled (or disabled) by a different parameter in the "DECSET CSI ? P m h " or "DECRST CSI ?
Manifest constants for the parameter values are defined in xcharmouse.h as follows:
#define SET_X10_MOUSE 9 #define SET_VT200_MOUSE 1000 #define SET_VT200_HIGHLIGHT_MOUSE 1001 #define SET_BTN_EVENT_MOUSE 1002 #define SET_ANY_EVENT_MOUSE 1003 #define SET_FOCUS_EVENT_MOUSE 1004 #define SET_EXT_MODE_MOUSE 1005 #define SET_SGR_EXT_MODE_MOUSE 1006 #define SET_URXVT_EXT_MODE_MOUSE 1015 #define SET_ALTERNATE_SCROLL 1007
The motion reporting modes are strictly xterm extensions, and are not part of any standard, though they are analogous to the DEC VT200 DECELR locator reports.
Normally, parameters (such as pointer position and button number) for all mouse tracking escape sequences generated by xterm encode numeric parameters in a single character as value+32.
For example, ! specifies the value 1. The upper left character position
on the terminal is denoted as 1,1. This scheme dates back to X10,
though the normal mouse-tracking (from X11) is more elaborate.
X10 compatbility mode
X10 compatibility mode sends an escape sequence only on button press, encoding the location and the mouse button pressed. It is enabled by specifying parameter 9 to DECSET. On button press, xterm sends CSI M C b C x C y (6 characters).
|
• |
C b is button−1. |
|
|
• |
C x and C y are the x and y coordinates of the mouse when the button was pressed. |
Normal tracking mode
Normal tracking mode sends an escape sequence on both button press and release. Modifier key (shift, ctrl, meta) information is also sent. It is enabled by specifying parameter 1000 to DECSET. On button press or release, xterm sends CSI M C b C x C y .
|
• |
The low two bits of C b encode button information: 0=MB1 pressed, 1=MB2 pressed, 2=MB3 pressed, 3=release. |
|
|
• |
The next three bits encode the modifiers which were down when the button was pressed and are added together: 4=Shift, 8=Meta, 16=Control. Note however that the shift and control bits are normally unavailable because xterm uses the control modifier with mouse for popup menus, and the shift modifier is used in the default translations for button events. The Meta modifier recognized by xterm is the mod1 mask, and is not necessarily the "Meta" key (see xmodmap). |
|
|
• |
C x and C y are the x and y coordinates of the mouse event, encoded as in X10 mode. |
Wheel mice
Wheel mice may return buttons 4 and 5. Those
buttons are represented by the same event codes as buttons 1 and 2
respectively, except that 64 is added to the event code. Release events
for the wheel buttons are not reported. By default, the wheel mouse
events are translated to scroll-back and scroll-forw
actions. Those actions normally scroll the whole window, as if the
scrollbar was used. However if Alternate Scroll mode is set, then cursor
up/down controls are sent when the terminal is displaying the alternate
screen. The initial state of Alternate Scroll mode is set using the alternateScroll resource.
Highlight tracking
Mouse highlight tracking notifies a program of a button press, receives a range of lines from the program, highlights the region covered by the mouse within that range until button release, and then sends the program the release coordinates. It is enabled by specifying parameter 1001 to DECSET. Highlighting is performed only for button 1, though other button events can be received.
Warning: use of this mode requires a cooperating program or it will hang xterm.
On button press, the same information as for normal tracking is generated; xterm then waits for the program to send mouse tracking information. All X events are ignored until the proper escape sequence is received from the pty: CSI P s ; P s ; P s ; P s ; P s T . The parameters are func, startx, starty, firstrow, and lastrow. func is non-zero to initiate highlight tracking and zero to abort. startx and starty give the starting x and y location for the highlighted region. The ending location tracks the mouse, but will never be above row firstrow and will always be above row lastrow. (The top of the screen is row 1.) When the button is released, xterm reports the ending position one of two ways:
|
• |
if the start and end coordinates are the same locations: |
CSI t C x C y .
|
• |
otherwise: |
CSI T C x C y C x C y C x C y .
The parameters are startx, starty, endx, endy, mousex, and mousey.
|
− |
startx, starty, endx, and endy give the starting and ending character positions of the region. |
||
|
− |
mousex and mousey give the location of the mouse at button up, which may not be over a character. |
Button-event tracking
Button-event tracking is essentially the same as normal tracking, but xterm also reports button-motion events. Motion events are reported only if the mouse pointer has moved to a different character cell. It is enabled by specifying parameter 1002 to DECSET. On button press or release, xterm sends the same codes used by normal tracking mode.
|
• |
On button-motion events, xterm adds 32 to the event code (the third character, C b ). |
|
|
• |
The other bits of the event code specify button and modifier keys as in normal mode. For example, motion into cell x,y with button 1 down is reported as CSI M @ C x C y . ( @ = 32 + 0 (button 1) + 32 (motion indicator) ). Similarly, motion with button 3 down is reported as CSI M B C x C y . ( B = 32 + 2 (button 3) + 32 (motion indicator) ). |
Any-event tracking
Any-event mode is the same as button-event
mode, except that all motion events are reported, even if no mouse
button is down. It is enabled by specifying 1003 to DECSET.
FocusIn/FocusOut
FocusIn/FocusOut can be combined with any of the mouse events since it uses a different protocol. When set, it causes xterm to send CSI I when the terminal gains focus, and CSI O when it loses focus.
Extended coordinates
The original X10 mouse protocol limits the C x and C y ordinates to 223 (=255 - 32). Xterm supports more than one scheme for extending this range, by changing the protocol encoding:
|
UTF-8 (1005) |
This enables UTF-8 encoding for C x and C y
under all tracking modes, expanding the maximum encodable position from
223 to 2015. For positions less than 95, the resulting output is
identical under both modes. Under extended mouse mode, positions greater
than 95 generate "extra" bytes which will confuse applications which do
not treat their input as a UTF-8 stream. Likewise, C b will be UTF-8 encoded, to reduce confusion with wheel mouse events.
Under normal mouse mode, positions outside (160,94) result in byte pairs
which can be interpreted as a single UTF-8 character; applications
which do treat their input as UTF-8 will almost certainly be confused
unless extended mouse mode is active.
This scheme has the drawback that the encoded coordinates will not pass through luit unchanged, e.g., for locales using non-UTF-8 encoding.
|
SGR (1006) |
The normal mouse response is altered to use CSI < followed by semicolon-separated encoded button value, the C x and C y ordinates and a final character which is M for button press and m for button release. |
|
• |
The encoded button value in this case does not add 32 since that was useful only in the X10 scheme for ensuring that the byte containing the button value is a printable code. |
||
|
• |
The modifiers are encoded in the same way. |
||
|
• |
A different final character is used for button release to resolve the X10 ambiguity regarding which button was released. |
The highlight tracking responses are also modified to an SGR-like format, using the same SGR-style scheme and button-encodings.
|
URXVT (1015) |
The normal mouse response is altered to use CSI followed by semicolon-separated encoded button value, the C x and C y ordinates and final character M .
This uses the same button encoding as X10, but printing it as a decimal integer rather than as a single byte.
However, CSI M can be mistaken for DL (delete lines), while the highlight tracking CSI
T can be mistaken for SD (scroll down), and the Window manipulation
controls. For these reasons, the 1015 control is not recommended; it is
not an improvement over 1005.
If xterm is configured as VT240, VT241, VT330, VT340 or VT382 using the decTerminalID resource, it supports Sixel Graphics controls, a palleted bitmap graphics system using sets of six vertical pixels as the basic element.
|
CSI P s c |
xterm responds to Send Device Attributes (Primary DA) with these additional codes: |
P s = 4 → Sixel graphics.
|
CSI ? P m h |
xterm has these additional private Set Mode values: |
P s = 8 0 → Sixel scrolling.
P s = 1 0 7 0 → use private color registers for each graphic.
P s = 8 4 5 2 → Sixel scrolling leaves cursor to right of graphic.
|
DCS P a ; P b ; P h q P s ..P s ST |
See
http://vt100.net/docs/vt3xx-gp/chapter14.html
The sixel data device control string has three positional parameters, following the q with sixel data.
P a → pixel aspect ratio
P b → background color option
P h → horizontal grid size (ignored).
P s → sixel data
If xterm is configured as VT125, VT240, VT241, VT330 or VT340 using the decTerminalID resource, it supports Remote Graphic Instruction Set, a graphics description language.
|
CSI P s c |
xterm responds to Send Device Attributes (Primary DA) with these additional codes: |
P s = 3 → ReGIS graphics.
|
CSI ? P m h |
xterm has these additional private Set Mode values: |
P s = 1 0 7 0 → use private color registers for each graphic.
|
DCS P m p P r ..P r ST |
See
http://vt100.net/docs/vt3xx-gp/chapter1.html
The ReGIS data device control string has one positional parameter with four possible values:
P m = 0 → resume command, use fullscreen mode
P m = 1 → start new command, use fullscreen mode
P m = 2 → resume command, use command display mode
P m = 3 → start new command, use command display mode
Most of these sequences are standard Tektronix 4014 control sequences. Graph mode supports the 12-bit addressing of the Tektronix 4014. The major features missing are the write-through and defocused modes. This document does not describe the commands used in the various Tektronix plotting modes but does describe the commands to switch modes.
|
BEL |
Bell (Ctrl-G). |
|
|
BS |
Backspace (Ctrl-H). |
|
|
TAB |
Horizontal Tab (Ctrl-I). |
|
|
LF |
Line Feed or New Line (Ctrl-J). |
|
|
VT |
Cursor up (Ctrl-K). |
|
|
FF |
Form Feed or New Page (Ctrl-L). |
|
|
CR |
Carriage Return (Ctrl-M). |
|
|
ESC ETX |
Switch to VT100 Mode ( ESC Ctrl-C). |
|
|
ESC ENQ |
Return Terminal Status ( ESC Ctrl-E). |
|
|
ESC FF |
PAGE (Clear Screen) ( ESC Ctrl-L). |
|
|
ESC SO |
Begin 4015 APL mode ( ESC Ctrl-N). (This is ignored by xterm). |
|
|
ESC SI |
End 4015 APL mode ( ESC Ctrl-O). (This is ignored by xterm). |
|
|
ESC ETB |
COPY (Save Tektronix Codes to file COPYyyyy-mm-dd.hh:mm:ss). |
ETB (end transmission block) is the same as Ctrl-W.
|
ESC CAN |
Bypass Condition ( ESC Ctrl-X). |
|
|
ESC SUB |
GIN mode ( ESC Ctrl-Z). |
|
|
ESC FS |
Special Point Plot Mode ( ESC Ctrl-\). |
|
|
ESC 8 |
Select Large Character Set. |
|
|
ESC 9 |
Select #2 Character Set. |
|
|
ESC : |
Select #3 Character Set. |
|
|
ESC ; |
Select Small Character Set. |
|
|
OSC P s ; P |
t BEL
|
Set Text Parameters of VT window. |
P s = 0 → Change Icon Name and Window Title to P t .
P s = 1 → Change Icon Name to P t .
P s = 2 → Change Window Title to P t .
P s = 4 6 → Change Log File to P t . (This is normally disabled by a compile-time option).
|
ESC ` |
Normal Z Axis and Normal (solid) Vectors. |
||
|
ESC a |
Normal Z Axis and Dotted Line Vectors. |
||
|
ESC b |
Normal Z Axis and Dot-Dashed Vectors. |
||
|
ESC c |
Normal Z Axis and Short-Dashed Vectors. |
||
|
ESC d |
Normal Z Axis and Long-Dashed Vectors. |
||
|
ESC h |
Defocused Z Axis and Normal (solid) Vectors. |
||
|
ESC i |
Defocused Z Axis and Dotted Line Vectors. |
||
|
ESC j |
Defocused Z Axis and Dot-Dashed Vectors. |
||
|
ESC k |
Defocused Z Axis and Short-Dashed Vectors. |
||
|
ESC l |
Defocused Z Axis and Long-Dashed Vectors. |
||
|
ESC p |
Write-Thru Mode and Normal (solid) Vectors. |
||
|
ESC q |
Write-Thru Mode and Dotted Line Vectors. |
||
|
ESC r |
Write-Thru Mode and Dot-Dashed Vectors. |
||
|
ESC s |
Write-Thru Mode and Short-Dashed Vectors. |
||
|
ESC t |
Write-Thru Mode and Long-Dashed Vectors. |
||
|
FS |
Point Plot Mode (Ctrl-\). |
||
|
GS |
Graph Mode (Ctrl-]). |
||
|
RS |
Incremental Plot Mode (Ctrl-^). |
||
|
US |
Alpha Mode (Ctrl-_). |
Parameters for cursor movement are at the end of the ESC Y escape sequence. Each ordinate is encoded in a single character as value+32. For example, ! is 1. The screen coordinate system is 0-based.
|
ESC A |
Cursor up. |
|
|
ESC B |
Cursor down. |
|
|
ESC C |
Cursor right. |
|
|
ESC D |
Cursor left. |
|
|
ESC F |
Enter graphics mode. |
|
|
ESC G |
Exit graphics mode. |
|
|
ESC H |
Move the cursor to the home position. |
|
|
ESC I |
Reverse line feed. |
|
|
ESC J |
Erase from the cursor to the end of the screen. |
|
|
ESC K |
Erase from the cursor to the end of the line. |
|
|
ESC Y P s P |
s
|
Move the cursor to given row and column. |
|||
|
ESC Z |
Identify. |
→ ESC / Z (‘‘I am a VT52.’’).
|
ESC = |
Enter alternate keypad mode. |
||
|
ESC > |
Exit alternate keypad mode. |
||
|
ESC < |
Exit VT52 mode (Enter VT100 mode). |


The Fat Boy 2018 is the best Fat Boy they have come out with yet with loads of new fetures like: Satin chrome finishes, Steamroller stance, Milwaukee-eight big twin engine, Signature LED forward lighting, All-new softail frame and high performance front suspension and rear mono shock.
The Deluxe 2018 comes with loads of new features such as the retro-modern LED lights, 107 v-twin engine and many more cool new features.
The 2018 Fat Bob comes with loads of cool new features a small selection of these are, Inverted forks, dual disk front brakes, 2-1-2 exaust and many more features that will want any motorbike guy want one.
The Heritage Classic 2018 is the best Classic they have come out with yet with loads of new fetures like: Detachable windscreen, cruise control, Milwaukee-eight big twin engine, Signature LED forward lighting, All-new softail frame and high performance front suspension and rear mono shock.
The Iron 883 comes with loads of new features like, low seat, slammed suspension, tuck and roll seat, 9-spoke wheels and loads more cool features.


Coding Falcons
Home
About Us
Sessions
Student profiles
Coding Falcons is a Web Development program for students in grades 5th - 8th grade.
Student profiles
Coding Falcons is a Web Development program for students in grades 5th - 8th grade.


@headerSignup()
Dashboard
Restaurants
Locations
Categories
Users
Location successfully created!
Location already exists!!!
@footer()


The Java Sound API is a low-level API for effecting and controlling input and output of audio media. It provides explicit control over the capabilities commonly required for audio input and output in a framework that promotes extensibility and flexibility.
Because sound is so fundamental, Java Sound fulfills the needs of a wide range of customers. Potential application areas include:
Java Sound enables applications to extend audio support with specialized capabilities, and integrates well with architectures that provide higher-level interfaces and integration with other media types.
Java Sound provides the lowest level of audio support on the Java platform. It provides a high degree of control over audio-specific functionality. For example, it provides mechanisms for installing, accessing, and manipulating system resources such as digital audio and MIDI (Musical Instrument Digital Interface) devices. It does not include sophisticated sound editors and GUI tools; rather, it provides a set of capabilities upon which such applications can be built. It emphasizes low-level control beyond that commonly expected by the end user, who benefits from higher-level interfaces built on top of Java Sound.
Note: Throughout this document, the word "application" refers generically to Java applets as well as Java applications.
The Java Sound API includes support for both digital audio and MIDI data. These two major modules of functionality are provided in separate packages:
javax.sound.sampled
This package specifies interfaces for capture, mixing, and playback
of digital (sampled) audio.
javax.sound.midi
This package provides interfaces for MIDI synthesis, sequencing,
and event transport.
Two other packages permit service providers (as opposed to application developers) to create custom components that can be installed on the system:
The next section of this document discusses the sampled-audio system, including an overview of the javax.sound.sampled API. The final section covers the MIDI system and the javax.sound.midi API.
The javax.sound.sampled package handles digital audio data, also referred to as sampled audio. ("Samples" refer to successive snapshots of a signal, which in the case of digital audio is a sound wave. For example, the audio recorded for storage on compact discs is sampled 44100 times per second. Typically, sampled audio comes from a sound recording, but the sound could instead be synthetically generated. The term "sampled audio" refers to the type of data, not its origin. Sampled audio can be thought of as the sound itself, whereas MIDI data can be thought of as a recipe for creating musical sound.)
Java Sound does not assume a specific audio hardware
configuration; it is designed to allow different sorts of audio
components to be installed on a system and accessed by the API.
Java Sound supports common functionality such as input and output
from a sound card (for example, for recording and playback of sound
files) as well as mixing of multiple streams of audio. Here is one
example of a typical audio architecture for which Java Sound might
be used:
In this example, a device such as a sound card has various input and output ports, and mixing is provided in software. The MIDI synthesizer shown as one of the mixer???s audio inputs might also be a feature of the sound card, or it might be implemented in software. (The javax.sound.midi package, discussed later, supplies a Java interface for synthesizers.)
The major concepts used in the javax.sound.sampled package are described in the sections below.
A line is an element of the digital audio "pipeline," such as an audio input or output port, a mixer, or an audio data path into or out of a mixer. The audio data flowing through a line can be mono or multichannel (for example, stereo). Each type of line will be described shortly, but first some of their functional relationships will be illustrated, showing the flow of audio through the "pipeline." The following diagram shows different types of lines in a simple audio-output system:
A Possible Configuration of Lines for Audio OutputIn this example, an application has asked a mixer for one or more available clips and source data lines. A clip is a mixer input into which you can load audio data prior to playback; a source data line is a mixer input that accepts a real-time stream of audio data. The application preloads audio data from a sound file into the clips, and then pushes other audio data into the source data lines. The mixer reads data from these lines, each of which may have its own reverberation, gain, and pan controls, and uses the reverb settings to mix the "dry" audio signals with the reverberated ("wet") mix. The mixer delivers its final output to one or more output ports, such as a speaker, a headphone jack, and a line-out jack.
Although the various lines are depicted as separate rectangles in the diagram, they are all "owned" by the mixer, and can be considered integral parts of the mixer. The reverb, gain, and pan rectangles represent processing controls (rather than lines) that can be applied by the mixer to data flowing through the lines. (Note that this is just one example of a possible audio system that is supported by the API. Not all audio configurations will have all the features illustrated. An individual source data line might not support panning, a mixer might not implement reverb, and so on.)
A simple audio-input system might be similar:
A Possible Configuration of Lines for Audio InputHere, data flows in to the mixer from one or more input ports, commonly the microphone or the line-in jack. Gain and pan are applied, and the mixer delivers the captured data to an application via the mixer's target data line. A target data line is a mixer output, containing the mixture of the streamed input sounds. The simplest mixer has just one target data line, but some mixers can deliver captured data to multiple target data lines simultaneously.
The different types of line will now be examined more closely. Several types of line are defined by subinterfaces of the basicLine
interface. The interface hierarchy is shown
below.
The Line Interface Hierarchy
The base interface, Line
, describes the
minimal functionality common to all lines:
Line.Info
) that indicates what mixer (if any) sends
its mixed audio data as output directly to the line, and what mixer
(if any) gets audio data as input directly from the line.
Subinterfaces of Line
may have corresponding
subclasses of Line.Info
that provide other kinds of
information specific to the particular types of line.Closing a line indicates that any resources used by the line may now be released. To free up resources, applications should close lines whenever they are not in use, and must close all opened lines when exiting.
Mixers are assumed to be shared system resources, and can be opened and closed repeatedly. Other lines may or may not support re-opening once they have been closed. Mechanisms for opening lines vary with the different sub-types and are documented where they are defined.
LineEvent
class. Two types of
LineEvent
are OPEN
and
CLOSE
, but subinterfaces of Line
can
introduce other types of events.OPEN
or CLOSE
event, the event is sent to all objects that have registered to
"listen" for events on that line. Such objects must
implement the LineListener
interface. An application
can create these objects, register them to listen for line events,
and react to the events as desired.Ports
are simple
lines for input or output of audio to or from audio devices. The
Port
interface has an inner class,
Port.Info
, that specifies the type of port. Some
common types are the microphone, line input, CD-ROM drive, speaker,
headphone, and line output.The Mixer
interface represents a hardware or
software device that has one or more input lines and one or more
output lines. This definition means that a mixer need not actually
mix data; it might have only a single input. The Mixer
API is intended to encompass a variety of devices, but the typical
case supports mixing.
The Mixer
interface provides methods for obtaining
a mixer's lines. These can include target data lines, from which an
application can read captured audio data, source data lines, to
which an application can write audio data for playback (rendering),
and clips, in which an application can preload sound data for
playback. The mixer can lock these resources. For example, if the
mixer has only one target data line and it is already in use, an
attempt by an application to obtain a target data line will cause
an exception to be thrown.
You can query a mixer for lines of different types, by passing
the appropriate type of Line.Info
. You can also ask
the mixer how many lines of a particular type it supports.
A mixer maintains textual information about its specific device
type in an inner class called Mixer.Info
. This
information include the product's name, version, and vendor, along
with a textual description.
Notice that the generic Line
interface does not
provide a means to start and stop playback or recording. For that
you need a data line. The DataLine
interface
supplies the following additional media-related features beyond
those of a Line
:
AudioFormat
) specifies the
arrangement of the bytes in the audio stream. Some of the format's
properties are the number of channels, the sample rate, the sample
size, and the encoding technique. Common encoding techniques
include linear pulse-code modulation (PCM), mu-law encoding, and
a-law encoding.START
and STOP
events are produced when
active presentation or capture of data from or to the data line
starts or stops.An application can obtain a data line from a mixer. If the data line cannot be allocated because of resource constraints (for example, if the mixer supports only one target data line and it is already in use), an exception is thrown.
A TargetDataLine
receives audio data from a
mixer. Commonly, the mixer has captured audio data from a port such
as a microphone; it might process or mix this captured audio before
placing the data in the target data line's buffer. The
TargetDataLine
interface provides methods for reading
the data from the target data line's buffer and for determining how
much data is currently available for reading. If an application
attempts to read more data than is available, the read method
blocks until the requested amount of data is available. This
applies even if the amount of data requested is greater than the
line's buffer size. The read method returns if the line is closed,
paused, or flushed.
Applications recording audio should read data from the target data
line fast enough to avoid overflow of the buffer, which results in
discontinuities in the captured data. If the buffer does overflow,
the oldest queued data is discarded and replaced by new
data.
A SourceDataLine
receives audio data for
playback. It provides methods for writing data to the source data
line's buffer for playback, and for determining how much data the
line is prepared to receive without blocking. If an application
attempts to write more data than is available, the read method
blocks until the requested amount of data can be written. This
applies even if the amount of data requested is greater than the
line's buffer size. The write method also returns if the line is
closed, paused, or flushed.
Applications playing audio should write data to the source data
line fast enough to avoid underflow (emptying) of the buffer, which
may result in discontinuities in audio playback. If audio playback
stops due to underflow, a STOP
event is generated. A
START
event is generated when presentation
resumes.
A Clip
is a data line into which audio data
can be loaded prior to playback. Because the data is pre-loaded
rather than streamed, the clip???s duration is known before playback,
and you can choose any starting position in the media. Clips can be
looped, meaning that upon playback, all the data between two
specified loop points will repeat a specified number of times, or
indefinitely.
GroupLine
is a synchronized group of data
lines. If a mixer supports group lines, you can specify which data
lines should be treated as a group. Then you can start, stop, or
close all those data lines by sending a single message to the
group, instead of having to control each line individually.Data lines and ports often have a set of controls that affect
the audio signal passing through the line. The way in which the
signal is affected depends on the type of control. The Java Sound
API defines the following subclasses of Control
:
GainControl
GainControl
object can be queried for its resolution and for the minimum and
maximum gain values it permits. The resolution is expressed as the
number of increments over which the range of possible values is
distributed.PanControl
ReverbControl
SampleRateControl
GainControl
, the change can be made gradually instead
of immediately, and the control can be queried for its resolution
and its minimum and maximum possible values.Programmatically, you obtain a particular control object from a line through a reference to the control???s class. You can also obtain an array of all the controls for that line.
AudioSystem
class serves as an application's entry
point for accessing the installed sampled-audio resources. You can
query the AudioSystem to learn what sorts of audio components have
been installed, and then you can obtain access to them. For
example, an application might start out by asking the
AudioSystem
class whether there is a mixer that has a
certain configuration, such as one of the input or output
configurations illustrated earlier in the discussion of lines. From
the mixer, the application would then obtain data lines, and so on.
Here are some of the resources an application can obtain from
the AudioSystem
:
Mixer.Info
object. You can learn what mixers are
available by invoking the getMixerInfo
method, which
returns an array of Mixer.Info
objects.AudioSystem
, without dealing
explicitly with mixers.An application can use format conversions to translate audio
data from one format to another. (See the discussion of AudioFormat above.) Format conversions
are often used to compress and decompress audio data. An
application can query the AudioSystem
to learn what
translations are supported. It can then pass the
AudioSystem
a stream of audio data and get back a
translated stream in a particular format.
An audio stream is an input stream with a specified audio data
format (AudioFormat
) and data length. The
AudioInputStream
class represents such a stream, from
which you can read bytes. Some audio input streams permit you to
remember positions in the stream and skip around in it. The
AudioSystem
class provides methods for translating
between audio files and audio streams. The AudioSystem
can also report the file format of a sound file and can write files
in the different formats. A file format is represented by the
AudioFileFormat
class. An AudioFileFormat
includes an AudioFormat
, the file's length, and its
type (WAV, AIFF, AU, etc.).
Service provider interfaces for the sampled audio system are
defined in the javax.sound.sampled.spi
package.
Service providers can extend the classes defined here so that their
own audio devices, sound file parsers and writers, and format
converters can be installed and made available by a Java Sound
implementation.
Interfaces describing MIDI event transport, synthesis, and
sequencing are defined in the javax.sound.midi
package. The major concepts used in the package are described in
the sections below.
The diagram below illustrates the functional relationships
between the major components in a typical Java Sound MIDI
configuration. (Java Sound permits a variety of devices to be
installed and interconnected. The system shown here is just one
possible scenario.) The flow of data between components is
indicated by arrows. The data can be in a standard file format, or
(as indicated by the key in the lower right corner of the diagram),
it can be audio, raw MIDI bytes, or Java Sound's
MidiEvent
objects.
In this example, the application prepares a musical performance
by loading a musical score that is stored as a Standard MIDI File
on a disk (lower left corner of the diagram). Standard MIDI files
contain tracks, each of which is a list of time-tagged MIDI events.
This MIDI file is read into a Sequence
object, whose
data structure reflects the file. A Sequence
contains
a set of Track
objects, each of which contains a set
of MidiEvent
objects. The Sequence
is
then "performed" by a Sequencer
. A
Sequencer
performs its music by sending
MidiEvents
to some other device, such as an internal
or external synthesizer.
As illustrated, MidiEvents
must be translated into
raw (non-time-tagged) MIDI before being sent through a MIDI output
port to an external synthesizer.
Similarly, raw MIDI data coming into the computer from an external
MIDI source is translated into MidiEvents
by a
StreamParser
.
The internal synthesizer (the rectangle marked "Synthesizer" in
the diagram) accepts MidiEvents
directly from the
Sequencer
or StreamParser
. It parses each
event and usually dispatches a corresponding command (such as
noteOn
) to one of its MidiChannel
objects, according to the MIDI channel number specified in the
event. (The MIDI Specification calls for 16 MIDI channels, so a
Synthesizer
typically has 16 MidiChannel
objects.)
The MidiChannel
uses the note information in these
messages to synthesize music. For example, a noteOn
message specifies the note's pitch and "velocity" (volume).
However, the note information is insufficient; the synthesizer also
requires precise instructions on how to create the audio signal for
each note. These instructions are represented by an
Instrument
. Each Instrument
typically
emulates a different real-world musical instrument or sound effect.
The Instruments
might come as presets with the
synthesizer, or they might be loaded from soundbank files. In the
synthesizer, the Instruments
are arranged by bank
number (the rows in the diagram) and program number (the columns).
An Instrument
can make use of stored digital audio,
included as Sample
objects in the soundbank. For
example, to play the sound of a trumpet playing a 5-second-long
note, the synthesizer might loop (cycle) through a half-second
snippet of a recording of a trumpet.
Now that the components have been introduced from a functional perspective, we will take a brief look at the API from a programmatic perspective.
A MidiEvent
object specifies the type, data length,
and status byte of the raw MIDI message for which it serves as a
wrapper. In addition, it provides a tick value that is used by
devices involved in MIDI timing, such as sequencers.
There are three categories of events, each represented by a
MidiEvent
subclass:
ShortEvents
are the most common and have at most
two data bytes following the status byte.SysexEvents
contain system-exclusive MIDI
messages. They may have many bytes, and generally contain
manufacturer-specific instructions.MetaEvents
occur in MIDI files, but not in raw
MIDI data streams. Meta events contain data, such as lyrics or
tempo settings, that might be useful to sequencers but are usually
meaningless for synthesizers.The base interface for devices is MidiDevice
. All
devices provide methods for listing the set of MIDI modes that they
support, and for querying and setting the current mode. (The mode
is a combination of MIDI's Omni mode and Mono/Poly mode.) Devices
can be opened and closed, and they provide descriptions of
themselves through a MidiDevice.Info
object.
The following diagram illustrates the MidiDevice
interface hierarchy. Also depicted are two classes, connected by
dashed lines to the MidiDevice
interfaces they
implement.
Devices are generally either transmitters or receivers of
MidiEvents
. The Transmitter
subinterface
of MidiDevice
includes methods for setting and
querying the receivers to which the transmitter is sending
MidiEvents
. From the perspective of a transmitter,
these receivers fall into two categories: MIDI Out and MIDI Thru.
The transmitter sends events that it generates itself to its MIDI
Out receivers. If the transmitter is itself also a receiver, it
passes along events that it has received from elsewhere to its MIDI
Thru receivers. The Receiver
subinterface of
MidiDevice
consists of a single method for receiving
MidiEvents
. Typically, this method is invoked by a
Transmitter
.
Java Sound includes concrete classes for converting between
MidiEvent
objects and the raw byte stream used in MIDI
wire protocol. A StreamGenerator
is a
Receiver
that accepts MidiEvent
objects
from a Transmitter
and writes out a raw MIDI byte
stream. Similarly, a StreamParser
is a
Transmitter
that accepts a raw MIDI byte stream and
writes the corresponding MidiEvent
objects to its
Receiver
.
A Synthesizer
is a type of MidiDevice
that generates sound. The Synthesizer
interface
extends both Receiver
and Transmitter
. It
provides methods for manipulating soundbanks and instruments. In
addition, it provides access to a set of MIDI channels through
which sound is actually produced. A Synthesizer
receives MidiEvents
and invokes corresponding
MidiChannel
messages.
MidiChannels
have methods representing the common
MIDI voice messages such as "note on" and "control change." They
also permit queries of the channel's current state.
Like Synthesizer
, the Sequencer
interface extends both Transmitter
and
Receiver
(and therefore MidiDevice
).
Sequencer
adds methods for basic MIDI sequencing
operations.  An
application can register to be notified when the sequencer
processes MetaEvents
and controller events. (A
controller event occurs when a MIDI controller, such as a
pitch-bend wheel or a data slider, changes its value. These events
are not MidiEvents
, but are created when the
Sequencer
encounters certain ShortEvents
in the Sequence
.)
The Sequence
object represents a MIDI sequence as
one or more tracks and associated timing information. A track
contains a list of time-stamped MIDI events. Sequences can be read
from MIDI files, or created from scratch and edited by adding
Tracks
to the Sequence
(or removing
them). Similarly, MidiEvents
can be added to or
removed from the Tracks
.
Tracks
to the Sequence
(or
removing them). Similarly, MidiEvents
can be added to
or removed from the Tracks
.
It is not necessary to load a MIDI file into a
Sequence
object before playing the file. The
setSequence(java.io.InputStream)
method of
Sequencer
lets you read a MIDI file directly into a
Sequencer
, without creating a Sequence
object first.
MidiSystem
acts as an application's entry point to
the MIDI music system. It provides information about, and access
to, the set of installed devices, including transmitters,
receivers, synthesizers, and sequencers.
The MidiSystem
class provides methods for reading
MIDI files to create Sequence
objects, and for writing
Sequences
to MIDI files. A MIDI Type 0 file contains
only one track, while a Type 1 file may contain any number.
MidiSystem
also provides methods to create
Soundbank
objects by parsing soundbank files.
Configuration of the MIDI system is handled in the
javax.sound.midi.spi package
. The abstract classes in
this package allow service providers to supply and install their
own MIDI devices, MIDI file readers and writers, and soundbank file
readers.


Data Engineer with Python (21 840 - 26 880 PLN net/month - B2B, Remote)
There was a problem redirecting you, here's our
offer


Bala Box Office: On Its Way To The 100 Crore Club, Topples 9 Movies In Top 100 Grossers
It has entered the list of Koimoi's All Time Grossers which consists of top 100 movies (since 2008).
by Koimoi.com TeamBala Box Office: Bala is all set to become Ayushmann Khurrana’s third movie to enter 100 crore club after Badhaai Ho and Dream Girl but it’s already making huge turn around in the chart of Koimoi’s All Time Grossers.
Bala has completed its 11 days theatrical run and earned 92.99 crores at the ticket windows. It has entered the list of Koimoi’s All Time Grossers which consists of top 100 movies (since 2008). It took over 9 movies including- OMG- Oh My God! (81.50 crores), Brothers (82.47 crores), Veere Di Wedding (83 crores), Fan (85 crores), Aashiqui 2 (85.40 crores), Gabbar Is Back (86 crores), Badla (88.02 crores), Satyameva Jayate (89.05 crores) and Singh Is Bliing (90.25 crores). By tomorrow it will go past Talaash (93 crores) and Luka Chuppi (94.15 crores).
Check out the complete list below:
(Please rotate your mobile screen for best viewing)
| Film ( since 2012) | Year | Collection |
|---|---|---|
| Baahubali 2: The Conclusion (Hindi) | 2017 | 511.30 |
| Dangal | 2016 | 387.39 |
| Sanju | 2018 | 341.22 |
| PK | 2014 | 339.50 |
| Tiger Zinda hai | 2017 | 339.16 |
| Bajrangi Bhaijaan | 2015 | 320.34 |
| War | 2019 | 317.77* |
| Sultan | 2016 | 300.45 |
| Padmaavat | 2018 | 300.26 |
| Dhoom 3 | 2013 | 280.25 |
| Kabir Singh | 2019 | 278.24 |
| Uri: The Surgical Strike | 2019 | 244.06 |
| Krissh 3 | 2013 | 240.50 |
| Simmba | 2018 | 240.22 |
| Kick | 2014 | 233.00 |
| Chennai Express | 2013 | 226.70 |
| Bharat | 2019 | 209.36 |
| Prem Ratan Dhan Payo | 2015 | 207.40 |
| Golmaal Again | 2017 | 205.72 |
| Happy New Year | 2014 | 205.00 |
| Housefull 4 | 2019 | 206.00* |
| 3 Idiots | 2009 | 202.00 |
| Mission Mangal | 2019 | 200.16 |
| Ek Tha Tiger | 2012 | 198.00 |
| Yeh Jawaani Hai Deewani | 2013 | 190.03 |
| 2.0 (Hindi) | 2018 | 188.00 |
| Bajirao Mastani | 2015 | 184.00 |
| Bang Bang | 2014 | 181.03 |
| Race 3 | 2018 | 169.00 |
| Baaghi 2 | 2018 | 165.00 |
| Dabangg 2 | 2012 | 158.50 |
| Total Dhamaal | 2019 | 154.30 |
| Kesari | 2019 | 153.00 |
| Tanu Weds Manu Returns | 2015 | 152.00 |
| Chhichhore | 2019 | 150.36 |
| Saaho | 2019 | 148.50 |
| Dilwale | 2015 | 148.00 |
| Super 30 | 2019 | 146.10 |
| Thugs Of Hindostan | 2018 | 145.29 |
| Bodyguard | 2011 | 142.00 |
| Singham Returns | 2014 | 141.00 |
| Dream Girl | 2019 | 139.70 |
| Gully Boy | 2019 | 139.38 |
| Dabangg | 2010 | 139.00 |
| Judwaa 2 | 2017 | 138.00 |
| Raees | 2017 | 137.51 |
| Badhaai Ho | 2018 | 136.80 |
| Toilet: Ek Prem Katha | 2017 | 133.60 |
| M.S. Dhoni- The Untold Story | 2016 | 133.04 |
| Rowdy Rathore | 2012 | 131.00 |
| Stree | 2018 | 129.67 |
| Airlift | 2016 | 129.00 |
| Rustom | 2016 | 127.49 |
| Kaabil | 2017 | 126.58 |
| Raazi | 2018 | 123.17 |
| Agneepath | 2012 | 123.05 |
| Tubelight | 2017 | 121.25 |
| Jab Tak Hai Jaan | 2012 | 120.65 |
| Baahubali: The Beginning | 2015 | 120.00 |
| Barfi! | 2012 | 120.00 |
| Ready | 2011 | 120.00 |
| Jolly LLB 2 | 2017 | 117.00 |
| Badrinath Ki Dulhania | 2017 | 116.60 |
| Housefull 2 | 2012 | 114.00 |
| Ghajini | 2008 | 114.00 |
| Holiday | 2014 | 112.65 |
| Ae Dil Hai Mushkil | 2016 | 112.50 |
| Jai Ho | 2014 | 111.00 |
| Goliyon Ki Raasleela Ramleela | 2013 | 110.00 |
| Sonu Ke Titu Ki Sweety | 2018 | 108.71 |
| Housefull 3 | 2016 | 107.70 |
| Gold | 2018 | 107.37 |
| ABCD 2 | 2015 | 107.00 |
| Ek Villain | 2014 | 105.50 |
| Son Of Sardaar | 2012 | 105.03 |
| 2 States | 2014 | 104.00 |
| Bhaag Milkha Bhaag | 2013 | 103.50 |
| Grand Masti | 2013 | 102.50 |
| De De Pyaar De | 2019 | 102.40 |
| Bol Bachchan | 2012 | 102.00 |
| Race 2 | 2013 | 102.00 |
| Raid | 2018 | 101.54 |
| Shivaay | 2016 | 100.35 |
| Zero | 2018 | 97.50 |
| Batla House | 2019 | 97.18 |
| Welcome back | 2015 | 97.00 |
| Baby | 2015 | 95.50 |
| Manikarnika: The Queen Of Jhansi | 2019 | 94.92 |
| Luka Chuppi | 2019 | 94.15 |
| Talaash | 2012 | 93.00 |
| Bala | 2019 | 92.99* |
| Singh Is Bliing | 2015 | 90.25 |
| Satyameva Jayate | 2018 | 89.05 |
| Badla | 2019 | 88.02 |
| Gabbar Is Back | 2015 | 86.00 |
| Aashiqui 2 | 2013 | 85.40 |
| Fan | 2016 | 85.00 |
| Veere Di Wedding | 2018 | 83.00 |
| Brothers | 2015 | 82.47 |
| OMG- Oh My God! | 2012 | 81.50 |
From the success of Bala, it could be well said now that Ayushmann has decoded the formula of striking gold on both critical and commercial front.
Ayushmann recently posted a three-minute video for the men’s grooming brand the Man Company, where he shunned many misplaced notions about what men should be like, which society continues to harbour.
In the video titled “What Makes A True Gentleman”, the actor draws from personal experiences to make his point.


Senator ends effort to name stretch of Route 66 after Trump
TULSA, Okla. (AP) - A Republican lawmaker from Oklahoma has abandoned his effort to rename a stretch of Route 66 after President Donald Trump.
State Sen. Nathan Dahm told the Tulsa World on Wednesday that he’s done trying to rename the 4-mile (6.44-kilometer) stretch of the iconic highway in northeastern Oklahoma after Trump.
The Oklahoma Route 66 Association and Lt. Gov. Matt Pinnell both swiftly rejected naming sections of Route 66 after Trump or any other political figure.
Pinnell, who oversees Oklahoma’s marketing and branding, and others have been working to establish the route of the former U.S. 66 for tourism. Pinnell says a “uniform branding” will soon be rolled out.
State Rep. Ben Loring, who represents the district where the proposed stretch of highway is located, says it could have adversely impacted tourism.
Information from: Tulsa World, http://www.tulsaworld.com
Sign up for Daily Newsletters
Copyright © 2019 The Washington Times, LLC.
Please read our comment policy before commenting.


foo
I'm Prasanth
a web developer.
I'm a web developer. I have a passion for web design and love to create for web and mobile devices.
This webpage is developed using Angular 2.
I'm a developer, so I know how to create your website to run across devices using the latest technologies available.
Now the page uploaded for testing.
foo


[§174C-55] Duration of permits. Each permit for water use in a designated water management area shall be valid until the designation of the water management area is rescinded, unless revoked as provided in section 174C-58 or modified as provided in section 174C-57. [L 1987, c 45, pt of §2]