X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=man%2Fcurs_util.3x;h=cd071b962abf947c8f0ae629d63ed26014a3282f;hp=77807d9e75bf79af79f415e391c0cfd10c772494;hb=97cb42f22c43eb31a4bf11475bd73ab0e0b10923;hpb=a8e3f06ac309504143cd56ac9ec55889bfdf4914;ds=sidebyside diff --git a/man/curs_util.3x b/man/curs_util.3x index 77807d9e..cd071b96 100644 --- a/man/curs_util.3x +++ b/man/curs_util.3x @@ -1,6 +1,6 @@ '\" t .\"*************************************************************************** -.\" Copyright (c) 1998-2015,2017 Free Software Foundation, Inc. * +.\" Copyright (c) 1998-2018,2019 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,14 +27,15 @@ .\" authorization. * .\"*************************************************************************** .\" -.\" $Id: curs_util.3x,v 1.48 2017/04/22 14:05:14 tom Exp $ +.\" $Id: curs_util.3x,v 1.55 2019/03/23 21:51:12 tom Exp $ .TH curs_util 3X "" .ie \n(.g .ds `` \(lq .el .ds `` `` .ie \n(.g .ds '' \(rq .el .ds '' '' .de bP -.IP \(bu 4 +.ie n .IP \(bu 4 +.el .IP \(bu 2 .. .na .hy 0 @@ -56,13 +57,13 @@ .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 .br -\fBchar *keyname(int c);\fR +\fBconst char *keyname(int c);\fR .br -\fBchar *key_name(wchar_t w);\fR +\fBconst char *key_name(wchar_t w);\fR .br \fBvoid filter(void);\fR .br @@ -124,10 +125,23 @@ the latter returns null where the former would display a meta character. .PP The \fBfilter\fR routine, if used, must be called before \fBinitscr\fR or \fBnewterm\fR are called. -The effect is that, during those calls, \fBLINES\fR -is set to 1; the capabilities \fBclear\fR, \fBcup\fR, \fBcud\fR, \fBcud1\fR, -\fBcuu1\fR, \fBcuu\fR, \fBvpa\fR are disabled; and the \fBhome\fR string is -set to the value of \fBcr\fR. +Calling \fBfilter\fP causes these changes in initialization: +.bP +\fBLINES\fR is set to 1; +.bP +the capabilities +\fBclear\fR, +\fBcud1\fR, +\fBcud\fR, +\fBcup\fR, +\fBcuu1\fR, +\fBcuu\fR, +\fBvpa\fR +are disabled; +.bP +the capability \fBed\fP is disabled if \fBbce\fP is set; +.bP +and the \fBhome\fR string is set to the value of \fBcr\fR. .PP The \fBnofilter\fP routine cancels the effect of a preceding \fBfilter\fP call. @@ -148,7 +162,7 @@ Normally \fBncurses\fP looks first at the terminal database for the screen size. .IP If \fBuse_env\fP was called with \fBFALSE\fP for parameter, it stops here unless -If \fBuse_tioctl\fP was also called with \fBTRUE\fP for parameter. +\fBuse_tioctl\fP was also called with \fBTRUE\fP for parameter. .bP Then it asks for the screen size via operating system calls. If successful, @@ -159,7 +173,7 @@ Finally (unless \fBuse_env\fP was called with \fBFALSE\fP parameter), using a value in those to override the results from the operating system or terminal database. .IP -\fBNcurses\fP also updates the screen size in response to SIGWINCH, +\fBNcurses\fP also updates the screen size in response to \fBSIGWINCH\fP, unless overridden by the \fBLINES\fR or \fBCOLUMNS\fR environment variables, .SS use_tioctl .PP @@ -167,7 +181,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. @@ -196,7 +211,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. @@ -219,8 +235,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), @@ -302,8 +318,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 @@ -341,7 +359,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. @@ -362,6 +381,12 @@ 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,