X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=man%2Fcurs_util.3x;h=a71015b3ef45ec5d2fc6efccd68ab4bedcb049c5;hp=1f22dff100c5b4b33c12b2693eca7f34bc3c9ff7;hb=e5d1530ca229aef94a3c84ad33f8ae89f35c4045;hpb=06078d3fa68db669ed37178c01873546b4b28745 diff --git a/man/curs_util.3x b/man/curs_util.3x index 1f22dff1..a71015b3 100644 --- a/man/curs_util.3x +++ b/man/curs_util.3x @@ -1,6 +1,7 @@ '\" t .\"*************************************************************************** -.\" Copyright (c) 1998-2015,2017 Free Software Foundation, Inc. * +.\" Copyright 2018-2019,2020 Thomas E. Dickey * +.\" Copyright 1998-2015,2017 Free Software Foundation, Inc. * .\" * .\" Permission is hereby granted, free of charge, to any person obtaining a * .\" copy of this software and associated documentation files (the * @@ -27,7 +28,7 @@ .\" authorization. * .\"*************************************************************************** .\" -.\" $Id: curs_util.3x,v 1.52 2017/11/18 23:47:37 tom Exp $ +.\" $Id: curs_util.3x,v 1.58 2020/10/17 22:54:59 tom Exp $ .TH curs_util 3X "" .ie \n(.g .ds `` \(lq .el .ds `` `` @@ -57,26 +58,26 @@ .SH SYNOPSIS \fB#include \fR .sp -\fBchar *unctrl(chtype c);\fR +\fBconst char *unctrl(chtype c);\fR .br \fBwchar_t *wunctrl(cchar_t *c);\fR +.sp +\fBconst char *keyname(int c);\fR .br -\fBchar *keyname(int c);\fR -.br -\fBchar *key_name(wchar_t w);\fR -.br +\fBconst char *key_name(wchar_t w);\fR +.sp \fBvoid filter(void);\fR .br \fBvoid nofilter(void);\fR -.br +.sp \fBvoid use_env(bool f);\fR .br \fBvoid use_tioctl(bool f);\fR -.br +.sp \fBint putwin(WINDOW *win, FILE *filep);\fR .br \fBWINDOW *getwin(FILE *filep);\fR -.br +.sp \fBint delay_output(int ms);\fR .br \fBint flushinp(void);\fR @@ -114,8 +115,8 @@ Values above 256 may be the names of the names of function keys. .bP Otherwise (if there is no corresponding name) the function returns null, to denote an error. -X/Open also lists an "UNKNOWN KEY" return value, which some implementations -return rather than null. +X/Open also lists an \*(``UNKNOWN KEY\*('' return value, +which some implementations return rather than null. .LP The corresponding \fBkey_name\fR returns a character string corresponding to the wide-character value \fIw\fR. @@ -181,7 +182,8 @@ The \fBuse_tioctl\fR routine, if used, should be called before \fBinitscr\fR or \fBnewterm\fR are called (because those compute the screen size). After \fBuse_tioctl\fR is called with \fBTRUE\fR as an argument, -\fBncurses\fP modifies the last step in its computation of screen size as follows: +\fBncurses\fP modifies the last step in its computation +of screen size as follows: .bP checks if the \fBLINES\fR and \fBCOLUMNS\fR environment variables are set to a number greater than zero. @@ -210,7 +212,8 @@ TRUE/TRUE/T{ \fBncurses\fP updates $LINES and $COLUMNS based on operating system calls. T} FALSE/TRUE/T{ -\fBncurses\fP ignores $LINES and $COLUMNS, uses operating system calls to obtain size. +\fBncurses\fP ignores $LINES and $COLUMNS, +uses operating system calls to obtain size. T} FALSE/FALSE/T{ \fBncurses\fP relies on the terminal database to determine size. @@ -233,8 +236,8 @@ There are a few caveats: .bP the data written is a copy of the \fBWINDOW\fP structure, and its associated character cells. -The format differs between the wide-character (ncursesw) and -non-wide (ncurses) libraries. +The format differs between the wide-character (\fBncursesw\fP) and +non-wide (\fBncurses\fP) libraries. You can transfer data between the two, however. .bP the retrieved window is always created as a top-level window (or pad), @@ -287,7 +290,7 @@ The \fBkeyname\fP function may return the names of user-defined string capabilities which are defined in the terminfo entry via the \fB\-x\fP option of \fB@TIC@\fP. This implementation automatically assigns at run-time keycodes to -user-defined strings which begin with "k". +user-defined strings which begin with \*(``k\*(''. The keycodes start at KEY_MAX, but are not guaranteed to be the same value for different runs because user-defined codes are merged from all terminal descriptions which have been loaded. @@ -316,8 +319,10 @@ and were later (in 1988) incorporated into SVr4. Oddly, there are no such functions in the 4.3BSD curses sources. .bP Most implementations simply dump the binary \fBWINDOW\fP structure to the file. -These include SVr4 curses, NetBSD and PDCurses, as well as older \fBncurses\fP versions. -This implementation (as well as the X/Open variant of Solaris curses, dated 1995) +These include SVr4 curses, NetBSD and PDCurses, +as well as older \fBncurses\fP versions. +This implementation +(as well as the X/Open variant of Solaris curses, dated 1995) uses textual dumps. .IP The implementations which use binary dumps use block-I/O @@ -339,7 +344,7 @@ the parameter is a 7-bit US\-ASCII code. This is the case that X/Open Curses documented. .bP the parameter is in the range 128\-159, i.e., a C1 control code. -If \fBuse_legacy_coding\fP has been called with a \fB2\fP parameter, +If \fBuse_legacy_coding\fP(3X) has been called with a \fB2\fP parameter, \fBunctrl\fP returns the parameter, i.e., a one-character string with the parameter as the first character. Otherwise, it returns \*(``~@\*('', \*(``~A\*('', etc., @@ -355,7 +360,8 @@ parameter values outside the 0 to 255 range. .PP The strings returned by \fBunctrl\fR in this implementation are determined at compile time, -showing C1 controls from the upper-128 codes with a \*(``~\*('' prefix rather than \*(``^\*(''. +showing C1 controls from the upper-128 codes +with a \*(``~\*('' prefix rather than \*(``^\*(''. Other implementations have different conventions. For example, they may show both sets of control characters with \*(``^\*('', and strip the parameter to 7 bits. @@ -363,19 +369,25 @@ Or they may ignore C1 controls and treat all of the upper-128 codes as printable. This implementation uses 8 bits but does not modify the string to reflect locale. -The \fBuse_legacy_coding\fP function allows the caller to +The \fBuse_legacy_coding\fP(3X) function allows the caller to change the output of \fBunctrl\fP. .PP Likewise, the \fBmeta\fP(3X) function allows the caller to change the output of \fBkeyname\fP, i.e., it determines whether to use the \*(``M\-\*('' prefix for \*(``meta\*('' keys (codes in the range 128 to 255). -Both \fBuse_legacy_coding\fP and \fBmeta\fP succeed only after +Both \fBuse_legacy_coding\fP(3X) and \fBmeta\fP(3X) succeed only after curses is initialized. X/Open Curses does not document the treatment of codes 128 to 159. When treating them as \*(``meta\*('' keys (or if \fBkeyname\fP is called before initializing curses), this implementation returns strings \*(``M\-^@\*('', \*(``M\-^A\*('', etc. +.PP +X/Open Curses documents \fBunctrl\fP as declared in \fB\fP, +which \fBncurses\fP does. +However, \fBncurses\fP' \fB\fP includes \fB\fP, +matching the behavior of SVr4 curses. +Other implementations may not do that. .SS use_env/use_tioctl .PP If \fBncurses\fP is configured to provide the sp-functions extension,