Lines Matching +full:128 +full:- +full:character
3 .\" Copyright 2018-2023,2024 Thomas E. Dickey *
4 .\" Copyright 1998-2015,2017 Free Software Foundation, Inc. *
32 .TH curs_util 3X 2024-04-20 "ncurses @NCURSES_MAJOR@.@NCURSES_MINOR@" "Library calls"
60 \fB\%wunctrl\fP \-
88 The \fBunctrl\fP routine returns a character string which is a printable
89 representation of the character \fIch\fP:
92 e.g., a one-character string containing the key.
98 DEL (character 127) is displayed as \fB^?\fP.
100 Values above 128 are either meta characters
103 shown in the \fBM\-\fIX\fR notation,
109 a complex character \fIwch\fP.
112 with the character parameter are ignored.
114 The \fBkeyname\fP routine returns a character string
116 Key codes are different from character codes.
124 Otherwise (if there is no corresponding name and the key is not a character)
130 a multibyte character string corresponding
131 to the wide-character value \fIw\fP.
135 \fBkeyname\fP returns null where \fBkey_name\fP would display a meta character.
164 in-memory copy of the terminal information.
209 \fI\%ncurses\fP re-fetches the value of the environment variables so
250 and its associated character cells.
251 The format differs between the wide-character (\fI\%ncursesw\fP) and
252 non-wide (\fI\%ncurses\fP) libraries.
255 the retrieved window is always created as a top-level window (or pad),
258 the window's character cells contain the color pair \fIvalue\fP,
312 SVr4 curses does not delay if no padding character is available.
314 NetBSD curses uses \fBnapms\fP when no padding character is available,
315 but does not take timing into account when using the padding character.
319 The \fBkeyname\fP function may return the names of user-defined
320 string capabilities which are defined in the terminfo entry via the \fB\-x\fP
322 This implementation automatically assigns at run-time keycodes to
323 user-defined strings which begin with \*(``k\*(''.
325 the same value for different runs because user-defined codes are
335 .SS "putwin/getwin file-format"
340 use an implementation-specific format.
358 The implementations which use binary dumps use block-I/O
360 Those that use textual dumps use buffered-I/O.
363 Doing that can run into problems mixing block- and buffered-I/O.
372 the parameter is a 7-bit US\-ASCII code.
375 the parameter is in the range 128\-159, i.e., a C1 control code.
377 \fBunctrl\fP returns the parameter, i.e., a one-character string with
378 the parameter as the first character.
392 showing C1 controls from the upper-128 codes
397 Or they may ignore C1 controls and treat all of the upper-128 codes as
406 it determines whether to use the \*(``M\-\*('' prefix
407 for \*(``meta\*('' keys (codes in the range 128 to 255).
410 X/Open Curses does not document the treatment of codes 128 to 159.
413 this implementation returns strings \*(``M\-^@\*('', \*(``M\-^A\*('', etc.
421 If \fI\%ncurses\fP is configured to provide the sp-functions extension,