Lines Matching +full:left +full:- +full:shifted
3 .\" Copyright 2018-2023,2024 Thomas E. Dickey *
32 .TH user_caps 5 2024-03-16 "ncurses @NCURSES_MAJOR@.@NCURSES_MINOR@" "File formats"
49 user_caps \-
50 user-defined \fIterminfo\fR capability format
52 .B @INFOCMP@ \-x
54 .B @TIC@ \-x
76 and reverse-engineering the compiled terminfo files to match the binary format.
79 copy the SVr2 binary format, which uses 16-bit signed integers,
80 and is limited to 4096-byte entries.
97 databases for AIX, HP-UX or OSF/1,
98 rather than the default Solaris-like configuration.
101 the terminal database is defined at compile-time using a text file
104 In principle, the text-file can be extended,
106 The text-file used in \fI\%ncurses\fP for terminal capabilities includes
136 The limitation to 16-bit signed integers was also mentioned.
147 These are referred to as \fIuser-defined capabilities\fP because no
151 command-line option \*(``\-x\*('' to control whether the nonstandard
156 When compiling a terminal database, if \*(``\-x\*('' is set,
157 \fB@TIC@\fP will store a user-defined capability if the capability name is not
161 these user-defined capabilities may be visible to termcap applications:
164 requires that the capability names are 2-characters.
167 it is provided as a 2-character name.
170 user-defined capabilities which refer to features not usable in termcap,
176 Some terminals can send distinct strings for special keys (cursor-,
177 keypad- or function-keys) depending on modifier keys (shift, control, etc.).
178 While terminfo and termcap have a set of 60 predefined function-key names,
183 to provide extended special-key names.
185 Fitting that into termcap's limitation of 2-character names
189 The \fI\%ncurses\fP library uses the user-definable capabilities.
246 as a slash-separated list of decimal integers.
257 asserts that \fI\%ncurses\fP must use Unicode values for line-drawing
260 when the locale uses UTF-8 encoding.
268 override \fI\%ncurses\fP's built-in string which
293 The terminal database uses building-blocks for the various xterm mouse
300 information to make the mouse support completely data-driven.
307 y-ordinate
310 x-ordinate
319 y-ordinate starting region
322 x-ordinate starting region
325 y-ordinate ending region
328 x-ordinate ending region
342 xterm+sm+1006|xterm SGR-mouse,
357 distinct special-key strings.
367 and that shifted special keys use uppercase letters in their names,
378 kDC shifted kdch1 (delete character)
380 kDN shifted kcud1 (cursor down)
381 kEND shifted kend (end)
382 kHOM shifted khome (home)
383 kLFT shifted kcub1 (cursor back)
384 kNXT shifted knext (next)
385 kPRV shifted kprev (previous)
386 kRIT shifted kcuf1 (cursor forward)
387 kUP shifted kcuu1 (cursor up)
396 interpret \*(``backward\*('' as \*(``left\*('',
429 which \fI\%ncurses\fP will allocate at runtime to \fIkey-codes\fP.
437 ask \fBkey_defined\fP(3X) for the \fIkey-code\fP which
441 The \*(``\-x\*('' extension feature of \fB@TIC@\fP and \fB@INFOCMP@\fP
443 That implementation stores user-defined capabilities,
456 .I "NCURSES USER-DEFINABLE CAPABILITIES"
457 summarizes commonly-used user-defined capabilities