Lines Matching full:strong
93 Non-<strong>use</strong> Capabilities</a></li>
112 <strong>ncurses</strong> library and utilities. It discusses
121 <p>The objective of the <strong>ncurses</strong> package is to
163 be easy to condition source code using <strong>ncurses</strong>
170 requires the <strong>ncurses</strong> extension.</p>
174 define, but which is defined in the <strong>ncurses</strong>
181 <p>Code written for <strong>ncurses</strong> may assume an
199 incompatibilities in the <strong>ncurses</strong> API between
226 <li><strong>Maintain package-internal files in plain
227 text.</strong> The expected viewer for them is <em>more(1)</em> or
230 <li><strong>Mark up manual pages in the man macros.</strong>
234 <li><strong>Write everything else in HTML.</strong>
474 these files. If there is a real bug in <strong>ncurses</strong>
480 <strong>ncurses</strong> library is to support fallback to
528 <strong>kmous</strong> capability as a prefix. This is kind of
535 <p>This kluge only works because <strong>kmous</strong> is not
555 <code>lib_getch.c</code> detects the <strong>kmous</strong>
645 <p>The <strong>ncurses</strong> implementation of
646 <strong>tic</strong> is rather complex internally; it has to do a
661 Non-<strong>use</strong> Capabilities</a></h3>
663 <p>Translation of most things besides <strong>use</strong>
687 <p>The background problem that makes <strong>tic</strong> tricky
689 <strong>use</strong> capabilities. Older versions would not
690 handle forward <strong>use</strong> references for this reason
696 <p>This will not do for <strong>ncurses</strong>. The problem is
698 the <strong>ncurses</strong> library so that it can be called by
704 <p>So our <strong>tic</strong> is designed to parse an entire
706 structures in-core, and then do <strong>use</strong> resolution
713 stand-alone user-accessible version of <strong>tic</strong>
715 keeping in core) any entry with no <strong>use</strong>
721 been reports of this process taking <strong>three hours</strong>,
725 <p>So. The executable <strong>tic</strong> passes the
735 an entry that postdates the time of <strong>tic</strong>'s first
737 overwriting entries newly made during the <strong>tic</strong>
743 <p>Another use of <strong>tic</strong> is to do source
746 know about are described in the <strong>captoinfo(1)</strong>
751 <strong>infocmp(1)</strong> utility. It takes the same internal
766 where the AIX <strong>box1</strong> capability get translated to
767 an <strong>acsc</strong> string.</p>
771 <p>The <strong>infocmp</strong> utility is just a wrapper around
772 the same entry-dumping code used by <strong>tic</strong> for
779 <p>The <strong>tput</strong> and <strong>clear</strong> utilities