📄 untitl~1.searchresults
字号:
---- initscr Matches (81 in 52 files) ----
Announce.html (doc\html):184
<code>initscr()</code>.
<li>fix form_driver() cases for REQ_CLR_EOF, REQ_CLR_EOL, REQ_DEL_CHAR,
Background.c (test):12
initscr();
cbreak();
noecho();
Blue.c (test):379
initscr();
/*
Bs.c (test):205
(void) initscr();
keypad(stdscr, TRUE);
(void) def_prog_mode();
Cardfile.c (test):511
initscr();
cbreak();
noecho();
Color_set.c (test):15
initscr();
cbreak();
noecho();
Cursslk.h (c++):124
// ::initscr() is called).
Soft_Label_Key_Set(Label_Layout fmt);
Curs_color.3x.html (doc\html\man):73
called, usually right after <STRONG>initscr</STRONG>. Colors are always
used in pairs (referred to as color-pairs). A color-pair
consists of a foreground color (for characters) and a
Curs_color.3x.html (doc\html\man):97
good practice to call this routine right after <STRONG>initscr</STRONG>.
<STRONG>start_color</STRONG> initializes eight basic colors (black, red,
green, yellow, blue, magenta, cyan, and white), and two
Curs_initscr.3x.html (doc\html\man):50
<STRONG>initscr</STRONG>, <STRONG>newterm</STRONG>, <STRONG>endwin</STRONG>, <STRONG>isendwin</STRONG>, <STRONG>set_term</STRONG>, <STRONG>delscreen</STRONG> -
<STRONG>curses</STRONG> screen initialization and manipulation routines
Curs_initscr.3x.html (doc\html\man):58
<STRONG>WINDOW</STRONG> <STRONG>*initscr(void);</STRONG>
<STRONG>int</STRONG> <STRONG>endwin(void);</STRONG>
<STRONG>bool</STRONG> <STRONG>isendwin(void);</STRONG>
Curs_initscr.3x.html (doc\html\man):68
<STRONG>initscr</STRONG> is normally the first <STRONG>curses</STRONG> routine to call when
initializing a program. A few special routines sometimes
need to be called before it; these are <STRONG>slk_init</STRONG>, <STRONG>filter</STRONG>,
Curs_initscr.3x.html (doc\html\man):72
<STRONG>newterm</STRONG> may be called before <STRONG>initscr</STRONG>.
The initscr code determines the terminal type and initial-
izes all <STRONG>curses</STRONG> data structures. <STRONG>initscr</STRONG> also causes the
first call to <STRONG>refresh</STRONG> to clear the screen. If errors
occur, <STRONG>initscr</STRONG> writes an appropriate error message to
standard error and exits; otherwise, a pointer is returned
to <STRONG>stdscr</STRONG>.
Curs_initscr.3x.html (doc\html\man):83
<STRONG>initscr</STRONG>. A program that needs to inspect capabilities, so
it can continue to run in a line-oriented mode if the ter-
minal cannot support a screen-oriented program, would also
Curs_initscr.3x.html (doc\html\man):133
Note that <STRONG>initscr</STRONG> and <STRONG>newterm</STRONG> may be macros.
Curs_initscr.3x.html (doc\html\man):140
call <STRONG>initscr</STRONG> more than once.
Old versions of curses, e.g., BSD 4.4, may have returned a
null pointer from <STRONG>initscr</STRONG> when an error is detected,
rather than exiting. It is safe but redundant to check
the return value of <STRONG>initscr</STRONG> in XSI Curses.
Curs_inopts.3x.html (doc\html\man):194
to <STRONG>newterm</STRONG>, or <STRONG>stdin</STRONG> in the case that <STRONG>initscr</STRONG> was used,
will be used to do this typeahead checking. The <STRONG>typeahead</STRONG>
routine specifies that the file descriptor <EM>fd</EM> is to be
Curs_kernel.3x.html (doc\html\man):82
done automatically by <STRONG>initscr</STRONG>. There is one such save
area for each screen context allocated by <STRONG>newterm()</STRONG>.
Curs_kernel.3x.html (doc\html\man):116
<STRONG>initscr</STRONG> or <STRONG>newterm</STRONG> is called. If <EM>line</EM> is positive, a line
is removed from the top of <STRONG>stdscr</STRONG>; if <EM>line</EM> is negative, a
line is removed from the bottom. When this is done inside
<STRONG>initscr</STRONG>, the routine <STRONG>init</STRONG> (supplied by the user) is called
with two arguments: a window pointer to the one-line win-
dow that has been allocated and an integer with the number
Curs_kernel.3x.html (doc\html\man):129
<STRONG>initscr</STRONG> or <STRONG>newterm</STRONG>.
The <STRONG>curs_set</STRONG> routine sets the cursor state is set to
Curs_scr_dump.3x.html (doc\html\man):80
is used after <STRONG>initscr</STRONG> or a <STRONG>system</STRONG> call to share the screen
with another process which has done a <STRONG>scr_dump</STRONG> after its
<STRONG>endwin</STRONG> call. The data is declared invalid if the terminfo
Curs_slk.3x.html (doc\html\man):95
The <STRONG>slk_init</STRONG> routine must be called before <STRONG>initscr</STRONG> or
<STRONG>newterm</STRONG> is called. If <STRONG>initscr</STRONG> eventually uses a line from
<STRONG>stdscr</STRONG> to emulate the soft labels, then <EM>fmt</EM> determines how
the labels are arranged on the screen. Setting <EM>fmt</EM> to <STRONG>0</STRONG>
Curs_termattrs.3x.html (doc\html\man):106
ters. It is defined only after the call to <STRONG>initscr</STRONG> or
<STRONG>newterm</STRONG>. The area is overwritten by each call to <STRONG>newterm</STRONG>
and is not restored by <STRONG>set_term</STRONG>, so the value should be
Curs_terminfo.3x.html (doc\html\man):88
<STRONG>setupterm</STRONG> is automatically called by <STRONG>initscr</STRONG> and <STRONG>newterm</STRONG>.
This defines the set of terminal-dependent variables
[listed in <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>]. The <STRONG>terminfo</STRONG> variables <STRONG>lines</STRONG> and
Curs_terminfo.3x.html (doc\html\man):168
<STRONG>initscr</STRONG>, except that it is called after restoring memory
to a previous state (for example, when reloading a game
saved as a core image dump). It assumes that the windows
Curs_terminfo.3x.html (doc\html\man):259
involved in <STRONG>initscr</STRONG>.
Note that <STRONG>vidattr</STRONG> and <STRONG>vidputs</STRONG> may be macros.
Curs_terminfo.3x.html (doc\html\man):288
either <STRONG>initscr</STRONG> or <STRONG>newterm</STRONG>. So though it is documented as
a terminfo function, <STRONG>mvcur</STRONG> is really a curses function
which is not well specified.
Curs_util.3x.html (doc\html\man):90
The <STRONG>filter</STRONG> routine, if used, must be called before <STRONG>initscr</STRONG>
or <STRONG>newterm</STRONG> are called. The effect is that, during those
calls, <STRONG>LINES</STRONG> is set to 1; the capabilities <STRONG>clear</STRONG>, <STRONG>cup</STRONG>,
Curs_util.3x.html (doc\html\man):96
The <STRONG>use_env</STRONG> routine, if used, is called before <STRONG>initscr</STRONG> or
<STRONG>newterm</STRONG> are called. When called with <STRONG>FALSE</STRONG> as an argu-
ment, the values of <STRONG>lines</STRONG> and <STRONG>columns</STRONG> specified in the
Demo_defkey.c (test):193
initscr();
(void) cbreak(); /* take input chars one at a time, no wait for \n */
(void) noecho(); /* don't echo input */
Demo_forms.c (test):268
initscr();
cbreak();
noecho();
Demo_keyok.c (test):18
initscr();
(void) cbreak(); /* take input chars one at a time, no wait for \n */
(void) noecho(); /* don't echo input */
Firework.c (test):127
initscr();
noecho();
cbreak();
Firstlast.c (test):30
initscr();
noecho();
Form.3x.html (doc\html\man):69
initialization routine such as <STRONG>initscr</STRONG> must be called
before using any of these functions. To use the <STRONG>form</STRONG>
library, link with the options <STRONG>-lform</STRONG> <STRONG>-lcurses</STRONG>.
Gdc.c (test):169
initscr();
}
cbreak();
Hanoi.c (test):105
initscr();
if (has_colors()) {
int i;
Hashtest.c (test):209
(void) initscr(); /* initialize the curses library */
keypad(stdscr, TRUE); /* enable keyboard mapping */
(void) nonl(); /* tell curses not to do NL->CR/NL on output */
Inserts.c (test):76
initscr();
(void) cbreak(); /* take input chars one at a time, no wait for \n */
(void) noecho(); /* don't echo input */
Ins_wide.c (test):91
initscr();
(void) cbreak(); /* take input chars one at a time, no wait for \n */
(void) noecho(); /* don't echo input */
Knight.c (test):77
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -