5095 lines
274 KiB
Diff
5095 lines
274 KiB
Diff
# ncurses 6.0 - patch 20161015 - Thomas E. Dickey
|
|
#
|
|
# ------------------------------------------------------------------------------
|
|
#
|
|
# Ncurses 6.0 is at
|
|
# ftp.gnu.org:/pub/gnu
|
|
#
|
|
# Patches for ncurses 6.0 can be found at
|
|
# ftp://invisible-island.net/ncurses/6.0
|
|
# http://invisible-mirror.net/archives/ncurses/6.0
|
|
#
|
|
# ------------------------------------------------------------------------------
|
|
# ftp://invisible-island.net/ncurses/6.0/ncurses-6.0-20161015.patch.gz
|
|
# patch by Thomas E. Dickey <dickey@invisible-island.net>
|
|
# created Sun Oct 16 00:57:24 UTC 2016
|
|
# ------------------------------------------------------------------------------
|
|
# NEWS | 14
|
|
# VERSION | 2
|
|
# dist.mk | 4
|
|
# doc/html/man/captoinfo.1m.html | 12
|
|
# doc/html/man/clear.1.html | 2
|
|
# doc/html/man/curs_attr.3x.html | 10
|
|
# doc/html/man/curs_clear.3x.html | 10
|
|
# doc/html/man/curs_color.3x.html | 8
|
|
# doc/html/man/curs_extend.3x.html | 22
|
|
# doc/html/man/curs_getch.3x.html | 4
|
|
# doc/html/man/curs_initscr.3x.html | 6
|
|
# doc/html/man/curs_inopts.3x.html | 10
|
|
# doc/html/man/curs_kernel.3x.html | 6
|
|
# doc/html/man/curs_outopts.3x.html | 8
|
|
# doc/html/man/curs_refresh.3x.html | 14
|
|
# doc/html/man/curs_slk.3x.html | 8
|
|
# doc/html/man/curs_terminfo.3x.html | 149 ++--
|
|
# doc/html/man/curs_trace.3x.html | 6
|
|
# doc/html/man/curs_window.3x.html | 6
|
|
# doc/html/man/default_colors.3x.html | 62 -
|
|
# doc/html/man/form.3x.html | 2
|
|
# doc/html/man/infocmp.1m.html | 23
|
|
# doc/html/man/infotocap.1m.html | 10
|
|
# doc/html/man/legacy_coding.3x.html | 6
|
|
# doc/html/man/menu.3x.html | 2
|
|
# doc/html/man/menu_format.3x.html | 6
|
|
# doc/html/man/menu_post.3x.html | 8
|
|
# doc/html/man/ncurses.3x.html | 2
|
|
# doc/html/man/panel.3x.html | 45 -
|
|
# doc/html/man/tabs.1.html | 6
|
|
# doc/html/man/term.5.html | 12
|
|
# doc/html/man/terminfo.5.html | 1239 +++++++++++++++++-----------------
|
|
# doc/html/man/tic.1m.html | 81 +-
|
|
# doc/html/man/toe.1m.html | 2
|
|
# doc/html/man/tput.1.html | 2
|
|
# doc/html/man/tset.1.html | 2
|
|
# man/captoinfo.1m | 10
|
|
# man/curs_attr.3x | 11
|
|
# man/curs_clear.3x | 6
|
|
# man/curs_color.3x | 6
|
|
# man/curs_extend.3x | 8
|
|
# man/curs_getch.3x | 4
|
|
# man/curs_initscr.3x | 6
|
|
# man/curs_inopts.3x | 8
|
|
# man/curs_kernel.3x | 6
|
|
# man/curs_outopts.3x | 8
|
|
# man/curs_refresh.3x | 10
|
|
# man/curs_slk.3x | 6
|
|
# man/curs_terminfo.3x | 18
|
|
# man/curs_trace.3x | 6
|
|
# man/curs_window.3x | 6
|
|
# man/default_colors.3x | 33
|
|
# man/infotocap.1m | 8
|
|
# man/legacy_coding.3x | 8
|
|
# man/menu_format.3x | 6
|
|
# man/menu_post.3x | 8
|
|
# man/panel.3x | 18
|
|
# man/tabs.1 | 4
|
|
# man/term.5 | 12
|
|
# man/terminfo.head | 4
|
|
# man/terminfo.tail | 54 -
|
|
# ncurses/llib-lncurses | 14
|
|
# ncurses/llib-lncursest | 14
|
|
# ncurses/llib-lncursestw | 14
|
|
# ncurses/llib-lncursesw | 14
|
|
# ncurses/llib-ltic | 11
|
|
# ncurses/llib-ltict | 11
|
|
# ncurses/llib-ltictw | 11
|
|
# ncurses/llib-lticw | 11
|
|
# ncurses/llib-ltinfo | 7
|
|
# ncurses/llib-ltinfot | 7
|
|
# ncurses/llib-ltinfotw | 7
|
|
# ncurses/llib-ltinfow | 7
|
|
# ncurses/tty/tty_update.c | 8
|
|
# package/debian-mingw/changelog | 4
|
|
# package/debian-mingw64/changelog | 4
|
|
# package/debian/changelog | 4
|
|
# package/mingw-ncurses.nsi | 4
|
|
# package/mingw-ncurses.spec | 2
|
|
# package/ncurses.spec | 2
|
|
# 80 files changed, 1168 insertions(+), 1073 deletions(-)
|
|
# ------------------------------------------------------------------------------
|
|
Index: NEWS
|
|
Prereq: 1.2677
|
|
--- ncurses-6.0-20161008+/NEWS 2016-10-09 01:52:39.000000000 +0000
|
|
+++ ncurses-6.0-20161015/NEWS 2016-10-15 23:26:53.000000000 +0000
|
|
@@ -25,7 +25,7 @@
|
|
-- sale, use or other dealings in this Software without prior written --
|
|
-- authorization. --
|
|
-------------------------------------------------------------------------------
|
|
--- $Id: NEWS,v 1.2677 2016/10/09 01:52:39 tom Exp $
|
|
+-- $Id: NEWS,v 1.2682 2016/10/15 23:26:53 tom Exp $
|
|
-------------------------------------------------------------------------------
|
|
|
|
This is a log of changes that ncurses has gone through since Zeyd started
|
|
@@ -45,6 +45,16 @@
|
|
Changes through 1.9.9e did not credit all contributions;
|
|
it is not possible to add this information.
|
|
|
|
+20161015
|
|
+ + amend internal use of tputs to consistently use the number of lines
|
|
+ affected, e.g., for insert/delete character operations. While
|
|
+ merging terminfo source early in 1995, several descriptions used the
|
|
+ "*" proportional delay for these operations, prompting a change in
|
|
+ doupdate.
|
|
+ + regenerate llib-* files.
|
|
+ + regenerate HTML manpages.
|
|
+ + fix several formatting issues with manual pages.
|
|
+
|
|
20161008
|
|
+ adjust size in infocmp/tic to work with strlcpy.
|
|
+ fix configure script to record when strlcat is found on OpenBSD.
|
|
@@ -11094,7 +11104,7 @@
|
|
(SVr4) curses, which doesn't use 'const' in its prototypes.
|
|
+ modify ifdef's in test/hashtest.c and test/view.c to compile with
|
|
Solaris curses.
|
|
- + modify _tracedump() to pad pad colors & attrs lines to match change
|
|
+ + modify _tracedump() to pad colors & attrs lines to match change
|
|
in 970101 showing first/last changes.
|
|
+ corrected location of terminating null on dynamically allocated forms
|
|
fields (patch by Per Foreby).
|
|
Index: VERSION
|
|
--- ncurses-6.0-20161008+/VERSION 2016-10-03 00:57:15.000000000 +0000
|
|
+++ ncurses-6.0-20161015/VERSION 2016-10-15 15:43:49.000000000 +0000
|
|
@@ -1 +1 @@
|
|
-5:0:9 6.0 20161008
|
|
+5:0:9 6.0 20161015
|
|
Index: dist.mk
|
|
Prereq: 1.1127
|
|
--- ncurses-6.0-20161008+/dist.mk 2016-10-03 00:57:15.000000000 +0000
|
|
+++ ncurses-6.0-20161015/dist.mk 2016-10-15 15:43:49.000000000 +0000
|
|
@@ -25,7 +25,7 @@
|
|
# use or other dealings in this Software without prior written #
|
|
# authorization. #
|
|
##############################################################################
|
|
-# $Id: dist.mk,v 1.1127 2016/10/03 00:57:15 tom Exp $
|
|
+# $Id: dist.mk,v 1.1128 2016/10/15 15:43:49 tom Exp $
|
|
# Makefile for creating ncurses distributions.
|
|
#
|
|
# This only needs to be used directly as a makefile by developers, but
|
|
@@ -37,7 +37,7 @@
|
|
# These define the major/minor/patch versions of ncurses.
|
|
NCURSES_MAJOR = 6
|
|
NCURSES_MINOR = 0
|
|
-NCURSES_PATCH = 20161008
|
|
+NCURSES_PATCH = 20161015
|
|
|
|
# We don't append the patch to the version, since this only applies to releases
|
|
VERSION = $(NCURSES_MAJOR).$(NCURSES_MINOR)
|
|
Index: doc/html/man/captoinfo.1m.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/captoinfo.1m.html 2016-09-10 22:14:37.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/captoinfo.1m.html 2016-10-15 23:12:19.000000000 +0000
|
|
@@ -1,7 +1,7 @@
|
|
<!--
|
|
* t
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2007,2010 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2010,2016 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 +27,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: captoinfo.1m,v 1.25 2010/12/04 18:36:44 tom Exp @
|
|
+ * @Id: captoinfo.1m,v 1.26 2016/10/15 17:26:09 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -160,7 +160,7 @@
|
|
GG acs magic cookie count
|
|
|
|
If the single-line capabilities occur in an entry, they
|
|
- will automatically be composed into an <EM>acsc</EM> string. The
|
|
+ will automatically be composed into an <STRONG>acsc</STRONG> string. The
|
|
double-line capabilities and <STRONG>GG</STRONG> are discarded with a warn-
|
|
ing message.
|
|
|
|
@@ -178,10 +178,10 @@
|
|
font3 s3ds
|
|
|
|
Additionally, the AIX <EM>box1</EM> capability will be automati-
|
|
- cally translated to an <EM>acsc</EM> string.
|
|
+ cally translated to an <STRONG>acsc</STRONG> string.
|
|
|
|
Hewlett-Packard's terminfo library supports two nonstan-
|
|
- dard terminfo capabilities <EM>meml</EM> (memory lock) and <EM>memu</EM>
|
|
+ dard terminfo capabilities <STRONG>meml</STRONG> (memory lock) and <STRONG>memu</STRONG>
|
|
(memory unlock). These will be discarded with a warning
|
|
message.
|
|
|
|
@@ -198,7 +198,7 @@
|
|
</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
|
|
<STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>, <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
</PRE><H2><a name="h2-AUTHOR">AUTHOR</a></H2><PRE>
|
|
Index: doc/html/man/clear.1.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/clear.1.html 2016-09-10 22:14:37.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/clear.1.html 2016-10-15 23:12:19.000000000 +0000
|
|
@@ -67,7 +67,7 @@
|
|
</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
|
|
<STRONG><A HREF="tput.1.html">tput(1)</A></STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
|
|
Index: doc/html/man/curs_attr.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_attr.3x.html 2016-07-24 00:13:41.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_attr.3x.html 2016-10-15 23:12:20.000000000 +0000
|
|
@@ -27,7 +27,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_attr.3x,v 1.47 2016/07/23 23:48:49 tom Exp @
|
|
+ * @Id: curs_attr.3x,v 1.48 2016/10/15 17:09:05 tom Exp @
|
|
* attr_get
|
|
* .br
|
|
* .br
|
|
@@ -266,12 +266,12 @@
|
|
<STRONG>A_ALTCHARSET</STRONG>, <STRONG>A_PROTECT</STRONG>, and <STRONG>A_INVIS</STRONG>).
|
|
|
|
This implementation provides the <STRONG>A_ITALIC</STRONG> attribute for
|
|
- terminals which have the <EM>enter</EM><STRONG>_</STRONG><EM>italics</EM><STRONG>_</STRONG><EM>mode</EM> (sitm) and <EM>ex-</EM>
|
|
- <EM>it</EM><STRONG>_</STRONG><EM>italics</EM><STRONG>_</STRONG><EM>mode</EM> (ritm) capabilities. Italics are not men-
|
|
+ terminals which have the <STRONG>enter_italics_mode</STRONG> (<STRONG>sitm</STRONG>) and <STRONG>ex-</STRONG>
|
|
+ <STRONG>it_italics_mode</STRONG> (<STRONG>ritm</STRONG>) capabilities. Italics are not men-
|
|
tioned in X/Open Curses. Unlike the other video at-
|
|
- tributes, <STRONG>I_ITALIC</STRONG> is unrelated to the <EM>set</EM><STRONG>_</STRONG><EM>attributes</EM> ca-
|
|
+ tributes, <STRONG>A_ITALIC</STRONG> is unrelated to the <STRONG>set_attributes</STRONG> ca-
|
|
pabilities. This implementation makes the assumption that
|
|
- <EM>exit</EM><STRONG>_</STRONG><EM>attribute</EM><STRONG>_</STRONG><EM>mode</EM> may also reset italics.
|
|
+ <STRONG>exit_attribute_mode</STRONG> may also reset italics.
|
|
|
|
XSI Curses added the new entry points, <STRONG>attr_get</STRONG>, <STRONG>attr_on</STRONG>,
|
|
<STRONG>attr_off</STRONG>, <STRONG>attr_set</STRONG>, <STRONG>wattr_on</STRONG>, <STRONG>wattr_off</STRONG>, <STRONG>wattr_get</STRONG>, <STRONG>wat-</STRONG>
|
|
Index: doc/html/man/curs_clear.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_clear.3x.html 2016-01-30 19:24:51.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_clear.3x.html 2016-10-15 23:12:20.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2007,2010 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2010,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_clear.3x,v 1.14 2010/12/04 18:36:44 tom Exp @
|
|
+ * @Id: curs_clear.3x,v 1.15 2016/10/15 17:02:31 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -111,9 +111,9 @@
|
|
<STRONG>scr)</STRONG>. This will not work under ncurses.
|
|
|
|
This implementation, and others such as Solaris, sets the
|
|
- current position to 0,0 after erasing via <STRONG>werase()</STRONG> and
|
|
- <STRONG>wclear()</STRONG>. That fact is not documented in other implemen-
|
|
- tations, and may not be true of implementations which were
|
|
+ current position to 0,0 after erasing via <STRONG>werase</STRONG> and
|
|
+ <STRONG>wclear</STRONG>. That fact is not documented in other implementa-
|
|
+ tions, and may not be true of implementations which were
|
|
not derived from SVr4 source.
|
|
|
|
Not obvious from the description, most implementations
|
|
Index: doc/html/man/curs_color.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_color.3x.html 2016-07-30 22:04:27.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_color.3x.html 2016-10-15 23:12:20.000000000 +0000
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_color.3x,v 1.43 2016/07/30 15:22:11 tom Exp @
|
|
+ * @Id: curs_color.3x,v 1.45 2016/10/15 17:10:19 tom Exp @
|
|
* .br
|
|
* .br
|
|
* .br
|
|
@@ -302,8 +302,8 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-RETURN-VALUE">RETURN VALUE</a></H2><PRE>
|
|
- The routines <STRONG>can_change_color()</STRONG> and <STRONG>has_colors()</STRONG> return
|
|
- <STRONG>TRUE</STRONG> or <STRONG>FALSE</STRONG>.
|
|
+ The routines <STRONG>can_change_color</STRONG> and <STRONG>has_colors</STRONG> return <STRONG>TRUE</STRONG>
|
|
+ or <STRONG>FALSE</STRONG>.
|
|
|
|
All other routines return the integer <STRONG>ERR</STRONG> upon failure and
|
|
an <STRONG>OK</STRONG> (SVr4 specifies only "an integer value other than
|
|
@@ -321,7 +321,7 @@
|
|
|
|
<STRONG>init_color</STRONG>
|
|
returns an error if the terminal does not support
|
|
- this feature, e.g., if the <EM>initialize</EM><STRONG>_</STRONG><EM>color</EM> capa-
|
|
+ this feature, e.g., if the <STRONG>initialize_color</STRONG> capa-
|
|
bility is absent from the terminal description.
|
|
|
|
<STRONG>start_color</STRONG>
|
|
Index: doc/html/man/curs_extend.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_extend.3x.html 2016-05-15 01:17:07.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_extend.3x.html 2016-10-15 23:12:20.000000000 +0000
|
|
@@ -27,7 +27,7 @@
|
|
* authorization. *
|
|
****************************************************************************
|
|
* Author: Thomas E. Dickey 1999-on
|
|
- * @Id: curs_extend.3x,v 1.20 2016/05/14 23:10:54 tom Exp @
|
|
+ * @Id: curs_extend.3x,v 1.21 2016/10/15 16:52:48 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -64,20 +64,20 @@
|
|
|
|
|
|
</PRE><H3><a name="h3-curses_version">curses_version</a></H3><PRE>
|
|
- Use <EM>curses</EM><STRONG>_</STRONG><EM>version()</EM> to get the version number, including
|
|
+ Use <STRONG>curses_version</STRONG> to get the version number, including
|
|
patch level of the library, e.g., <STRONG>5.0.19991023</STRONG>
|
|
|
|
|
|
</PRE><H3><a name="h3-use_extended_names">use_extended_names</a></H3><PRE>
|
|
- The <EM>use</EM><STRONG>_</STRONG><EM>extended</EM><STRONG>_</STRONG><EM>names()</EM> function controls whether the
|
|
- calling application is able to use user-defined or non-
|
|
- standard names which may be compiled into the terminfo
|
|
- description, i.e., via the terminfo or termcap interfaces.
|
|
- Normally these names are available for use, since the
|
|
- essential decision is made by using the <STRONG>-x</STRONG> option of <STRONG>tic</STRONG>
|
|
- to compile extended terminal definitions. However you can
|
|
- disable this feature to ensure compatibility with other
|
|
- implementations of curses.
|
|
+ The <STRONG>use_extended_names</STRONG> function controls whether the call-
|
|
+ ing application is able to use user-defined or nonstandard
|
|
+ names which may be compiled into the terminfo description,
|
|
+ i.e., via the terminfo or termcap interfaces. Normally
|
|
+ these names are available for use, since the essential
|
|
+ decision is made by using the <STRONG>-x</STRONG> option of <STRONG>tic</STRONG> to compile
|
|
+ extended terminal definitions. However you can disable
|
|
+ this feature to ensure compatibility with other implemen-
|
|
+ tations of curses.
|
|
|
|
|
|
</PRE><H2><a name="h2-RETURN-VALUE">RETURN VALUE</a></H2><PRE>
|
|
Index: doc/html/man/curs_getch.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_getch.3x.html 2016-09-10 22:14:38.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_getch.3x.html 2016-10-15 23:12:20.000000000 +0000
|
|
@@ -27,7 +27,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_getch.3x,v 1.48 2016/09/10 21:56:25 Leon.Winter Exp @
|
|
+ * @Id: curs_getch.3x,v 1.49 2016/10/15 16:44:01 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -295,7 +295,7 @@
|
|
|
|
</PRE><H2><a name="h2-RETURN-VALUE">RETURN VALUE</a></H2><PRE>
|
|
All routines return the integer <STRONG>ERR</STRONG> upon failure and an
|
|
- integer value other than <STRONG>ERR</STRONG> (<STRONG>OK</STRONG> in the case of ungetch())
|
|
+ integer value other than <STRONG>ERR</STRONG> (<STRONG>OK</STRONG> in the case of <STRONG>ungetch</STRONG>)
|
|
upon successful completion.
|
|
|
|
<STRONG>ungetch</STRONG>
|
|
Index: doc/html/man/curs_initscr.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_initscr.3x.html 2016-01-30 19:24:52.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_initscr.3x.html 2016-10-15 23:12:20.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2014,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_initscr.3x,v 1.24 2015/07/21 23:01:38 tom Exp @
|
|
+ * @Id: curs_initscr.3x,v 1.25 2016/10/15 17:02:31 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -202,7 +202,7 @@
|
|
|
|
<EM>Curses</EM> <EM>implementations</EM> <EM>may</EM> <EM>provide</EM> <EM>for</EM> <EM>special</EM> <EM>han-</EM>
|
|
<EM>dling</EM> <EM>of</EM> <EM>the</EM> <EM>SIGINT,</EM> <EM>SIGQUIT</EM> <EM>and</EM> <EM>SIGTSTP</EM> <EM>signals</EM> <EM>if</EM>
|
|
- <EM>their</EM> <EM>disposition</EM> <EM>is</EM> <EM>SIG</EM><STRONG>_</STRONG><EM>DFL</EM> <EM>at</EM> <EM>the</EM> <EM>time</EM> <STRONG>initscr()</STRONG> <EM>is</EM>
|
|
+ <EM>their</EM> <EM>disposition</EM> <EM>is</EM> <EM>SIG</EM><STRONG>_</STRONG><EM>DFL</EM> <EM>at</EM> <EM>the</EM> <EM>time</EM> <STRONG>initscr</STRONG> <EM>is</EM>
|
|
<EM>called</EM> <STRONG>...</STRONG>
|
|
|
|
<EM>Any</EM> <EM>special</EM> <EM>handling</EM> <EM>for</EM> <EM>these</EM> <EM>signals</EM> <EM>may</EM> <EM>remain</EM> <EM>in</EM>
|
|
Index: doc/html/man/curs_inopts.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_inopts.3x.html 2016-01-30 19:24:52.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_inopts.3x.html 2016-10-15 23:12:20.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2013,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_inopts.3x,v 1.20 2015/11/28 19:03:12 Benno.Schulenberg Exp @
|
|
+ * @Id: curs_inopts.3x,v 1.22 2016/10/15 17:13:45 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -193,8 +193,8 @@
|
|
and output queues associated with the <STRONG>INTR</STRONG>, <STRONG>QUIT</STRONG> and <STRONG>SUSP</STRONG>
|
|
characters will not be done [see <STRONG>termio(7)</STRONG>]. When <STRONG>qiflush</STRONG>
|
|
is called, the queues will be flushed when these control
|
|
- characters are read. You may want to call <STRONG>noqiflush()</STRONG> in
|
|
- a signal handler if you want output to continue as though
|
|
+ characters are read. You may want to call <STRONG>noqiflush</STRONG> in a
|
|
+ signal handler if you want output to continue as though
|
|
the interrupt had not occurred, after the handler exits.
|
|
|
|
|
|
@@ -268,7 +268,7 @@
|
|
curses key-names). On the other hand, an application can
|
|
use <STRONG>define_key</STRONG> to establish a specific keycode for a given
|
|
string. This makes it possible for an application to
|
|
- check for an extended capability's presence with <EM>tigetstr</EM>,
|
|
+ check for an extended capability's presence with <STRONG>tigetstr</STRONG>,
|
|
and reassign the keycode to match its own needs.
|
|
|
|
Low-level applications can use <STRONG>tigetstr</STRONG> to obtain the def-
|
|
Index: doc/html/man/curs_kernel.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_kernel.3x.html 2016-01-30 19:24:53.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_kernel.3x.html 2016-10-15 23:12:21.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_kernel.3x,v 1.20 2015/07/21 01:10:11 tom Exp @
|
|
+ * @Id: curs_kernel.3x,v 1.21 2016/10/15 16:42:55 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -79,7 +79,7 @@
|
|
"shell" (not in <STRONG>curses</STRONG>) state for use by the <STRONG>re-</STRONG>
|
|
<STRONG>set_prog_mode</STRONG> and <STRONG>reset_shell_mode</STRONG> routines. This is done
|
|
automatically by <STRONG>initscr</STRONG>. There is one such save area for
|
|
- each screen context allocated by <STRONG>newterm()</STRONG>.
|
|
+ each screen context allocated by <STRONG>newterm</STRONG>.
|
|
|
|
|
|
</PRE><H3><a name="h3-reset_prog_mode_-reset_shell_mode">reset_prog_mode, reset_shell_mode</a></H3><PRE>
|
|
Index: doc/html/man/curs_outopts.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_outopts.3x.html 2016-01-30 19:24:53.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_outopts.3x.html 2016-10-15 23:12:21.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_outopts.3x,v 1.26 2015/07/21 00:23:43 tom Exp @
|
|
+ * @Id: curs_outopts.3x,v 1.27 2016/10/15 17:02:31 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -193,8 +193,8 @@
|
|
Issue 4.
|
|
|
|
The XSI Curses standard is ambiguous on the question of
|
|
- whether <STRONG>raw</STRONG>() should disable the CRLF translations con-
|
|
- trolled by <STRONG>nl</STRONG>() and <STRONG>nonl</STRONG>(). BSD curses did turn off these
|
|
+ whether <STRONG>raw</STRONG> should disable the CRLF translations con-
|
|
+ trolled by <STRONG>nl</STRONG> and <STRONG>nonl</STRONG>. BSD curses did turn off these
|
|
translations; AT&T curses (at least as late as SVr1) did
|
|
not. We choose to do so, on the theory that a programmer
|
|
requesting raw input wants a clean (ideally 8-bit clean)
|
|
Index: doc/html/man/curs_refresh.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_refresh.3x.html 2016-01-30 19:24:53.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_refresh.3x.html 2016-10-15 23:12:21.000000000 +0000
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_refresh.3x,v 1.16 2016/01/30 15:52:36 tom Exp @
|
|
+ * @Id: curs_refresh.3x,v 1.17 2016/10/15 16:45:45 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -114,7 +114,7 @@
|
|
The <STRONG>wredrawln</STRONG> routine indicates to <STRONG>curses</STRONG> that some screen
|
|
lines are corrupted and should be thrown away before any-
|
|
thing is written over them. It touches the indicated
|
|
- lines (marking them changed). The routine <STRONG>redrawwin</STRONG>()
|
|
+ lines (marking them changed). The routine <STRONG>redrawwin</STRONG>
|
|
touches the entire window.
|
|
|
|
|
|
@@ -143,14 +143,14 @@
|
|
The XSI Curses standard, Issue 4 describes these func-
|
|
tions.
|
|
|
|
- Whether <STRONG>wnoutrefresh()</STRONG> copies to the virtual screen the
|
|
- entire contents of a window or just its changed portions
|
|
- has never been well-documented in historic curses versions
|
|
+ Whether <STRONG>wnoutrefresh</STRONG> copies to the virtual screen the en-
|
|
+ tire contents of a window or just its changed portions has
|
|
+ never been well-documented in historic curses versions
|
|
(including SVr4). It might be unwise to rely on either
|
|
behavior in programs that might have to be linked with
|
|
other curses implementations. Instead, you can do an ex-
|
|
- plicit <STRONG>touchwin()</STRONG> before the <STRONG>wnoutrefresh()</STRONG> call to guar-
|
|
- antee an entire-contents copy anywhere.
|
|
+ plicit <STRONG>touchwin</STRONG> before the <STRONG>wnoutrefresh</STRONG> call to guarantee
|
|
+ an entire-contents copy anywhere.
|
|
|
|
|
|
</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
|
|
Index: doc/html/man/curs_slk.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_slk.3x.html 2016-01-30 19:24:54.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_slk.3x.html 2016-10-15 23:12:21.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2007,2010 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2010,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_slk.3x,v 1.22 2010/12/04 18:38:55 tom Exp @
|
|
+ * @Id: curs_slk.3x,v 1.23 2016/10/15 17:02:31 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -207,8 +207,8 @@
|
|
tions. It changes the argument type of the attribute-ma-
|
|
nipulation functions <STRONG>slk_attron</STRONG>, <STRONG>slk_attroff</STRONG>, <STRONG>slk_attrset</STRONG>
|
|
to be <STRONG>attr_t</STRONG>, and adds <STRONG>const</STRONG> qualifiers. The format codes
|
|
- <STRONG>2</STRONG> and <STRONG>3</STRONG> for <STRONG>slk_init()</STRONG> and the function <STRONG>slk_attr</STRONG> are spe-
|
|
- cific to ncurses.
|
|
+ <STRONG>2</STRONG> and <STRONG>3</STRONG> for <STRONG>slk_init</STRONG> and the function <STRONG>slk_attr</STRONG> are specif-
|
|
+ ic to ncurses.
|
|
|
|
|
|
</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
|
|
Index: doc/html/man/curs_terminfo.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_terminfo.3x.html 2016-08-21 00:10:09.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_terminfo.3x.html 2016-10-15 23:12:21.000000000 +0000
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_terminfo.3x,v 1.44 2016/08/20 23:26:10 tom Exp @
|
|
+ * @Id: curs_terminfo.3x,v 1.46 2016/10/15 17:27:48 tom Exp @
|
|
* ***************************************************************************
|
|
* ***************************************************************************
|
|
* ***************************************************************************
|
|
@@ -149,14 +149,14 @@
|
|
for curses applications.
|
|
|
|
<STRONG>setupterm</STRONG> determines if the entry is a hardcopy type
|
|
- by checking the <EM>hc</EM> (<EM>hardcopy</EM>) capability.
|
|
+ by checking the <STRONG>hc</STRONG> (<STRONG>hardcopy</STRONG>) capability.
|
|
|
|
<STRONG>0</STRONG> means that the terminal could not be found, or that
|
|
it is a generic type, having too little information
|
|
for curses applications to run.
|
|
|
|
<STRONG>setupterm</STRONG> determines if the entry is a generic type
|
|
- by checking the <EM>gn</EM> (<EM>generic</EM>) capability.
|
|
+ by checking the <STRONG>gn</STRONG> (<STRONG>generic</STRONG>) capability.
|
|
|
|
<STRONG>-1</STRONG> means that the <STRONG>terminfo</STRONG> database could not be found.
|
|
|
|
@@ -226,44 +226,49 @@
|
|
|
|
</PRE><H3><a name="h3-Output-Functions">Output Functions</a></H3><PRE>
|
|
The <STRONG>tputs</STRONG> routine applies padding information to the
|
|
- string <EM>str</EM> and outputs it. The <EM>str</EM> must be a terminfo
|
|
- string variable or the return value from <STRONG>tparm</STRONG>, <STRONG>tgetstr</STRONG>,
|
|
- or <STRONG>tgoto</STRONG>. <EM>affcnt</EM> is the number of lines affected, or 1 if
|
|
- not applicable. <EM>putc</EM> is a <STRONG>putchar</STRONG>-like routine to which
|
|
- the characters are passed, one at a time.
|
|
+ string <EM>str</EM> and outputs it:
|
|
|
|
- The <STRONG>putp</STRONG> routine calls <STRONG>tputs(</STRONG><EM>str</EM><STRONG>,</STRONG> <STRONG>1,</STRONG> <STRONG>putchar)</STRONG>. Note that
|
|
- the output of <STRONG>putp</STRONG> always goes to <STRONG>stdout</STRONG>, not to the
|
|
+ <STRONG>o</STRONG> The <EM>str</EM> must be a terminfo string variable or the re-
|
|
+ turn value from <STRONG>tparm</STRONG>, <STRONG>tgetstr</STRONG>, or <STRONG>tgoto</STRONG>.
|
|
+
|
|
+ <STRONG>o</STRONG> <EM>affcnt</EM> is the number of lines affected, or 1 if not
|
|
+ applicable.
|
|
+
|
|
+ <STRONG>o</STRONG> <EM>putc</EM> is a <STRONG>putchar</STRONG>-like routine to which the characters
|
|
+ are passed, one at a time.
|
|
+
|
|
+ The <STRONG>putp</STRONG> routine calls <STRONG>tputs(</STRONG><EM>str</EM><STRONG>,</STRONG> <STRONG>1,</STRONG> <STRONG>putchar)</STRONG>. Note that
|
|
+ the output of <STRONG>putp</STRONG> always goes to <STRONG>stdout</STRONG>, not to the
|
|
<EM>fildes</EM> specified in <STRONG>setupterm</STRONG>.
|
|
|
|
The <STRONG>vidputs</STRONG> routine displays the string on the terminal in
|
|
- the video attribute mode <EM>attrs</EM>, which is any combination
|
|
- of the attributes listed in <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>. The characters
|
|
+ the video attribute mode <EM>attrs</EM>, which is any combination
|
|
+ of the attributes listed in <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>. The characters
|
|
are passed to the <STRONG>putchar</STRONG>-like routine <EM>putc</EM>.
|
|
|
|
- The <STRONG>vidattr</STRONG> routine is like the <STRONG>vidputs</STRONG> routine, except
|
|
+ The <STRONG>vidattr</STRONG> routine is like the <STRONG>vidputs</STRONG> routine, except
|
|
that it outputs through <STRONG>putchar</STRONG>.
|
|
|
|
- The <STRONG>vid_attr</STRONG> and <STRONG>vid_puts</STRONG> routines correspond to vidattr
|
|
- and vidputs, respectively. They use a set of arguments
|
|
- for representing the video attributes plus color, i.e.,
|
|
+ The <STRONG>vid_attr</STRONG> and <STRONG>vid_puts</STRONG> routines correspond to vidattr
|
|
+ and vidputs, respectively. They use a set of arguments
|
|
+ for representing the video attributes plus color, i.e.,
|
|
one of type attr_t for the attributes and one of short for
|
|
the color_pair number. The <STRONG>vid_attr</STRONG> and <STRONG>vid_puts</STRONG> routines
|
|
- are designed to use the attribute constants with the <EM>WA</EM><STRONG>_</STRONG>
|
|
- prefix. The opts argument is reserved for future use.
|
|
- Currently, applications must provide a null pointer for
|
|
+ are designed to use the attribute constants with the <EM>WA</EM><STRONG>_</STRONG>
|
|
+ prefix. The opts argument is reserved for future use.
|
|
+ Currently, applications must provide a null pointer for
|
|
that argument.
|
|
|
|
- The <STRONG>mvcur</STRONG> routine provides low-level cursor motion. It
|
|
- takes effect immediately (rather than at the next re-
|
|
+ The <STRONG>mvcur</STRONG> routine provides low-level cursor motion. It
|
|
+ takes effect immediately (rather than at the next re-
|
|
fresh).
|
|
|
|
|
|
</PRE><H3><a name="h3-Terminal-Capability-Functions">Terminal Capability Functions</a></H3><PRE>
|
|
- The <STRONG>tigetflag</STRONG>, <STRONG>tigetnum</STRONG> and <STRONG>tigetstr</STRONG> routines return the
|
|
+ The <STRONG>tigetflag</STRONG>, <STRONG>tigetnum</STRONG> and <STRONG>tigetstr</STRONG> routines return the
|
|
value of the capability corresponding to the <STRONG>terminfo</STRONG> <EM>cap-</EM>
|
|
- <EM>name</EM> passed to them, such as <STRONG>xenl</STRONG>. The <EM>capname</EM> for each
|
|
- capability is given in the table column entitled <EM>capname</EM>
|
|
+ <EM>name</EM> passed to them, such as <STRONG>xenl</STRONG>. The <EM>capname</EM> for each
|
|
+ capability is given in the table column entitled <EM>capname</EM>
|
|
code in the capabilities section of <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>.
|
|
|
|
These routines return special values to denote errors.
|
|
@@ -272,14 +277,14 @@
|
|
|
|
<STRONG>-1</STRONG> if <EM>capname</EM> is not a boolean capability, or
|
|
|
|
- <STRONG>0</STRONG> if it is canceled or absent from the terminal de-
|
|
+ <STRONG>0</STRONG> if it is canceled or absent from the terminal de-
|
|
scription.
|
|
|
|
The <STRONG>tigetnum</STRONG> routine returns
|
|
|
|
<STRONG>-2</STRONG> if <EM>capname</EM> is not a numeric capability, or
|
|
|
|
- <STRONG>-1</STRONG> if it is canceled or absent from the terminal de-
|
|
+ <STRONG>-1</STRONG> if it is canceled or absent from the terminal de-
|
|
scription.
|
|
|
|
The <STRONG>tigetstr</STRONG> routine returns
|
|
@@ -287,13 +292,13 @@
|
|
<STRONG>(char</STRONG> <STRONG>*)-1</STRONG>
|
|
if <EM>capname</EM> is not a string capability, or
|
|
|
|
- <STRONG>0</STRONG> if it is canceled or absent from the terminal de-
|
|
+ <STRONG>0</STRONG> if it is canceled or absent from the terminal de-
|
|
scription.
|
|
|
|
|
|
</PRE><H3><a name="h3-Terminal-Capability-Names">Terminal Capability Names</a></H3><PRE>
|
|
- These null-terminated arrays contain the short terminfo
|
|
- names ("codes"), the <STRONG>termcap</STRONG> names, and the long terminfo
|
|
+ These null-terminated arrays contain the short terminfo
|
|
+ names ("codes"), the <STRONG>termcap</STRONG> names, and the long terminfo
|
|
names ("fnames") for each of the predefined <STRONG>terminfo</STRONG> vari-
|
|
ables:
|
|
<STRONG>char</STRONG> <STRONG>*boolnames[]</STRONG>, <STRONG>*boolcodes[]</STRONG>, <STRONG>*boolfnames[]</STRONG>
|
|
@@ -304,119 +309,119 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-RETURN-VALUE">RETURN VALUE</a></H2><PRE>
|
|
- Routines that return an integer return <STRONG>ERR</STRONG> upon failure
|
|
- and <STRONG>OK</STRONG> (SVr4 only specifies "an integer value other than
|
|
- <STRONG>ERR</STRONG>") upon successful completion, unless otherwise noted
|
|
+ Routines that return an integer return <STRONG>ERR</STRONG> upon failure
|
|
+ and <STRONG>OK</STRONG> (SVr4 only specifies "an integer value other than
|
|
+ <STRONG>ERR</STRONG>") upon successful completion, unless otherwise noted
|
|
in the preceding routine descriptions.
|
|
|
|
Routines that return pointers always return <STRONG>NULL</STRONG> on error.
|
|
|
|
- X/Open defines no error conditions. In this implementa-
|
|
+ X/Open defines no error conditions. In this implementa-
|
|
tion
|
|
|
|
<STRONG>del_curterm</STRONG>
|
|
- returns an error if its terminal parameter is
|
|
+ returns an error if its terminal parameter is
|
|
null.
|
|
|
|
<STRONG>putp</STRONG> calls <STRONG>tputs</STRONG>, returning the same error-codes.
|
|
|
|
<STRONG>restartterm</STRONG>
|
|
- returns an error if the associated call to <STRONG>se-</STRONG>
|
|
+ returns an error if the associated call to <STRONG>se-</STRONG>
|
|
<STRONG>tupterm</STRONG> returns an error.
|
|
|
|
<STRONG>setupterm</STRONG>
|
|
- returns an error if it cannot allocate enough
|
|
- memory, or create the initial windows (stdscr,
|
|
- curscr, newscr). Other error conditions are
|
|
+ returns an error if it cannot allocate enough
|
|
+ memory, or create the initial windows (stdscr,
|
|
+ curscr, newscr). Other error conditions are
|
|
documented above.
|
|
|
|
<STRONG>tputs</STRONG>
|
|
- returns an error if the string parameter is
|
|
- null. It does not detect I/O errors: X/Open
|
|
- states that <STRONG>tputs</STRONG> ignores the return value of
|
|
+ returns an error if the string parameter is
|
|
+ null. It does not detect I/O errors: X/Open
|
|
+ states that <STRONG>tputs</STRONG> ignores the return value of
|
|
the output function <EM>putc</EM>.
|
|
|
|
|
|
</PRE><H2><a name="h2-PORTABILITY">PORTABILITY</a></H2><PRE>
|
|
X/Open notes that <STRONG>vidattr</STRONG> and <STRONG>vidputs</STRONG> may be macros.
|
|
|
|
- The function <STRONG>setterm</STRONG> is not described by X/Open and must
|
|
- be considered non-portable. All other functions are as
|
|
+ The function <STRONG>setterm</STRONG> is not described by X/Open and must
|
|
+ be considered non-portable. All other functions are as
|
|
described by X/Open.
|
|
|
|
- <STRONG>setupterm</STRONG> copies the terminal name to the array <STRONG>ttytype</STRONG>.
|
|
- This is not part of X/Open Curses, but is assumed by some
|
|
+ <STRONG>setupterm</STRONG> copies the terminal name to the array <STRONG>ttytype</STRONG>.
|
|
+ This is not part of X/Open Curses, but is assumed by some
|
|
applications.
|
|
|
|
- If configured to use the terminal-driver, e.g., for the
|
|
+ If configured to use the terminal-driver, e.g., for the
|
|
MinGW port,
|
|
|
|
- <STRONG>o</STRONG> <STRONG>setupterm</STRONG> interprets a missing/empty TERM variable as
|
|
+ <STRONG>o</STRONG> <STRONG>setupterm</STRONG> interprets a missing/empty TERM variable as
|
|
the special value "unknown".
|
|
|
|
- <STRONG>o</STRONG> <STRONG>setupterm</STRONG> allows explicit use of the the windows con-
|
|
+ <STRONG>o</STRONG> <STRONG>setupterm</STRONG> allows explicit use of the the windows con-
|
|
sole driver by checking if $TERM is set to "#win32con"
|
|
or an abbreviation of that string.
|
|
|
|
Older versions of <STRONG>ncurses</STRONG> assumed that the file descriptor
|
|
- passed to <STRONG>setupterm</STRONG> from <STRONG>initscr</STRONG> or <STRONG>newterm</STRONG> uses buffered
|
|
- I/O, and would write to the corresponding stream. In ad-
|
|
- dition to the limitation that the terminal was left in
|
|
+ passed to <STRONG>setupterm</STRONG> from <STRONG>initscr</STRONG> or <STRONG>newterm</STRONG> uses buffered
|
|
+ I/O, and would write to the corresponding stream. In ad-
|
|
+ dition to the limitation that the terminal was left in
|
|
block-buffered mode on exit (like System V curses), it was
|
|
- problematic because <STRONG>ncurses</STRONG> did not allow a reliable way
|
|
+ problematic because <STRONG>ncurses</STRONG> did not allow a reliable way
|
|
to cleanup on receiving SIGTSTP. The current version uses
|
|
- output buffers managed directly by <STRONG>ncurses</STRONG>. Some of the
|
|
+ output buffers managed directly by <STRONG>ncurses</STRONG>. Some of the
|
|
low-level functions described in this manual page write to
|
|
the standard output. They are not signal-safe. The high-
|
|
level functions in <STRONG>ncurses</STRONG> use alternate versions of these
|
|
functions using the more reliable buffering scheme.
|
|
|
|
- In System V Release 4, <STRONG>set_curterm</STRONG> has an <STRONG>int</STRONG> return type
|
|
- and returns <STRONG>OK</STRONG> or <STRONG>ERR</STRONG>. We have chosen to implement the
|
|
+ In System V Release 4, <STRONG>set_curterm</STRONG> has an <STRONG>int</STRONG> return type
|
|
+ and returns <STRONG>OK</STRONG> or <STRONG>ERR</STRONG>. We have chosen to implement the
|
|
X/Open Curses semantics.
|
|
|
|
In System V Release 4, the third argument of <STRONG>tputs</STRONG> has the
|
|
type <STRONG>int</STRONG> <STRONG>(*putc)(char)</STRONG>.
|
|
|
|
At least one implementation of X/Open Curses (Solaris) re-
|
|
- turns a value other than OK/ERR from <STRONG>tputs</STRONG>. That returns
|
|
+ turns a value other than OK/ERR from <STRONG>tputs</STRONG>. That returns
|
|
the length of the string, and does no error-checking.
|
|
|
|
- X/Open Curses prototypes <STRONG>tparm</STRONG> with a fixed number of pa-
|
|
- rameters, rather than a variable argument list. This im-
|
|
- plementation uses a variable argument list, but can be
|
|
- configured to use the fixed-parameter list. Portable ap-
|
|
- plications should provide 9 parameters after the format;
|
|
+ X/Open Curses prototypes <STRONG>tparm</STRONG> with a fixed number of pa-
|
|
+ rameters, rather than a variable argument list. This im-
|
|
+ plementation uses a variable argument list, but can be
|
|
+ configured to use the fixed-parameter list. Portable ap-
|
|
+ plications should provide 9 parameters after the format;
|
|
zeroes are fine for this purpose.
|
|
|
|
In response to comments by Thomas E. Dickey, X/Open Curses
|
|
Issue 7 proposed the <STRONG>tiparm</STRONG> function in mid-2009.
|
|
|
|
- X/Open notes that after calling <STRONG>mvcur</STRONG>, the curses state
|
|
- may not match the actual terminal state, and that an ap-
|
|
- plication should touch and refresh the window before re-
|
|
+ X/Open notes that after calling <STRONG>mvcur</STRONG>, the curses state
|
|
+ may not match the actual terminal state, and that an ap-
|
|
+ plication should touch and refresh the window before re-
|
|
suming normal curses calls. Both <STRONG>ncurses</STRONG> and System V Re-
|
|
lease 4 curses implement <STRONG>mvcur</STRONG> using the SCREEN data allo-
|
|
cated in either <STRONG>initscr</STRONG> or <STRONG>newterm</STRONG>. So though it is docu-
|
|
- mented as a terminfo function, <STRONG>mvcur</STRONG> is really a curses
|
|
+ mented as a terminfo function, <STRONG>mvcur</STRONG> is really a curses
|
|
function which is not well specified.
|
|
|
|
- X/Open states that the old location must be given for
|
|
- <STRONG>mvcur</STRONG>. This implementation allows the caller to use -1's
|
|
- for the old ordinates. In that case, the old location is
|
|
+ X/Open states that the old location must be given for
|
|
+ <STRONG>mvcur</STRONG>. This implementation allows the caller to use -1's
|
|
+ for the old ordinates. In that case, the old location is
|
|
unknown.
|
|
|
|
- Other implementions may not declare the capability name
|
|
+ Other implementions may not declare the capability name
|
|
arrays. Some provide them without declaring them. X/Open
|
|
does not specify them.
|
|
|
|
- Extended terminal capability names, e.g., as defined by
|
|
+ Extended terminal capability names, e.g., as defined by
|
|
<STRONG>tic</STRONG> <STRONG>-x</STRONG>, are not stored in the arrays described here.
|
|
|
|
|
|
</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
|
|
- <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="curs_initscr.3x.html">curs_initscr(3x)</A></STRONG>, <STRONG><A HREF="curs_kernel.3x.html">curs_kernel(3x)</A></STRONG>, <STRONG>curs_term-</STRONG>
|
|
- <STRONG><A HREF="curs_termcap.3x.html">cap(3x)</A></STRONG>, <STRONG><A HREF="curs_variables.3x.html">curs_variables(3x)</A></STRONG>, <STRONG><A HREF="term_variables.3x.html">term_variables(3x)</A></STRONG>, <STRONG>putc(3)</STRONG>,
|
|
+ <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="curs_initscr.3x.html">curs_initscr(3x)</A></STRONG>, <STRONG><A HREF="curs_kernel.3x.html">curs_kernel(3x)</A></STRONG>, <STRONG>curs_term-</STRONG>
|
|
+ <STRONG><A HREF="curs_termcap.3x.html">cap(3x)</A></STRONG>, <STRONG><A HREF="curs_variables.3x.html">curs_variables(3x)</A></STRONG>, <STRONG><A HREF="term_variables.3x.html">term_variables(3x)</A></STRONG>, <STRONG>putc(3)</STRONG>,
|
|
<STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>
|
|
|
|
|
|
Index: doc/html/man/curs_trace.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_trace.3x.html 2016-01-30 19:24:54.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_trace.3x.html 2016-10-15 23:12:21.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 2000-2010,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2000-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_trace.3x,v 1.13 2015/07/20 22:54:44 tom Exp @
|
|
+ * @Id: curs_trace.3x,v 1.14 2016/10/15 17:26:09 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -99,7 +99,7 @@
|
|
trace user and system times of updates.
|
|
|
|
<STRONG>TRACE_TPUTS</STRONG>
|
|
- trace tputs calls.
|
|
+ trace <STRONG>tputs</STRONG> calls.
|
|
|
|
<STRONG>TRACE_UPDATE</STRONG>
|
|
trace update actions, old & new screens.
|
|
Index: doc/html/man/curs_window.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/curs_window.3x.html 2016-01-30 19:24:54.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/curs_window.3x.html 2016-10-15 23:12:21.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2014,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: curs_window.3x,v 1.19 2015/07/21 08:25:23 tom Exp @
|
|
+ * @Id: curs_window.3x,v 1.20 2016/10/15 17:26:09 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -218,7 +218,7 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-BUGS">BUGS</a></H2><PRE>
|
|
- The subwindow functions (<EM>subwin</EM>, <EM>derwin</EM>, <EM>mvderwin</EM>, <STRONG>wsyn-</STRONG>
|
|
+ The subwindow functions (<STRONG>subwin</STRONG>, <STRONG>derwin</STRONG>, <STRONG>mvderwin</STRONG>, <STRONG>wsyn-</STRONG>
|
|
<STRONG>cup</STRONG>, <STRONG>wsyncdown</STRONG>, <STRONG>wcursyncup</STRONG>, <STRONG>syncok</STRONG>) are flaky, incomplete-
|
|
ly implemented, and not well tested.
|
|
|
|
Index: doc/html/man/default_colors.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/default_colors.3x.html 2016-01-30 19:24:54.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/default_colors.3x.html 2016-10-15 23:12:22.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2010,2011 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2011,2016 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 +27,7 @@
|
|
* authorization. *
|
|
****************************************************************************
|
|
* Author: Thomas E. Dickey 1997,1999,2000,2005
|
|
- * @Id: default_colors.3x,v 1.23 2011/01/03 21:52:27 Tim.van.der.Molen Exp @
|
|
+ * @Id: default_colors.3x,v 1.25 2016/10/15 17:16:48 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -59,9 +59,9 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-DESCRIPTION">DESCRIPTION</a></H2><PRE>
|
|
- The <EM>use</EM><STRONG>_</STRONG><EM>default</EM><STRONG>_</STRONG><EM>colors()</EM> and <EM>assume</EM><STRONG>_</STRONG><EM>default</EM><STRONG>_</STRONG><EM>colors()</EM> func-
|
|
- tions are extensions to the curses library. They are used
|
|
- with terminals that support ISO 6429 color, or equivalent.
|
|
+ The <STRONG>use_default_colors</STRONG> and <STRONG>assume_default_colors</STRONG> functions
|
|
+ are extensions to the curses library. They are used with
|
|
+ terminals that support ISO 6429 color, or equivalent.
|
|
These terminals allow the application to reset color to an
|
|
unspecified default value (e.g., with SGR 39 or SGR 49).
|
|
|
|
@@ -72,19 +72,19 @@
|
|
there are several implementations of the <STRONG>ls</STRONG> program which
|
|
use colors to denote different file types or permissions.
|
|
These "color ls" programs do not necessarily modify the
|
|
- background color, typically using only the <EM>setaf</EM> terminfo
|
|
+ background color, typically using only the <STRONG>setaf</STRONG> terminfo
|
|
capability to set the foreground color. Full-screen
|
|
applications that use default colors can achieve similar
|
|
visual effects.
|
|
|
|
- The first function, <EM>use</EM><STRONG>_</STRONG><EM>default</EM><STRONG>_</STRONG><EM>colors()</EM> tells the curses
|
|
+ The first function, <STRONG>use_default_colors</STRONG> tells the curses
|
|
library to assign terminal default foreground/background
|
|
colors to color number -1. So init_pair(x,COLOR_RED,-1)
|
|
will initialize pair x as red on default background and
|
|
init_pair(x,-1,COLOR_BLUE) will initialize pair x as
|
|
default foreground on blue.
|
|
|
|
- The other, <EM>assume</EM><STRONG>_</STRONG><EM>default</EM><STRONG>_</STRONG><EM>colors()</EM> is a refinement which
|
|
+ The other, <STRONG>assume_default_colors</STRONG> is a refinement which
|
|
tells which colors to paint for color pair 0. This func-
|
|
tion recognizes a special color number -1, which denotes
|
|
the default terminal color.
|
|
@@ -95,23 +95,23 @@
|
|
|
|
These are ncurses extensions. For other curses implemen-
|
|
tations, color number -1 does not mean anything, just as
|
|
- for ncurses before a successful call of <EM>use</EM><STRONG>_</STRONG><EM>default</EM><STRONG>_</STRONG><EM>col-</EM>
|
|
- <EM>ors()</EM> or <EM>assume</EM><STRONG>_</STRONG><EM>default</EM><STRONG>_</STRONG><EM>colors()</EM>.
|
|
+ for ncurses before a successful call of <STRONG>use_default_colors</STRONG>
|
|
+ or <STRONG>assume_default_colors</STRONG>.
|
|
|
|
Other curses implementations do not allow an application
|
|
to modify color pair 0. They assume that the background
|
|
is COLOR_BLACK, but do not ensure that the color pair 0 is
|
|
painted to match the assumption. If your application does
|
|
- not use either <EM>use</EM><STRONG>_</STRONG><EM>default</EM><STRONG>_</STRONG><EM>colors()</EM> or <EM>assume</EM><STRONG>_</STRONG><EM>default</EM><STRONG>_</STRONG><EM>col-</EM>
|
|
- <EM>ors()</EM> ncurses will paint a white foreground (text) with
|
|
- black background for color pair 0.
|
|
+ not use either <STRONG>use_default_colors</STRONG> or <STRONG>assume_default_colors</STRONG>
|
|
+ ncurses will paint a white foreground (text) with black
|
|
+ background for color pair 0.
|
|
|
|
|
|
</PRE><H2><a name="h2-RETURN-VALUE">RETURN VALUE</a></H2><PRE>
|
|
These functions return the integer <STRONG>ERR</STRONG> upon failure and <STRONG>OK</STRONG>
|
|
on success. They will fail if either the terminal does
|
|
- not support the <EM>orig</EM><STRONG>_</STRONG><EM>pair</EM> or <EM>orig</EM><STRONG>_</STRONG><EM>colors</EM> capability. If
|
|
- the <EM>initialize</EM><STRONG>_</STRONG><EM>pair</EM> capability is not found, this causes
|
|
+ not support the <STRONG>orig_pair</STRONG> or <STRONG>orig_colors</STRONG> capability. If
|
|
+ the <STRONG>initialize_pair</STRONG> capability is not found, this causes
|
|
an error as well.
|
|
|
|
|
|
@@ -120,24 +120,24 @@
|
|
accepts negative arguments to specify default foreground
|
|
or background colors.
|
|
|
|
- The <EM>use</EM><STRONG>_</STRONG><EM>default</EM><STRONG>_</STRONG><EM>colors()</EM> function was added to support
|
|
- <EM>ded</EM>. This is a full-screen application which uses curses
|
|
- to manage only part of the screen. The bottom portion of
|
|
- the screen, which is of adjustable size, is left uncolored
|
|
- to display the results from shell commands. The top por-
|
|
- tion of the screen colors filenames using a scheme like
|
|
- the "color ls" programs. Attempting to manage the back-
|
|
- ground color of the screen for this application would give
|
|
- unsatisfactory results for a variety of reasons. This
|
|
- extension was devised after noting that color xterm (and
|
|
- similar programs) provides a background color which does
|
|
- not necessarily correspond to any of the ANSI colors.
|
|
- While a special terminfo entry could be constructed using
|
|
- nine colors, there was no mechanism provided within curses
|
|
- to account for the related <EM>orig</EM><STRONG>_</STRONG><EM>pair</EM> and <EM>back</EM><STRONG>_</STRONG><EM>color</EM><STRONG>_</STRONG><EM>erase</EM>
|
|
+ The <STRONG>use_default_colors</STRONG> function was added to support <EM>ded</EM>.
|
|
+ This is a full-screen application which uses curses to
|
|
+ manage only part of the screen. The bottom portion of the
|
|
+ screen, which is of adjustable size, is left uncolored to
|
|
+ display the results from shell commands. The top portion
|
|
+ of the screen colors filenames using a scheme like the
|
|
+ "color ls" programs. Attempting to manage the background
|
|
+ color of the screen for this application would give unsat-
|
|
+ isfactory results for a variety of reasons. This exten-
|
|
+ sion was devised after noting that color xterm (and simi-
|
|
+ lar programs) provides a background color which does not
|
|
+ necessarily correspond to any of the ANSI colors. While a
|
|
+ special terminfo entry could be constructed using nine
|
|
+ colors, there was no mechanism provided within curses to
|
|
+ account for the related <STRONG>orig_pair</STRONG> and <STRONG>back_color_erase</STRONG>
|
|
capabilities.
|
|
|
|
- The <EM>assume</EM><STRONG>_</STRONG><EM>default</EM><STRONG>_</STRONG><EM>colors()</EM> function was added to solve a
|
|
+ The <STRONG>assume_default_colors</STRONG> function was added to solve a
|
|
different problem: support for applications which would
|
|
use environment variables and other configuration to
|
|
bypass curses' notion of the terminal's default colors,
|
|
Index: doc/html/man/form.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/form.3x.html 2016-09-10 22:14:40.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/form.3x.html 2016-10-15 23:12:22.000000000 +0000
|
|
@@ -235,7 +235,7 @@
|
|
<STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG> and related pages whose names begin "form_" for
|
|
detailed descriptions of the entry points.
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
|
|
Index: doc/html/man/infocmp.1m.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/infocmp.1m.html 2016-09-10 22:14:40.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/infocmp.1m.html 2016-10-15 23:12:22.000000000 +0000
|
|
@@ -1,7 +1,7 @@
|
|
<!--
|
|
* t
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2014,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 +27,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: infocmp.1m,v 1.57 2015/09/05 20:50:22 tom Exp @
|
|
+ * @Id: infocmp.1m,v 1.58 2016/10/01 17:15:45 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -51,7 +51,7 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-SYNOPSIS">SYNOPSIS</a></H2><PRE>
|
|
- <STRONG>infocmp</STRONG> [<STRONG>-1CDEFGIKLTUVcdegilnpqrtux</STRONG>]
|
|
+ <STRONG>infocmp</STRONG> [<STRONG>-1CDEFGIKLTUVWcdegilnpqrtux</STRONG>]
|
|
[<STRONG>-v</STRONG> <EM>n</EM>] [<STRONG>-s</STRONG> <STRONG>d</STRONG>| <STRONG>i</STRONG>| <STRONG>l</STRONG>| <STRONG>c</STRONG>] [<STRONG>-Q</STRONG> <EM>n</EM>] [<STRONG>-R</STRONG> <STRONG>subset</STRONG>]
|
|
[<STRONG>-w</STRONG> <EM>width</EM>] [<STRONG>-A</STRONG> <EM>directory</EM>] [<STRONG>-B</STRONG> <EM>directory</EM>]
|
|
[<EM>termname</EM>...]
|
|
@@ -441,10 +441,13 @@
|
|
the program runs. Higher values of n induce greater
|
|
verbosity.
|
|
|
|
+ <STRONG>-W</STRONG> By itself, the <STRONG>-w</STRONG> option will not force long strings
|
|
+ to be wrapped. Use the <STRONG>-W</STRONG> option to do this.
|
|
+
|
|
<STRONG>-w</STRONG> <EM>width</EM>
|
|
changes the output to <EM>width</EM> characters.
|
|
|
|
- <STRONG>-x</STRONG> print information for user-defined capabilities.
|
|
+ <STRONG>-x</STRONG> print information for user-defined capabilities.
|
|
These are extensions to the terminfo repertoire which
|
|
can be loaded using the <STRONG>-x</STRONG> option of <STRONG>tic</STRONG>.
|
|
|
|
@@ -455,13 +458,13 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-EXTENSIONS">EXTENSIONS</a></H2><PRE>
|
|
- The <STRONG>-0</STRONG>, <STRONG>-1</STRONG>, <STRONG>-E</STRONG>, <STRONG>-F</STRONG>, <STRONG>-G</STRONG>, <STRONG>-R</STRONG>, <STRONG>-T</STRONG>, <STRONG>-V</STRONG>, <STRONG>-a</STRONG>, <STRONG>-e</STRONG>, <STRONG>-f</STRONG>, <STRONG>-g</STRONG>, <STRONG>-i</STRONG>,
|
|
- <STRONG>-l</STRONG>, <STRONG>-p</STRONG>, <STRONG>-q</STRONG> and <STRONG>-t</STRONG> options are not supported in SVr4
|
|
+ The <STRONG>-0</STRONG>, <STRONG>-1</STRONG>, <STRONG>-E</STRONG>, <STRONG>-F</STRONG>, <STRONG>-G</STRONG>, <STRONG>-R</STRONG>, <STRONG>-T</STRONG>, <STRONG>-V</STRONG>, <STRONG>-a</STRONG>, <STRONG>-e</STRONG>, <STRONG>-f</STRONG>, <STRONG>-g</STRONG>, <STRONG>-i</STRONG>,
|
|
+ <STRONG>-l</STRONG>, <STRONG>-p</STRONG>, <STRONG>-q</STRONG> and <STRONG>-t</STRONG> options are not supported in SVr4
|
|
curses.
|
|
|
|
The <STRONG>-r</STRONG> option's notion of `termcap' capabilities is System
|
|
- V Release 4's. Actual BSD curses versions will have a
|
|
- more restricted set. To see only the 4.4BSD set, use <STRONG>-r</STRONG>
|
|
+ V Release 4's. Actual BSD curses versions will have a
|
|
+ more restricted set. To see only the 4.4BSD set, use <STRONG>-r</STRONG>
|
|
<STRONG>-RBSD</STRONG>.
|
|
|
|
|
|
@@ -470,12 +473,12 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
|
|
- <STRONG><A HREF="captoinfo.1m.html">captoinfo(1m)</A></STRONG>, <STRONG><A HREF="infotocap.1m.html">infotocap(1m)</A></STRONG>, <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG>, <STRONG><A HREF="toe.1m.html">toe(1m)</A></STRONG>,
|
|
+ <STRONG><A HREF="captoinfo.1m.html">captoinfo(1m)</A></STRONG>, <STRONG><A HREF="infotocap.1m.html">infotocap(1m)</A></STRONG>, <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG>, <STRONG><A HREF="toe.1m.html">toe(1m)</A></STRONG>,
|
|
<STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>.
|
|
|
|
http://invisible-island.net/ncurses/tctest.html
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
</PRE><H2><a name="h2-AUTHOR">AUTHOR</a></H2><PRE>
|
|
Index: doc/html/man/infotocap.1m.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/infotocap.1m.html 2016-09-10 22:14:40.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/infotocap.1m.html 2016-10-15 23:12:22.000000000 +0000
|
|
@@ -1,7 +1,7 @@
|
|
<!--
|
|
* t
|
|
****************************************************************************
|
|
- * Copyright (c) 1999-2006,2010 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1999-2010,2016 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 +27,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: infotocap.1m,v 1.11 2010/12/04 18:38:55 tom Exp @
|
|
+ * @Id: infotocap.1m,v 1.12 2016/10/15 17:26:09 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -81,14 +81,14 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-NOTES">NOTES</a></H2><PRE>
|
|
- This utility is actually a link to <EM>tic</EM>, running in <EM>-C</EM>
|
|
- mode. You can use other <EM>tic</EM> options such as <STRONG>-f</STRONG> and <STRONG>-x</STRONG>.
|
|
+ This utility is actually a link to <STRONG>tic</STRONG>, running in <EM>-C</EM>
|
|
+ mode. You can use other <STRONG>tic</STRONG> options such as <STRONG>-f</STRONG> and <STRONG>-x</STRONG>.
|
|
|
|
|
|
</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
|
|
<STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG>, <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
</PRE><H2><a name="h2-AUTHOR">AUTHOR</a></H2><PRE>
|
|
Index: doc/html/man/legacy_coding.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/legacy_coding.3x.html 2016-01-30 19:24:56.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/legacy_coding.3x.html 2016-10-15 23:12:23.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 2005-2006,2010 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2005-2010,2016 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 +27,7 @@
|
|
* authorization. *
|
|
****************************************************************************
|
|
* Author: Thomas E. Dickey
|
|
- * @Id: legacy_coding.3x,v 1.4 2010/12/04 18:49:20 tom Exp @
|
|
+ * @Id: legacy_coding.3x,v 1.5 2016/10/15 17:02:31 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -57,7 +57,7 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-DESCRIPTION">DESCRIPTION</a></H2><PRE>
|
|
- The <EM>use</EM><STRONG>_</STRONG><EM>legacy</EM><STRONG>_</STRONG><EM>coding()</EM> function is an extension to the
|
|
+ The <STRONG>use_legacy_coding</STRONG> function is an extension to the
|
|
curses library. It allows the caller to change the result
|
|
of <STRONG>unctrl</STRONG>, and suppress related checks within the library
|
|
that would normally cause nonprinting characters to be
|
|
Index: doc/html/man/menu.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/menu.3x.html 2016-09-10 22:14:41.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/menu.3x.html 2016-10-15 23:12:23.000000000 +0000
|
|
@@ -217,7 +217,7 @@
|
|
<STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG> and related pages whose names begin "menu_" for
|
|
detailed descriptions of the entry points.
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
|
|
Index: doc/html/man/menu_format.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/menu_format.3x.html 2016-01-30 19:24:57.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/menu_format.3x.html 2016-10-15 23:12:23.000000000 +0000
|
|
@@ -1,7 +1,7 @@
|
|
<!--
|
|
* t
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 +27,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: menu_format.3x,v 1.13 2015/12/05 23:01:16 tom Exp @
|
|
+ * @Id: menu_format.3x,v 1.14 2016/10/15 17:02:31 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -61,7 +61,7 @@
|
|
of the given menu. If this size is too small to display
|
|
all menu items, the menu will be made scrollable. If this
|
|
size is larger than the menus subwindow and the subwindow
|
|
- is too small to display all menu items, <STRONG>post_menu()</STRONG> will
|
|
+ is too small to display all menu items, <STRONG>post_menu</STRONG> will
|
|
fail.
|
|
|
|
The default format is 16 rows, 1 column. Calling
|
|
Index: doc/html/man/menu_post.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/menu_post.3x.html 2016-01-30 19:24:57.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/menu_post.3x.html 2016-10-15 23:12:23.000000000 +0000
|
|
@@ -1,7 +1,7 @@
|
|
<!--
|
|
* t
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 +27,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: menu_post.3x,v 1.12 2015/12/05 23:42:45 tom Exp @
|
|
+ * @Id: menu_post.3x,v 1.13 2016/10/15 17:02:31 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -89,8 +89,8 @@
|
|
tion function.
|
|
|
|
<STRONG>E_NO_ROOM</STRONG>
|
|
- Menu is too large for its window. You should consider
|
|
- to use <STRONG>set_menu_format()</STRONG> to solve the problem.
|
|
+ Menu is too large for its window. You should con-
|
|
+ sider using <STRONG>set_menu_format</STRONG> to solve the problem.
|
|
|
|
<STRONG>E_NOT_POSTED</STRONG>
|
|
The menu has not been posted.
|
|
Index: doc/html/man/ncurses.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/ncurses.3x.html 2016-09-10 22:14:41.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/ncurses.3x.html 2016-10-15 23:12:23.000000000 +0000
|
|
@@ -60,7 +60,7 @@
|
|
sonable optimization. This implementation is "new curses"
|
|
(ncurses) and is the approved replacement for 4.4BSD clas-
|
|
sic curses, which has been discontinued. This describes
|
|
- <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
The <STRONG>ncurses</STRONG> library emulates the curses library of System
|
|
V Release 4 UNIX, and XPG4 (X/Open Portability Guide)
|
|
Index: doc/html/man/panel.3x.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/panel.3x.html 2016-09-10 22:14:41.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/panel.3x.html 2016-10-15 23:12:23.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: panel.3x,v 1.19 2015/12/05 23:42:45 tom Exp @
|
|
+ * @Id: panel.3x,v 1.20 2016/10/15 17:02:31 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -98,13 +98,13 @@
|
|
(causes it to be displayed above any other
|
|
panel) and returns a pointer to the new panel.
|
|
|
|
- <STRONG>update_panels()</STRONG>
|
|
+ <STRONG>update_panels</STRONG>
|
|
refreshes the virtual screen to reflect the rela-
|
|
tions between the panels in the stack, but does not
|
|
- call doupdate() to refresh the physical screen.
|
|
- Use this function and not <STRONG>wrefresh</STRONG> or <STRONG>wnoutrefresh</STRONG>.
|
|
+ call <STRONG>doupdate</STRONG> to refresh the physical screen. Use
|
|
+ this function and not <STRONG>wrefresh</STRONG> or <STRONG>wnoutrefresh</STRONG>.
|
|
<STRONG>update_panels</STRONG> may be called more than once before a
|
|
- call to doupdate(), but doupdate() is the function
|
|
+ call to <STRONG>doupdate</STRONG>, but <STRONG>doupdate</STRONG> is the function
|
|
responsible for updating the physical screen.
|
|
|
|
<STRONG>del_panel(pan)</STRONG>
|
|
@@ -138,8 +138,8 @@
|
|
moves the given panel window so that its upper-left
|
|
corner is at <STRONG>starty</STRONG>, <STRONG>startx</STRONG>. It does not change
|
|
the position of the panel in the stack. Be sure to
|
|
- use this function, not <STRONG>mvwin()</STRONG>, to move a panel
|
|
- window.
|
|
+ use this function, not <STRONG>mvwin</STRONG>, to move a panel win-
|
|
+ dow.
|
|
|
|
<STRONG>replace_panel(pan,window)</STRONG>
|
|
replaces the current window of panel with <STRONG>window</STRONG>
|
|
@@ -182,20 +182,19 @@
|
|
are merely similar. The programmer is cautioned not to
|
|
directly use <STRONG>PANEL</STRONG> fields.
|
|
|
|
- The functions <STRONG>show_panel()</STRONG> and <STRONG>top_panel()</STRONG> are identical
|
|
- in this implementation, and work equally well with dis-
|
|
- played or hidden panels. In the native System V implemen-
|
|
- tation, <STRONG>show_panel()</STRONG> is intended for making a hidden panel
|
|
- visible (at the top of the stack) and <STRONG>top_panel()</STRONG> is
|
|
- intended for making an already-visible panel move to the
|
|
- top of the stack. You are cautioned to use the correct
|
|
- function to ensure compatibility with native panel
|
|
- libraries.
|
|
+ The functions <STRONG>show_panel</STRONG> and <STRONG>top_panel</STRONG> are identical in
|
|
+ this implementation, and work equally well with displayed
|
|
+ or hidden panels. In the native System V implementation,
|
|
+ <STRONG>show_panel</STRONG> is intended for making a hidden panel visible
|
|
+ (at the top of the stack) and <STRONG>top_panel</STRONG> is intended for
|
|
+ making an already-visible panel move to the top of the
|
|
+ stack. You are cautioned to use the correct function to
|
|
+ ensure compatibility with native panel libraries.
|
|
|
|
|
|
</PRE><H2><a name="h2-NOTE">NOTE</a></H2><PRE>
|
|
- In your library list, libpanel.a should be before libn-
|
|
- curses.a; that is, you want to say `-lpanel -lncurses',
|
|
+ In your library list, libpanel.a should be before libn-
|
|
+ curses.a; that is, you want to say `-lpanel -lncurses',
|
|
not the other way around (which would usually give a link-
|
|
error).
|
|
|
|
@@ -209,13 +208,13 @@
|
|
</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
|
|
<STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="curs_variables.3x.html">curs_variables(3x)</A></STRONG>,
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
</PRE><H2><a name="h2-AUTHOR">AUTHOR</a></H2><PRE>
|
|
- Originally written by Warren Tucker <wht@n4hgf.mt-
|
|
- park.ga.us>, primarily to assist in porting u386mon to
|
|
- systems without a native panels library. Repackaged for
|
|
+ Originally written by Warren Tucker <wht@n4hgf.mt-
|
|
+ park.ga.us>, primarily to assist in porting u386mon to
|
|
+ systems without a native panels library. Repackaged for
|
|
ncurses by Zeyd ben-Halim.
|
|
|
|
|
|
Index: doc/html/man/tabs.1.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/tabs.1.html 2016-09-10 22:14:41.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/tabs.1.html 2016-10-15 23:12:23.000000000 +0000
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: tabs.1,v 1.12 2016/04/02 23:40:46 tom Exp @
|
|
+ * @Id: tabs.1,v 1.13 2016/10/15 16:16:38 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -148,7 +148,7 @@
|
|
terminal database provide this capability.
|
|
|
|
<STRONG>o</STRONG> There is no counterpart in X/Open Curses Issue 7 for
|
|
- this utility, unlike <STRONG><A HREF="tput.3x.html">tput(3x)</A></STRONG>.
|
|
+ this utility, unlike <STRONG><A HREF="tput.1.html">tput(1)</A></STRONG>.
|
|
|
|
The <STRONG>-d</STRONG> (debug) and <STRONG>-n</STRONG> (no-op) options are extensions not
|
|
provided by other implementations.
|
|
@@ -164,7 +164,7 @@
|
|
</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
|
|
<STRONG><A HREF="tset.1.html">tset(1)</A></STRONG>, <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>, <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>.
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
|
|
Index: doc/html/man/term.5.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/term.5.html 2016-01-30 19:24:58.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/term.5.html 2016-10-15 23:12:24.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: term.5,v 1.22 2015/04/26 14:50:23 tom Exp @
|
|
+ * @Id: term.5,v 1.23 2016/10/15 17:02:31 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -95,7 +95,7 @@
|
|
made.
|
|
|
|
The compiled file is created with the <STRONG>tic</STRONG> program, and
|
|
- read by the routine <EM>setupterm</EM>. The file is divided into
|
|
+ read by the routine <STRONG>setupterm</STRONG>. The file is divided into
|
|
six parts: the header, terminal names, boolean flags, num-
|
|
bers, strings, and string table.
|
|
|
|
@@ -207,13 +207,13 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-PORTABILITY">PORTABILITY</a></H2><PRE>
|
|
- Note that it is possible for <EM>setupterm</EM> to expect a differ-
|
|
+ Note that it is possible for <STRONG>setupterm</STRONG> to expect a differ-
|
|
ent set of capabilities than are actually present in the
|
|
file. Either the database may have been updated since
|
|
- <EM>setupterm</EM> has been recompiled (resulting in extra unrecog-
|
|
+ <STRONG>setupterm</STRONG> has been recompiled (resulting in extra unrecog-
|
|
nized entries in the file) or the program may have been
|
|
recompiled more recently than the database was updated
|
|
- (resulting in missing entries). The routine <EM>setupterm</EM>
|
|
+ (resulting in missing entries). The routine <STRONG>setupterm</STRONG>
|
|
must be prepared for both possibilities - this is why the
|
|
numbers and sizes are included. Also, new capabilities
|
|
must always be added at the end of the lists of boolean,
|
|
Index: doc/html/man/terminfo.5.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/terminfo.5.html 2016-09-10 22:14:42.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/terminfo.5.html 2016-10-15 23:12:24.000000000 +0000
|
|
@@ -5,7 +5,7 @@
|
|
* Note: this must be run through tbl before nroff.
|
|
* The magic cookie on the first line triggers this under some man programs.
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2012,2013 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2013,2016 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 *
|
|
@@ -31,9 +31,9 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: terminfo.head,v 1.21 2013/03/09 22:11:36 tom Exp @
|
|
+ * @Id: terminfo.head,v 1.22 2016/10/15 17:02:31 tom Exp @
|
|
* Head of terminfo man page ends here
|
|
- * @Id: terminfo.tail,v 1.69 2015/04/26 14:47:23 tom Exp @
|
|
+ * @Id: terminfo.tail,v 1.72 2016/10/15 18:34:58 tom Exp @
|
|
* Beginning of terminfo.tail file
|
|
* This file is part of ncurses.
|
|
* See "terminfo.head" for copyright.
|
|
@@ -75,7 +75,7 @@
|
|
nals by giving a set of capabilities which they have, by
|
|
specifying how to perform screen operations, and by speci-
|
|
fying padding requirements and initialization sequences.
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
Entries in <EM>terminfo</EM> consist of a sequence of `,' separated
|
|
fields (embedded commas may be escaped with a backslash or
|
|
@@ -1167,56 +1167,63 @@
|
|
|
|
A delay in milliseconds may appear anywhere in a string
|
|
capability, enclosed in $<..> brackets, as in <STRONG>el</STRONG>=\EK$<5>,
|
|
- and padding characters are supplied by <EM>tputs</EM> to provide
|
|
- this delay. The delay must be a number with at most one
|
|
- decimal place of precision; it may be followed by suffixes
|
|
- "*" or "/" or both. A "*" indicates that the padding
|
|
- required is proportional to the number of lines affected
|
|
- by the operation, and the amount given is the per-
|
|
- affected-unit padding required. (In the case of insert
|
|
- character, the factor is still the number of <EM>lines</EM>
|
|
- affected.) Normally, padding is advisory if the device
|
|
- has the <STRONG>xon</STRONG> capability; it is used for cost computation
|
|
- but does not trigger delays. A "/" suffix indicates that
|
|
- the padding is mandatory and forces a delay of the given
|
|
- number of milliseconds even on devices for which <STRONG>xon</STRONG> is
|
|
- present to indicate flow control.
|
|
+ and padding characters are supplied by <STRONG>tputs</STRONG> to provide
|
|
+ this delay.
|
|
|
|
- Sometimes individual capabilities must be commented out.
|
|
- To do this, put a period before the capability name. For
|
|
+ <STRONG>o</STRONG> The delay must be a number with at most one decimal
|
|
+ place of precision; it may be followed by suffixes "*"
|
|
+ or "/" or both.
|
|
+
|
|
+ <STRONG>o</STRONG> A "*" indicates that the padding required is propor-
|
|
+ tional to the number of lines affected by the opera-
|
|
+ tion, and the amount given is the per-affected-unit
|
|
+ padding required. (In the case of insert character,
|
|
+ the factor is still the number of <EM>lines</EM> affected.)
|
|
+
|
|
+ Normally, padding is advisory if the device has the
|
|
+ <STRONG>xon</STRONG> capability; it is used for cost computation but
|
|
+ does not trigger delays.
|
|
+
|
|
+ <STRONG>o</STRONG> A "/" suffix indicates that the padding is mandatory
|
|
+ and forces a delay of the given number of milliseconds
|
|
+ even on devices for which <STRONG>xon</STRONG> is present to indicate
|
|
+ flow control.
|
|
+
|
|
+ Sometimes individual capabilities must be commented out.
|
|
+ To do this, put a period before the capability name. For
|
|
example, see the second <STRONG>ind</STRONG> in the example above.
|
|
|
|
|
|
</PRE><H3><a name="h3-Fetching-Compiled-Descriptions">Fetching Compiled Descriptions</a></H3><PRE>
|
|
- The <STRONG>ncurses</STRONG> library searches for terminal descriptions in
|
|
+ The <STRONG>ncurses</STRONG> library searches for terminal descriptions in
|
|
several places. It uses only the first description found.
|
|
- The library has a compiled-in list of places to search
|
|
- which can be overridden by environment variables. Before
|
|
- starting to search, <STRONG>ncurses</STRONG> eliminates duplicates in its
|
|
+ The library has a compiled-in list of places to search
|
|
+ which can be overridden by environment variables. Before
|
|
+ starting to search, <STRONG>ncurses</STRONG> eliminates duplicates in its
|
|
search list.
|
|
|
|
- <STRONG>o</STRONG> If the environment variable TERMINFO is set, it is
|
|
- interpreted as the pathname of a directory containing
|
|
- the compiled description you are working on. Only
|
|
+ <STRONG>o</STRONG> If the environment variable TERMINFO is set, it is
|
|
+ interpreted as the pathname of a directory containing
|
|
+ the compiled description you are working on. Only
|
|
that directory is searched.
|
|
|
|
- <STRONG>o</STRONG> If TERMINFO is not set, <STRONG>ncurses</STRONG> will instead look in
|
|
- the directory <STRONG>$HOME/.terminfo</STRONG> for a compiled descrip-
|
|
+ <STRONG>o</STRONG> If TERMINFO is not set, <STRONG>ncurses</STRONG> will instead look in
|
|
+ the directory <STRONG>$HOME/.terminfo</STRONG> for a compiled descrip-
|
|
tion.
|
|
|
|
- <STRONG>o</STRONG> Next, if the environment variable TERMINFO_DIRS is
|
|
+ <STRONG>o</STRONG> Next, if the environment variable TERMINFO_DIRS is
|
|
set, <STRONG>ncurses</STRONG> will interpret the contents of that vari-
|
|
- able as a list of colon-separated directories (or
|
|
+ able as a list of colon-separated directories (or
|
|
database files) to be searched.
|
|
|
|
- An empty directory name (i.e., if the variable begins
|
|
- or ends with a colon, or contains adjacent colons) is
|
|
- interpreted as the system location <EM>/usr/share/ter-</EM>
|
|
+ An empty directory name (i.e., if the variable begins
|
|
+ or ends with a colon, or contains adjacent colons) is
|
|
+ interpreted as the system location <EM>/usr/share/ter-</EM>
|
|
<EM>minfo</EM>.
|
|
|
|
<STRONG>o</STRONG> Finally, <STRONG>ncurses</STRONG> searches these compiled-in locations:
|
|
|
|
- <STRONG>o</STRONG> a list of directories
|
|
+ <STRONG>o</STRONG> a list of directories
|
|
(/usr/local/ncurses/share/terminfo:/usr/share/ter-
|
|
minfo), and
|
|
|
|
@@ -1225,91 +1232,91 @@
|
|
|
|
|
|
</PRE><H3><a name="h3-Preparing-Descriptions">Preparing Descriptions</a></H3><PRE>
|
|
- We now outline how to prepare descriptions of terminals.
|
|
- The most effective way to prepare a terminal description
|
|
- is by imitating the description of a similar terminal in
|
|
- <EM>terminfo</EM> and to build up a description gradually, using
|
|
+ We now outline how to prepare descriptions of terminals.
|
|
+ The most effective way to prepare a terminal description
|
|
+ is by imitating the description of a similar terminal in
|
|
+ <EM>terminfo</EM> and to build up a description gradually, using
|
|
partial descriptions with <EM>vi</EM> or some other screen-oriented
|
|
- program to check that they are correct. Be aware that a
|
|
+ program to check that they are correct. Be aware that a
|
|
very unusual terminal may expose deficiencies in the abil-
|
|
- ity of the <EM>terminfo</EM> file to describe it or bugs in the
|
|
+ ity of the <EM>terminfo</EM> file to describe it or bugs in the
|
|
screen-handling code of the test program.
|
|
|
|
- To get the padding for insert line right (if the terminal
|
|
+ To get the padding for insert line right (if the terminal
|
|
manufacturer did not document it) a severe test is to edit
|
|
- a large file at 9600 baud, delete 16 or so lines from the
|
|
- middle of the screen, then hit the "u" key several times
|
|
- quickly. If the terminal messes up, more padding is usu-
|
|
- ally needed. A similar test can be used for insert char-
|
|
+ a large file at 9600 baud, delete 16 or so lines from the
|
|
+ middle of the screen, then hit the "u" key several times
|
|
+ quickly. If the terminal messes up, more padding is usu-
|
|
+ ally needed. A similar test can be used for insert char-
|
|
acter.
|
|
|
|
|
|
</PRE><H3><a name="h3-Basic-Capabilities">Basic Capabilities</a></H3><PRE>
|
|
- The number of columns on each line for the terminal is
|
|
- given by the <STRONG>cols</STRONG> numeric capability. If the terminal is
|
|
- a CRT, then the number of lines on the screen is given by
|
|
+ The number of columns on each line for the terminal is
|
|
+ given by the <STRONG>cols</STRONG> numeric capability. If the terminal is
|
|
+ a CRT, then the number of lines on the screen is given by
|
|
the <STRONG>lines</STRONG> capability. If the terminal wraps around to the
|
|
- beginning of the next line when it reaches the right mar-
|
|
+ beginning of the next line when it reaches the right mar-
|
|
gin, then it should have the <STRONG>am</STRONG> capability. If the termi-
|
|
- nal can clear its screen, leaving the cursor in the home
|
|
- position, then this is given by the <STRONG>clear</STRONG> string capabil-
|
|
- ity. If the terminal overstrikes (rather than clearing a
|
|
- position when a character is struck over) then it should
|
|
- have the <STRONG>os</STRONG> capability. If the terminal is a printing
|
|
- terminal, with no soft copy unit, give it both <STRONG>hc</STRONG> and <STRONG>os</STRONG>.
|
|
- (<STRONG>os</STRONG> applies to storage scope terminals, such as TEKTRONIX
|
|
- 4010 series, as well as hard copy and APL terminals.) If
|
|
+ nal can clear its screen, leaving the cursor in the home
|
|
+ position, then this is given by the <STRONG>clear</STRONG> string capabil-
|
|
+ ity. If the terminal overstrikes (rather than clearing a
|
|
+ position when a character is struck over) then it should
|
|
+ have the <STRONG>os</STRONG> capability. If the terminal is a printing
|
|
+ terminal, with no soft copy unit, give it both <STRONG>hc</STRONG> and <STRONG>os</STRONG>.
|
|
+ (<STRONG>os</STRONG> applies to storage scope terminals, such as TEKTRONIX
|
|
+ 4010 series, as well as hard copy and APL terminals.) If
|
|
there is a code to move the cursor to the left edge of the
|
|
current row, give this as <STRONG>cr</STRONG>. (Normally this will be car-
|
|
- riage return, control M.) If there is a code to produce
|
|
+ riage return, control M.) If there is a code to produce
|
|
an audible signal (bell, beep, etc) give this as <STRONG>bel</STRONG>.
|
|
|
|
- If there is a code to move the cursor one position to the
|
|
- left (such as backspace) that capability should be given
|
|
- as <STRONG>cub1</STRONG>. Similarly, codes to move to the right, up, and
|
|
+ If there is a code to move the cursor one position to the
|
|
+ left (such as backspace) that capability should be given
|
|
+ as <STRONG>cub1</STRONG>. Similarly, codes to move to the right, up, and
|
|
down should be given as <STRONG>cuf1</STRONG>, <STRONG>cuu1</STRONG>, and <STRONG>cud1</STRONG>. These local
|
|
- cursor motions should not alter the text they pass over,
|
|
- for example, you would not normally use "<STRONG>cuf1</STRONG>= " because
|
|
+ cursor motions should not alter the text they pass over,
|
|
+ for example, you would not normally use "<STRONG>cuf1</STRONG>= " because
|
|
the space would erase the character moved over.
|
|
|
|
- A very important point here is that the local cursor
|
|
- motions encoded in <EM>terminfo</EM> are undefined at the left and
|
|
- top edges of a CRT terminal. Programs should never
|
|
- attempt to backspace around the left edge, unless <STRONG>bw</STRONG> is
|
|
+ A very important point here is that the local cursor
|
|
+ motions encoded in <EM>terminfo</EM> are undefined at the left and
|
|
+ top edges of a CRT terminal. Programs should never
|
|
+ attempt to backspace around the left edge, unless <STRONG>bw</STRONG> is
|
|
given, and never attempt to go up locally off the top. In
|
|
- order to scroll text up, a program will go to the bottom
|
|
+ order to scroll text up, a program will go to the bottom
|
|
left corner of the screen and send the <STRONG>ind</STRONG> (index) string.
|
|
|
|
To scroll text down, a program goes to the top left corner
|
|
- of the screen and sends the <STRONG>ri</STRONG> (reverse index) string.
|
|
- The strings <STRONG>ind</STRONG> and <STRONG>ri</STRONG> are undefined when not on their
|
|
+ of the screen and sends the <STRONG>ri</STRONG> (reverse index) string.
|
|
+ The strings <STRONG>ind</STRONG> and <STRONG>ri</STRONG> are undefined when not on their
|
|
respective corners of the screen.
|
|
|
|
Parameterized versions of the scrolling sequences are <STRONG>indn</STRONG>
|
|
and <STRONG>rin</STRONG> which have the same semantics as <STRONG>ind</STRONG> and <STRONG>ri</STRONG> except
|
|
- that they take one parameter, and scroll that many lines.
|
|
- They are also undefined except at the appropriate edge of
|
|
+ that they take one parameter, and scroll that many lines.
|
|
+ They are also undefined except at the appropriate edge of
|
|
the screen.
|
|
|
|
- The <STRONG>am</STRONG> capability tells whether the cursor sticks at the
|
|
- right edge of the screen when text is output, but this
|
|
+ The <STRONG>am</STRONG> capability tells whether the cursor sticks at the
|
|
+ right edge of the screen when text is output, but this
|
|
does not necessarily apply to a <STRONG>cuf1</STRONG> from the last column.
|
|
- The only local motion which is defined from the left edge
|
|
- is if <STRONG>bw</STRONG> is given, then a <STRONG>cub1</STRONG> from the left edge will
|
|
- move to the right edge of the previous row. If <STRONG>bw</STRONG> is not
|
|
- given, the effect is undefined. This is useful for draw-
|
|
- ing a box around the edge of the screen, for example. If
|
|
- the terminal has switch selectable automatic margins, the
|
|
- <EM>terminfo</EM> file usually assumes that this is on; i.e., <STRONG>am</STRONG>.
|
|
- If the terminal has a command which moves to the first
|
|
- column of the next line, that command can be given as <STRONG>nel</STRONG>
|
|
- (newline). It does not matter if the command clears the
|
|
- remainder of the current line, so if the terminal has no
|
|
- <STRONG>cr</STRONG> and <STRONG>lf</STRONG> it may still be possible to craft a working <STRONG>nel</STRONG>
|
|
+ The only local motion which is defined from the left edge
|
|
+ is if <STRONG>bw</STRONG> is given, then a <STRONG>cub1</STRONG> from the left edge will
|
|
+ move to the right edge of the previous row. If <STRONG>bw</STRONG> is not
|
|
+ given, the effect is undefined. This is useful for draw-
|
|
+ ing a box around the edge of the screen, for example. If
|
|
+ the terminal has switch selectable automatic margins, the
|
|
+ <EM>terminfo</EM> file usually assumes that this is on; i.e., <STRONG>am</STRONG>.
|
|
+ If the terminal has a command which moves to the first
|
|
+ column of the next line, that command can be given as <STRONG>nel</STRONG>
|
|
+ (newline). It does not matter if the command clears the
|
|
+ remainder of the current line, so if the terminal has no
|
|
+ <STRONG>cr</STRONG> and <STRONG>lf</STRONG> it may still be possible to craft a working <STRONG>nel</STRONG>
|
|
out of one or both of them.
|
|
|
|
These capabilities suffice to describe hard-copy and
|
|
- "glass-tty" terminals. Thus the model 33 teletype is
|
|
+ "glass-tty" terminals. Thus the model 33 teletype is
|
|
described as
|
|
|
|
33|tty33|tty|model 33 teletype,
|
|
@@ -1323,21 +1330,21 @@
|
|
|
|
|
|
</PRE><H3><a name="h3-Parameterized-Strings">Parameterized Strings</a></H3><PRE>
|
|
- Cursor addressing and other strings requiring parameters
|
|
- in the terminal are described by a parameterized string
|
|
- capability, with <EM>printf</EM>-like escapes such as <EM>%x</EM> in it.
|
|
- For example, to address the cursor, the <STRONG>cup</STRONG> capability is
|
|
+ Cursor addressing and other strings requiring parameters
|
|
+ in the terminal are described by a parameterized string
|
|
+ capability, with <EM>printf</EM>-like escapes such as <EM>%x</EM> in it.
|
|
+ For example, to address the cursor, the <STRONG>cup</STRONG> capability is
|
|
given, using two parameters: the row and column to address
|
|
to. (Rows and columns are numbered from zero and refer to
|
|
the physical screen visible to the user, not to any unseen
|
|
- memory.) If the terminal has memory relative cursor
|
|
+ memory.) If the terminal has memory relative cursor
|
|
addressing, that can be indicated by <STRONG>mrcup</STRONG>.
|
|
|
|
- The parameter mechanism uses a stack and special <STRONG>%</STRONG> codes
|
|
- to manipulate it. Typically a sequence will push one of
|
|
- the parameters onto the stack and then print it in some
|
|
- format. Print (e.g., "%d") is a special case. Other
|
|
- operations, including "%t" pop their operand from the
|
|
+ The parameter mechanism uses a stack and special <STRONG>%</STRONG> codes
|
|
+ to manipulate it. Typically a sequence will push one of
|
|
+ the parameters onto the stack and then print it in some
|
|
+ format. Print (e.g., "%d") is a special case. Other
|
|
+ operations, including "%t" pop their operand from the
|
|
stack. It is noted that more complex operations are often
|
|
necessary, e.g., in the <STRONG>sgr</STRONG> string.
|
|
|
|
@@ -1346,19 +1353,19 @@
|
|
<STRONG>%%</STRONG> outputs "%"
|
|
|
|
<STRONG>%</STRONG><EM>[[</EM>:<EM>]flags][width[.precision]][</EM><STRONG>doxXs</STRONG><EM>]</EM>
|
|
- as in <STRONG>printf</STRONG>, flags are <EM>[-+#]</EM> and <EM>space</EM>. Use a ":"
|
|
- to allow the next character to be a "-" flag, avoid-
|
|
+ as in <STRONG>printf</STRONG>, flags are <EM>[-+#]</EM> and <EM>space</EM>. Use a ":"
|
|
+ to allow the next character to be a "-" flag, avoid-
|
|
ing interpreting "%-" as an operator.
|
|
|
|
- %c print pop() like %c in <STRONG>printf</STRONG>
|
|
+ %c print <EM>pop()</EM> like %c in <STRONG>printf</STRONG>
|
|
|
|
- <STRONG>%s</STRONG> print pop() like %s in <STRONG>printf</STRONG>
|
|
+ <STRONG>%s</STRONG> print <EM>pop()</EM> like %s in <STRONG>printf</STRONG>
|
|
|
|
<STRONG>%p</STRONG><EM>[1-9]</EM>
|
|
push <EM>i</EM>'th parameter
|
|
|
|
<STRONG>%P</STRONG><EM>[a-z]</EM>
|
|
- set dynamic variable <EM>[a-z]</EM> to pop()
|
|
+ set dynamic variable <EM>[a-z]</EM> to <EM>pop()</EM>
|
|
|
|
<STRONG>%g</STRONG><EM>[a-z]/</EM>
|
|
get dynamic variable <EM>[a-z]</EM> and push it
|
|
@@ -1369,11 +1376,11 @@
|
|
<STRONG>%g</STRONG><EM>[A-Z]</EM>
|
|
get static variable <EM>[a-z]</EM> and push it
|
|
|
|
- The terms "static" and "dynamic" are misleading.
|
|
- Historically, these are simply two different sets of
|
|
- variables, whose values are not reset between calls
|
|
- to <STRONG>tparm</STRONG>. However, that fact is not documented in
|
|
- other implementations. Relying on it will adversely
|
|
+ The terms "static" and "dynamic" are misleading.
|
|
+ Historically, these are simply two different sets of
|
|
+ variables, whose values are not reset between calls
|
|
+ to <STRONG>tparm</STRONG>. However, that fact is not documented in
|
|
+ other implementations. Relying on it will adversely
|
|
impact portability to other implementations.
|
|
|
|
<STRONG>%'</STRONG><EM>c</EM><STRONG>'</STRONG> char constant <EM>c</EM>
|
|
@@ -1384,7 +1391,7 @@
|
|
<STRONG>%l</STRONG> push strlen(pop)
|
|
|
|
<STRONG>%+</STRONG>, <STRONG>%-</STRONG>, <STRONG>%*</STRONG>, <STRONG>%/</STRONG>, <STRONG>%m</STRONG>
|
|
- arithmetic (%m is mod): <EM>push(pop()</EM> <EM>op</EM> <EM>pop())</EM>
|
|
+ arithmetic (%m is <EM>mod</EM>): <EM>push(pop()</EM> <EM>op</EM> <EM>pop())</EM>
|
|
|
|
<STRONG>%&</STRONG>, <STRONG>%|</STRONG>, <STRONG>%^</STRONG>
|
|
bit operations (AND, OR and exclusive-OR): <EM>push(pop()</EM>
|
|
@@ -1397,16 +1404,16 @@
|
|
logical AND and OR operations (for conditionals)
|
|
|
|
<STRONG>%!</STRONG>, <STRONG>%~</STRONG>
|
|
- unary operations (logical and bit complement):
|
|
- push(op pop())
|
|
+ unary operations (logical and bit complement):
|
|
+ <EM>push(op</EM> <EM>pop())</EM>
|
|
|
|
<STRONG>%i</STRONG> add 1 to first two parameters (for ANSI terminals)
|
|
|
|
<STRONG>%?</STRONG> <EM>expr</EM> <STRONG>%t</STRONG> <EM>thenpart</EM> <STRONG>%e</STRONG> <EM>elsepart</EM> <STRONG>%;</STRONG>
|
|
- This forms an if-then-else. The <STRONG>%e</STRONG> <EM>elsepart</EM> is
|
|
- optional. Usually the <STRONG>%?</STRONG> <EM>expr</EM> part pushes a value
|
|
- onto the stack, and <STRONG>%t</STRONG> pops it from the stack, test-
|
|
- ing if it is nonzero (true). If it is zero (false),
|
|
+ This forms an if-then-else. The <STRONG>%e</STRONG> <EM>elsepart</EM> is
|
|
+ optional. Usually the <STRONG>%?</STRONG> <EM>expr</EM> part pushes a value
|
|
+ onto the stack, and <STRONG>%t</STRONG> pops it from the stack, test-
|
|
+ ing if it is nonzero (true). If it is zero (false),
|
|
control passes to the <STRONG>%e</STRONG> (else) part.
|
|
|
|
It is possible to form else-if's a la Algol 68:
|
|
@@ -1415,221 +1422,221 @@
|
|
where ci are conditions, bi are bodies.
|
|
|
|
Use the <STRONG>-f</STRONG> option of <STRONG>tic</STRONG> or <STRONG>infocmp</STRONG> to see the struc-
|
|
- ture of if-then-else's. Some strings, e.g., <STRONG>sgr</STRONG> can
|
|
+ ture of if-then-else's. Some strings, e.g., <STRONG>sgr</STRONG> can
|
|
be very complicated when written on one line. The <STRONG>-f</STRONG>
|
|
- option splits the string into lines with the parts
|
|
+ option splits the string into lines with the parts
|
|
indented.
|
|
|
|
Binary operations are in postfix form with the operands in
|
|
- the usual order. That is, to get x-5 one would use
|
|
- "%gx%{5}%-". <STRONG>%P</STRONG> and <STRONG>%g</STRONG> variables are persistent across
|
|
+ the usual order. That is, to get x-5 one would use
|
|
+ "%gx%{5}%-". <STRONG>%P</STRONG> and <STRONG>%g</STRONG> variables are persistent across
|
|
escape-string evaluations.
|
|
|
|
Consider the HP2645, which, to get to row 3 and column 12,
|
|
- needs to be sent \E&a12c03Y padded for 6 milliseconds.
|
|
- Note that the order of the rows and columns is inverted
|
|
- here, and that the row and column are printed as two dig-
|
|
+ needs to be sent \E&a12c03Y padded for 6 milliseconds.
|
|
+ Note that the order of the rows and columns is inverted
|
|
+ here, and that the row and column are printed as two dig-
|
|
its. Thus its <STRONG>cup</STRONG> capability is "cup=6\E&%p2%2dc%p1%2dY".
|
|
|
|
The Microterm ACT-IV needs the current row and column sent
|
|
- preceded by a <STRONG>^T</STRONG>, with the row and column simply encoded
|
|
- in binary, "cup=^T%p1%c%p2%c". Terminals which use "%c"
|
|
- need to be able to backspace the cursor (<STRONG>cub1</STRONG>), and to
|
|
+ preceded by a <STRONG>^T</STRONG>, with the row and column simply encoded
|
|
+ in binary, "cup=^T%p1%c%p2%c". Terminals which use "%c"
|
|
+ need to be able to backspace the cursor (<STRONG>cub1</STRONG>), and to
|
|
move the cursor up one line on the screen (<STRONG>cuu1</STRONG>). This is
|
|
- necessary because it is not always safe to transmit <STRONG>\n</STRONG> <STRONG>^D</STRONG>
|
|
- and <STRONG>\r</STRONG>, as the system may change or discard them. (The
|
|
- library routines dealing with terminfo set tty modes so
|
|
+ necessary because it is not always safe to transmit <STRONG>\n</STRONG> <STRONG>^D</STRONG>
|
|
+ and <STRONG>\r</STRONG>, as the system may change or discard them. (The
|
|
+ library routines dealing with terminfo set tty modes so
|
|
that tabs are never expanded, so \t is safe to send. This
|
|
turns out to be essential for the Ann Arbor 4080.)
|
|
|
|
A final example is the LSI ADM-3a, which uses row and col-
|
|
umn offset by a blank character, thus "cup=\E=%p1%'
|
|
- '%+%c%p2%' '%+%c". After sending "\E=", this pushes the
|
|
- first parameter, pushes the ASCII value for a space (32),
|
|
- adds them (pushing the sum on the stack in place of the
|
|
- two previous values) and outputs that value as a charac-
|
|
- ter. Then the same is done for the second parameter.
|
|
+ '%+%c%p2%' '%+%c". After sending "\E=", this pushes the
|
|
+ first parameter, pushes the ASCII value for a space (32),
|
|
+ adds them (pushing the sum on the stack in place of the
|
|
+ two previous values) and outputs that value as a charac-
|
|
+ ter. Then the same is done for the second parameter.
|
|
More complex arithmetic is possible using the stack.
|
|
|
|
|
|
</PRE><H3><a name="h3-Cursor-Motions">Cursor Motions</a></H3><PRE>
|
|
If the terminal has a fast way to home the cursor (to very
|
|
- upper left corner of screen) then this can be given as
|
|
- <STRONG>home</STRONG>; similarly a fast way of getting to the lower left-
|
|
- hand corner can be given as <STRONG>ll</STRONG>; this may involve going up
|
|
- with <STRONG>cuu1</STRONG> from the home position, but a program should
|
|
- never do this itself (unless <STRONG>ll</STRONG> does) because it can make
|
|
- no assumption about the effect of moving up from the home
|
|
- position. Note that the home position is the same as
|
|
+ upper left corner of screen) then this can be given as
|
|
+ <STRONG>home</STRONG>; similarly a fast way of getting to the lower left-
|
|
+ hand corner can be given as <STRONG>ll</STRONG>; this may involve going up
|
|
+ with <STRONG>cuu1</STRONG> from the home position, but a program should
|
|
+ never do this itself (unless <STRONG>ll</STRONG> does) because it can make
|
|
+ no assumption about the effect of moving up from the home
|
|
+ position. Note that the home position is the same as
|
|
addressing to (0,0): to the top left corner of the screen,
|
|
- not of memory. (Thus, the \EH sequence on HP terminals
|
|
+ not of memory. (Thus, the \EH sequence on HP terminals
|
|
cannot be used for <STRONG>home</STRONG>.)
|
|
|
|
If the terminal has row or column absolute cursor address-
|
|
- ing, these can be given as single parameter capabilities
|
|
+ ing, these can be given as single parameter capabilities
|
|
<STRONG>hpa</STRONG> (horizontal position absolute) and <STRONG>vpa</STRONG> (vertical posi-
|
|
tion absolute). Sometimes these are shorter than the more
|
|
- general two parameter sequence (as with the hp2645) and
|
|
+ general two parameter sequence (as with the hp2645) and
|
|
can be used in preference to <STRONG>cup</STRONG>. If there are parameter-
|
|
- ized local motions (e.g., move <EM>n</EM> spaces to the right)
|
|
+ ized local motions (e.g., move <EM>n</EM> spaces to the right)
|
|
these can be given as <STRONG>cud</STRONG>, <STRONG>cub</STRONG>, <STRONG>cuf</STRONG>, and <STRONG>cuu</STRONG> with a single
|
|
- parameter indicating how many spaces to move. These are
|
|
- primarily useful if the terminal does not have <STRONG>cup</STRONG>, such
|
|
+ parameter indicating how many spaces to move. These are
|
|
+ primarily useful if the terminal does not have <STRONG>cup</STRONG>, such
|
|
as the TEKTRONIX 4025.
|
|
|
|
If the terminal needs to be in a special mode when running
|
|
a program that uses these capabilities, the codes to enter
|
|
- and exit this mode can be given as <STRONG>smcup</STRONG> and <STRONG>rmcup</STRONG>. This
|
|
- arises, for example, from terminals like the Concept with
|
|
- more than one page of memory. If the terminal has only
|
|
- memory relative cursor addressing and not screen relative
|
|
+ and exit this mode can be given as <STRONG>smcup</STRONG> and <STRONG>rmcup</STRONG>. This
|
|
+ arises, for example, from terminals like the Concept with
|
|
+ more than one page of memory. If the terminal has only
|
|
+ memory relative cursor addressing and not screen relative
|
|
cursor addressing, a one screen-sized window must be fixed
|
|
- into the terminal for cursor addressing to work properly.
|
|
+ into the terminal for cursor addressing to work properly.
|
|
This is also used for the TEKTRONIX 4025, where <STRONG>smcup</STRONG> sets
|
|
- the command character to be the one used by terminfo. If
|
|
- the <STRONG>smcup</STRONG> sequence will not restore the screen after an
|
|
+ the command character to be the one used by terminfo. If
|
|
+ the <STRONG>smcup</STRONG> sequence will not restore the screen after an
|
|
<STRONG>rmcup</STRONG> sequence is output (to the state prior to outputting
|
|
<STRONG>rmcup</STRONG>), specify <STRONG>nrrmc</STRONG>.
|
|
|
|
|
|
</PRE><H3><a name="h3-Area-Clears">Area Clears</a></H3><PRE>
|
|
If the terminal can clear from the current position to the
|
|
- end of the line, leaving the cursor where it is, this
|
|
+ end of the line, leaving the cursor where it is, this
|
|
should be given as <STRONG>el</STRONG>. If the terminal can clear from the
|
|
- beginning of the line to the current position inclusive,
|
|
- leaving the cursor where it is, this should be given as
|
|
- <STRONG>el1</STRONG>. If the terminal can clear from the current position
|
|
- to the end of the display, then this should be given as
|
|
- <STRONG>ed</STRONG>. <STRONG>Ed</STRONG> is only defined from the first column of a line.
|
|
- (Thus, it can be simulated by a request to delete a large
|
|
+ beginning of the line to the current position inclusive,
|
|
+ leaving the cursor where it is, this should be given as
|
|
+ <STRONG>el1</STRONG>. If the terminal can clear from the current position
|
|
+ to the end of the display, then this should be given as
|
|
+ <STRONG>ed</STRONG>. <STRONG>Ed</STRONG> is only defined from the first column of a line.
|
|
+ (Thus, it can be simulated by a request to delete a large
|
|
number of lines, if a true <STRONG>ed</STRONG> is not available.)
|
|
|
|
|
|
</PRE><H3><a name="h3-Insert_delete-line-and-vertical-motions">Insert/delete line and vertical motions</a></H3><PRE>
|
|
- If the terminal can open a new blank line before the line
|
|
- where the cursor is, this should be given as <STRONG>il1</STRONG>; this is
|
|
- done only from the first position of a line. The cursor
|
|
+ If the terminal can open a new blank line before the line
|
|
+ where the cursor is, this should be given as <STRONG>il1</STRONG>; this is
|
|
+ done only from the first position of a line. The cursor
|
|
must then appear on the newly blank line. If the terminal
|
|
- can delete the line which the cursor is on, then this
|
|
- should be given as <STRONG>dl1</STRONG>; this is done only from the first
|
|
- position on the line to be deleted. Versions of <STRONG>il1</STRONG> and
|
|
- <STRONG>dl1</STRONG> which take a single parameter and insert or delete
|
|
+ can delete the line which the cursor is on, then this
|
|
+ should be given as <STRONG>dl1</STRONG>; this is done only from the first
|
|
+ position on the line to be deleted. Versions of <STRONG>il1</STRONG> and
|
|
+ <STRONG>dl1</STRONG> which take a single parameter and insert or delete
|
|
that many lines can be given as <STRONG>il</STRONG> and <STRONG>dl</STRONG>.
|
|
|
|
- If the terminal has a settable scrolling region (like the
|
|
- vt100) the command to set this can be described with the
|
|
- <STRONG>csr</STRONG> capability, which takes two parameters: the top and
|
|
+ If the terminal has a settable scrolling region (like the
|
|
+ vt100) the command to set this can be described with the
|
|
+ <STRONG>csr</STRONG> capability, which takes two parameters: the top and
|
|
bottom lines of the scrolling region. The cursor position
|
|
is, alas, undefined after using this command.
|
|
|
|
- It is possible to get the effect of insert or delete line
|
|
+ It is possible to get the effect of insert or delete line
|
|
using <STRONG>csr</STRONG> on a properly chosen region; the <STRONG>sc</STRONG> and <STRONG>rc</STRONG> (save
|
|
- and restore cursor) commands may be useful for ensuring
|
|
- that your synthesized insert/delete string does not move
|
|
- the cursor. (Note that the <STRONG><A HREF="ncurses.3x.html">ncurses(3x)</A></STRONG> library does this
|
|
- synthesis automatically, so you need not compose
|
|
+ and restore cursor) commands may be useful for ensuring
|
|
+ that your synthesized insert/delete string does not move
|
|
+ the cursor. (Note that the <STRONG><A HREF="ncurses.3x.html">ncurses(3x)</A></STRONG> library does this
|
|
+ synthesis automatically, so you need not compose
|
|
insert/delete strings for an entry with <STRONG>csr</STRONG>).
|
|
|
|
Yet another way to construct insert and delete might be to
|
|
- use a combination of index with the memory-lock feature
|
|
- found on some terminals (like the HP-700/90 series, which
|
|
+ use a combination of index with the memory-lock feature
|
|
+ found on some terminals (like the HP-700/90 series, which
|
|
however also has insert/delete).
|
|
|
|
- Inserting lines at the top or bottom of the screen can
|
|
- also be done using <STRONG>ri</STRONG> or <STRONG>ind</STRONG> on many terminals without a
|
|
- true insert/delete line, and is often faster even on ter-
|
|
+ Inserting lines at the top or bottom of the screen can
|
|
+ also be done using <STRONG>ri</STRONG> or <STRONG>ind</STRONG> on many terminals without a
|
|
+ true insert/delete line, and is often faster even on ter-
|
|
minals with those features.
|
|
|
|
- The boolean <STRONG>non_dest_scroll_region</STRONG> should be set if each
|
|
- scrolling window is effectively a view port on a screen-
|
|
- sized canvas. To test for this capability, create a
|
|
- scrolling region in the middle of the screen, write some-
|
|
- thing to the bottom line, move the cursor to the top of
|
|
+ The boolean <STRONG>non_dest_scroll_region</STRONG> should be set if each
|
|
+ scrolling window is effectively a view port on a screen-
|
|
+ sized canvas. To test for this capability, create a
|
|
+ scrolling region in the middle of the screen, write some-
|
|
+ thing to the bottom line, move the cursor to the top of
|
|
the region, and do <STRONG>ri</STRONG> followed by <STRONG>dl1</STRONG> or <STRONG>ind</STRONG>. If the data
|
|
- scrolled off the bottom of the region by the <STRONG>ri</STRONG> re-
|
|
- appears, then scrolling is non-destructive. System V and
|
|
- XSI Curses expect that <STRONG>ind</STRONG>, <STRONG>ri</STRONG>, <STRONG>indn</STRONG>, and <STRONG>rin</STRONG> will simu-
|
|
- late destructive scrolling; their documentation cautions
|
|
- you not to define <STRONG>csr</STRONG> unless this is true. This <STRONG>curses</STRONG>
|
|
+ scrolled off the bottom of the region by the <STRONG>ri</STRONG> re-
|
|
+ appears, then scrolling is non-destructive. System V and
|
|
+ XSI Curses expect that <STRONG>ind</STRONG>, <STRONG>ri</STRONG>, <STRONG>indn</STRONG>, and <STRONG>rin</STRONG> will simu-
|
|
+ late destructive scrolling; their documentation cautions
|
|
+ you not to define <STRONG>csr</STRONG> unless this is true. This <STRONG>curses</STRONG>
|
|
implementation is more liberal and will do explicit erases
|
|
after scrolling if <STRONG>ndstr</STRONG> is defined.
|
|
|
|
If the terminal has the ability to define a window as part
|
|
- of memory, which all commands affect, it should be given
|
|
+ of memory, which all commands affect, it should be given
|
|
as the parameterized string <STRONG>wind</STRONG>. The four parameters are
|
|
- the starting and ending lines in memory and the starting
|
|
+ the starting and ending lines in memory and the starting
|
|
and ending columns in memory, in that order.
|
|
|
|
- If the terminal can retain display memory above, then the
|
|
- <STRONG>da</STRONG> capability should be given; if display memory can be
|
|
- retained below, then <STRONG>db</STRONG> should be given. These indicate
|
|
- that deleting a line or scrolling may bring non-blank
|
|
- lines up from below or that scrolling back with <STRONG>ri</STRONG> may
|
|
+ If the terminal can retain display memory above, then the
|
|
+ <STRONG>da</STRONG> capability should be given; if display memory can be
|
|
+ retained below, then <STRONG>db</STRONG> should be given. These indicate
|
|
+ that deleting a line or scrolling may bring non-blank
|
|
+ lines up from below or that scrolling back with <STRONG>ri</STRONG> may
|
|
bring down non-blank lines.
|
|
|
|
|
|
</PRE><H3><a name="h3-Insert_Delete-Character">Insert/Delete Character</a></H3><PRE>
|
|
- There are two basic kinds of intelligent terminals with
|
|
- respect to insert/delete character which can be described
|
|
- using <EM>terminfo.</EM> The most common insert/delete character
|
|
- operations affect only the characters on the current line
|
|
- and shift characters off the end of the line rigidly.
|
|
- Other terminals, such as the Concept 100 and the Perkin
|
|
- Elmer Owl, make a distinction between typed and untyped
|
|
- blanks on the screen, shifting upon an insert or delete
|
|
- only to an untyped blank on the screen which is either
|
|
+ There are two basic kinds of intelligent terminals with
|
|
+ respect to insert/delete character which can be described
|
|
+ using <EM>terminfo.</EM> The most common insert/delete character
|
|
+ operations affect only the characters on the current line
|
|
+ and shift characters off the end of the line rigidly.
|
|
+ Other terminals, such as the Concept 100 and the Perkin
|
|
+ Elmer Owl, make a distinction between typed and untyped
|
|
+ blanks on the screen, shifting upon an insert or delete
|
|
+ only to an untyped blank on the screen which is either
|
|
eliminated, or expanded to two untyped blanks.
|
|
|
|
- You can determine the kind of terminal you have by clear-
|
|
- ing the screen and then typing text separated by cursor
|
|
- motions. Type "abc def" using local cursor motions
|
|
- (not spaces) between the "abc" and the "def". Then posi-
|
|
- tion the cursor before the "abc" and put the terminal in
|
|
- insert mode. If typing characters causes the rest of the
|
|
- line to shift rigidly and characters to fall off the end,
|
|
+ You can determine the kind of terminal you have by clear-
|
|
+ ing the screen and then typing text separated by cursor
|
|
+ motions. Type "abc def" using local cursor motions
|
|
+ (not spaces) between the "abc" and the "def". Then posi-
|
|
+ tion the cursor before the "abc" and put the terminal in
|
|
+ insert mode. If typing characters causes the rest of the
|
|
+ line to shift rigidly and characters to fall off the end,
|
|
then your terminal does not distinguish between blanks and
|
|
- untyped positions. If the "abc" shifts over to the "def"
|
|
- which then move together around the end of the current
|
|
- line and onto the next as you insert, you have the second
|
|
+ untyped positions. If the "abc" shifts over to the "def"
|
|
+ which then move together around the end of the current
|
|
+ line and onto the next as you insert, you have the second
|
|
type of terminal, and should give the capability <STRONG>in</STRONG>, which
|
|
stands for "insert null".
|
|
|
|
- While these are two logically separate attributes (one
|
|
- line versus multi-line insert mode, and special treatment
|
|
- of untyped spaces) we have seen no terminals whose insert
|
|
+ While these are two logically separate attributes (one
|
|
+ line versus multi-line insert mode, and special treatment
|
|
+ of untyped spaces) we have seen no terminals whose insert
|
|
mode cannot be described with the single attribute.
|
|
|
|
- Terminfo can describe both terminals which have an insert
|
|
+ Terminfo can describe both terminals which have an insert
|
|
mode, and terminals which send a simple sequence to open a
|
|
- blank position on the current line. Give as <STRONG>smir</STRONG> the
|
|
- sequence to get into insert mode. Give as <STRONG>rmir</STRONG> the
|
|
- sequence to leave insert mode. Now give as <STRONG>ich1</STRONG> any
|
|
+ blank position on the current line. Give as <STRONG>smir</STRONG> the
|
|
+ sequence to get into insert mode. Give as <STRONG>rmir</STRONG> the
|
|
+ sequence to leave insert mode. Now give as <STRONG>ich1</STRONG> any
|
|
sequence needed to be sent just before sending the charac-
|
|
- ter to be inserted. Most terminals with a true insert
|
|
- mode will not give <STRONG>ich1</STRONG>; terminals which send a sequence
|
|
+ ter to be inserted. Most terminals with a true insert
|
|
+ mode will not give <STRONG>ich1</STRONG>; terminals which send a sequence
|
|
to open a screen position should give it here.
|
|
|
|
- If your terminal has both, insert mode is usually prefer-
|
|
- able to <STRONG>ich1</STRONG>. Technically, you should not give both
|
|
- unless the terminal actually requires both to be used in
|
|
- combination. Accordingly, some non-curses applications
|
|
- get confused if both are present; the symptom is doubled
|
|
+ If your terminal has both, insert mode is usually prefer-
|
|
+ able to <STRONG>ich1</STRONG>. Technically, you should not give both
|
|
+ unless the terminal actually requires both to be used in
|
|
+ combination. Accordingly, some non-curses applications
|
|
+ get confused if both are present; the symptom is doubled
|
|
characters in an update using insert. This requirement is
|
|
now rare; most <STRONG>ich</STRONG> sequences do not require previous smir,
|
|
and most smir insert modes do not require <STRONG>ich1</STRONG> before each
|
|
- character. Therefore, the new <STRONG>curses</STRONG> actually assumes
|
|
- this is the case and uses either <STRONG>rmir</STRONG>/<STRONG>smir</STRONG> or <STRONG>ich</STRONG>/<STRONG>ich1</STRONG> as
|
|
+ character. Therefore, the new <STRONG>curses</STRONG> actually assumes
|
|
+ this is the case and uses either <STRONG>rmir</STRONG>/<STRONG>smir</STRONG> or <STRONG>ich</STRONG>/<STRONG>ich1</STRONG> as
|
|
appropriate (but not both). If you have to write an entry
|
|
- to be used under new curses for a terminal old enough to
|
|
+ to be used under new curses for a terminal old enough to
|
|
need both, include the <STRONG>rmir</STRONG>/<STRONG>smir</STRONG> sequences in <STRONG>ich1</STRONG>.
|
|
|
|
If post insert padding is needed, give this as a number of
|
|
- milliseconds in <STRONG>ip</STRONG> (a string option). Any other sequence
|
|
- which may need to be sent after an insert of a single
|
|
+ milliseconds in <STRONG>ip</STRONG> (a string option). Any other sequence
|
|
+ which may need to be sent after an insert of a single
|
|
character may also be given in <STRONG>ip</STRONG>. If your terminal needs
|
|
both to be placed into an "insert mode" and a special code
|
|
- to precede each inserted character, then both <STRONG>smir</STRONG>/<STRONG>rmir</STRONG>
|
|
- and <STRONG>ich1</STRONG> can be given, and both will be used. The <STRONG>ich</STRONG>
|
|
+ to precede each inserted character, then both <STRONG>smir</STRONG>/<STRONG>rmir</STRONG>
|
|
+ and <STRONG>ich1</STRONG> can be given, and both will be used. The <STRONG>ich</STRONG>
|
|
capability, with one parameter, <EM>n</EM>, will repeat the effects
|
|
of <STRONG>ich1</STRONG> <EM>n</EM> times.
|
|
|
|
@@ -1637,62 +1644,62 @@
|
|
in insert mode, give this as a number of milliseconds pad-
|
|
ding in <STRONG>rmp</STRONG>.
|
|
|
|
- It is occasionally necessary to move around while in
|
|
- insert mode to delete characters on the same line (e.g.,
|
|
- if there is a tab after the insertion position). If your
|
|
- terminal allows motion while in insert mode you can give
|
|
- the capability <STRONG>mir</STRONG> to speed up inserting in this case.
|
|
- Omitting <STRONG>mir</STRONG> will affect only speed. Some terminals
|
|
+ It is occasionally necessary to move around while in
|
|
+ insert mode to delete characters on the same line (e.g.,
|
|
+ if there is a tab after the insertion position). If your
|
|
+ terminal allows motion while in insert mode you can give
|
|
+ the capability <STRONG>mir</STRONG> to speed up inserting in this case.
|
|
+ Omitting <STRONG>mir</STRONG> will affect only speed. Some terminals
|
|
(notably Datamedia's) must not have <STRONG>mir</STRONG> because of the way
|
|
their insert mode works.
|
|
|
|
- Finally, you can specify <STRONG>dch1</STRONG> to delete a single charac-
|
|
- ter, <STRONG>dch</STRONG> with one parameter, <EM>n</EM>, to delete <EM>n</EM> <EM>characters,</EM>
|
|
- and delete mode by giving <STRONG>smdc</STRONG> and <STRONG>rmdc</STRONG> to enter and exit
|
|
- delete mode (any mode the terminal needs to be placed in
|
|
+ Finally, you can specify <STRONG>dch1</STRONG> to delete a single charac-
|
|
+ ter, <STRONG>dch</STRONG> with one parameter, <EM>n</EM>, to delete <EM>n</EM> <EM>characters,</EM>
|
|
+ and delete mode by giving <STRONG>smdc</STRONG> and <STRONG>rmdc</STRONG> to enter and exit
|
|
+ delete mode (any mode the terminal needs to be placed in
|
|
for <STRONG>dch1</STRONG> to work).
|
|
|
|
- A command to erase <EM>n</EM> characters (equivalent to outputting
|
|
- <EM>n</EM> blanks without moving the cursor) can be given as <STRONG>ech</STRONG>
|
|
+ A command to erase <EM>n</EM> characters (equivalent to outputting
|
|
+ <EM>n</EM> blanks without moving the cursor) can be given as <STRONG>ech</STRONG>
|
|
with one parameter.
|
|
|
|
|
|
</PRE><H3><a name="h3-Highlighting_-Underlining_-and-Visible-Bells">Highlighting, Underlining, and Visible Bells</a></H3><PRE>
|
|
If your terminal has one or more kinds of display
|
|
- attributes, these can be represented in a number of dif-
|
|
+ attributes, these can be represented in a number of dif-
|
|
ferent ways. You should choose one display form as <EM>stand-</EM>
|
|
<EM>out</EM> <EM>mode</EM>, representing a good, high contrast, easy-on-the-
|
|
- eyes, format for highlighting error messages and other
|
|
- attention getters. (If you have a choice, reverse video
|
|
- plus half-bright is good, or reverse video alone.) The
|
|
- sequences to enter and exit standout mode are given as
|
|
- <STRONG>smso</STRONG> and <STRONG>rmso</STRONG>, respectively. If the code to change into
|
|
- or out of standout mode leaves one or even two blank spa-
|
|
- ces on the screen, as the TVI 912 and Teleray 1061 do,
|
|
+ eyes, format for highlighting error messages and other
|
|
+ attention getters. (If you have a choice, reverse video
|
|
+ plus half-bright is good, or reverse video alone.) The
|
|
+ sequences to enter and exit standout mode are given as
|
|
+ <STRONG>smso</STRONG> and <STRONG>rmso</STRONG>, respectively. If the code to change into
|
|
+ or out of standout mode leaves one or even two blank spa-
|
|
+ ces on the screen, as the TVI 912 and Teleray 1061 do,
|
|
then <STRONG>xmc</STRONG> should be given to tell how many spaces are left.
|
|
|
|
- Codes to begin underlining and end underlining can be
|
|
- given as <STRONG>smul</STRONG> and <STRONG>rmul</STRONG> respectively. If the terminal has
|
|
- a code to underline the current character and move the
|
|
+ Codes to begin underlining and end underlining can be
|
|
+ given as <STRONG>smul</STRONG> and <STRONG>rmul</STRONG> respectively. If the terminal has
|
|
+ a code to underline the current character and move the
|
|
cursor one space to the right, such as the Microterm Mime,
|
|
this can be given as <STRONG>uc</STRONG>.
|
|
|
|
- Other capabilities to enter various highlighting modes
|
|
- include <STRONG>blink</STRONG> (blinking) <STRONG>bold</STRONG> (bold or extra bright) <STRONG>dim</STRONG>
|
|
- (dim or half-bright) <STRONG>invis</STRONG> (blanking or invisible text)
|
|
- <STRONG>prot</STRONG> (protected) <STRONG>rev</STRONG> (reverse video) <STRONG>sgr0</STRONG> (turn off <EM>all</EM>
|
|
- attribute modes) <STRONG>smacs</STRONG> (enter alternate character set
|
|
- mode) and <STRONG>rmacs</STRONG> (exit alternate character set mode).
|
|
- Turning on any of these modes singly may or may not turn
|
|
+ Other capabilities to enter various highlighting modes
|
|
+ include <STRONG>blink</STRONG> (blinking) <STRONG>bold</STRONG> (bold or extra bright) <STRONG>dim</STRONG>
|
|
+ (dim or half-bright) <STRONG>invis</STRONG> (blanking or invisible text)
|
|
+ <STRONG>prot</STRONG> (protected) <STRONG>rev</STRONG> (reverse video) <STRONG>sgr0</STRONG> (turn off <EM>all</EM>
|
|
+ attribute modes) <STRONG>smacs</STRONG> (enter alternate character set
|
|
+ mode) and <STRONG>rmacs</STRONG> (exit alternate character set mode).
|
|
+ Turning on any of these modes singly may or may not turn
|
|
off other modes.
|
|
|
|
- If there is a sequence to set arbitrary combinations of
|
|
- modes, this should be given as <STRONG>sgr</STRONG> (set attributes), tak-
|
|
- ing 9 parameters. Each parameter is either 0 or nonzero,
|
|
+ If there is a sequence to set arbitrary combinations of
|
|
+ modes, this should be given as <STRONG>sgr</STRONG> (set attributes), tak-
|
|
+ ing 9 parameters. Each parameter is either 0 or nonzero,
|
|
as the corresponding attribute is on or off. The 9 param-
|
|
- eters are, in order: standout, underline, reverse, blink,
|
|
- dim, bold, blank, protect, alternate character set. Not
|
|
- all modes need be supported by <STRONG>sgr</STRONG>, only those for which
|
|
+ eters are, in order: standout, underline, reverse, blink,
|
|
+ dim, bold, blank, protect, alternate character set. Not
|
|
+ all modes need be supported by <STRONG>sgr</STRONG>, only those for which
|
|
corresponding separate attribute commands exist.
|
|
|
|
For example, the DEC vt220 supports most of the modes:
|
|
@@ -1710,22 +1717,22 @@
|
|
p8 protect not used
|
|
p9 altcharset ^O (off) ^N (on)
|
|
|
|
- We begin each escape sequence by turning off any existing
|
|
- modes, since there is no quick way to determine whether
|
|
+ We begin each escape sequence by turning off any existing
|
|
+ modes, since there is no quick way to determine whether
|
|
they are active. Standout is set up to be the combination
|
|
- of reverse and bold. The vt220 terminal has a protect
|
|
- mode, though it is not commonly used in sgr because it
|
|
- protects characters on the screen from the host's era-
|
|
- sures. The altcharset mode also is different in that it
|
|
- is either ^O or ^N, depending on whether it is off or on.
|
|
- If all modes are turned on, the resulting sequence is
|
|
+ of reverse and bold. The vt220 terminal has a protect
|
|
+ mode, though it is not commonly used in sgr because it
|
|
+ protects characters on the screen from the host's era-
|
|
+ sures. The altcharset mode also is different in that it
|
|
+ is either ^O or ^N, depending on whether it is off or on.
|
|
+ If all modes are turned on, the resulting sequence is
|
|
\E[0;1;4;5;7;8m^N.
|
|
|
|
- Some sequences are common to different modes. For exam-
|
|
- ple, ;7 is output when either p1 or p3 is true, that is,
|
|
+ Some sequences are common to different modes. For exam-
|
|
+ ple, ;7 is output when either p1 or p3 is true, that is,
|
|
if either standout or reverse modes are turned on.
|
|
|
|
- Writing out the above sequences, along with their depen-
|
|
+ Writing out the above sequences, along with their depen-
|
|
dencies yields
|
|
|
|
<STRONG>sequence</STRONG> <STRONG>when</STRONG> <STRONG>to</STRONG> <STRONG>output</STRONG> <STRONG>terminfo</STRONG> <STRONG>translation</STRONG>
|
|
@@ -1744,62 +1751,62 @@
|
|
sgr=\E[0%?%p1%p6%|%t;1%;%?%p2%t;4%;%?%p4%t;5%;
|
|
%?%p1%p3%|%t;7%;%?%p7%t;8%;m%?%p9%t\016%e\017%;,
|
|
|
|
- Remember that if you specify sgr, you must also specify
|
|
- sgr0. Also, some implementations rely on sgr being given
|
|
- if sgr0 is, Not all terminfo entries necessarily have an
|
|
- sgr string, however. Many terminfo entries are derived
|
|
- from termcap entries which have no sgr string. The only
|
|
- drawback to adding an sgr string is that termcap also
|
|
- assumes that sgr0 does not exit alternate character set
|
|
+ Remember that if you specify sgr, you must also specify
|
|
+ sgr0. Also, some implementations rely on sgr being given
|
|
+ if sgr0 is, Not all terminfo entries necessarily have an
|
|
+ sgr string, however. Many terminfo entries are derived
|
|
+ from termcap entries which have no sgr string. The only
|
|
+ drawback to adding an sgr string is that termcap also
|
|
+ assumes that sgr0 does not exit alternate character set
|
|
mode.
|
|
|
|
- Terminals with the "magic cookie" glitch (<STRONG>xmc</STRONG>) deposit
|
|
+ Terminals with the "magic cookie" glitch (<STRONG>xmc</STRONG>) deposit
|
|
special "cookies" when they receive mode-setting
|
|
- sequences, which affect the display algorithm rather than
|
|
- having extra bits for each character. Some terminals,
|
|
- such as the HP 2621, automatically leave standout mode
|
|
- when they move to a new line or the cursor is addressed.
|
|
- Programs using standout mode should exit standout mode
|
|
- before moving the cursor or sending a newline, unless the
|
|
- <STRONG>msgr</STRONG> capability, asserting that it is safe to move in
|
|
+ sequences, which affect the display algorithm rather than
|
|
+ having extra bits for each character. Some terminals,
|
|
+ such as the HP 2621, automatically leave standout mode
|
|
+ when they move to a new line or the cursor is addressed.
|
|
+ Programs using standout mode should exit standout mode
|
|
+ before moving the cursor or sending a newline, unless the
|
|
+ <STRONG>msgr</STRONG> capability, asserting that it is safe to move in
|
|
standout mode, is present.
|
|
|
|
- If the terminal has a way of flashing the screen to indi-
|
|
- cate an error quietly (a bell replacement) then this can
|
|
+ If the terminal has a way of flashing the screen to indi-
|
|
+ cate an error quietly (a bell replacement) then this can
|
|
be given as <STRONG>flash</STRONG>; it must not move the cursor.
|
|
|
|
- If the cursor needs to be made more visible than normal
|
|
+ If the cursor needs to be made more visible than normal
|
|
when it is not on the bottom line (to make, for example, a
|
|
- non-blinking underline into an easier to find block or
|
|
+ non-blinking underline into an easier to find block or
|
|
blinking underline) give this sequence as <STRONG>cvvis</STRONG>. If there
|
|
- is a way to make the cursor completely invisible, give
|
|
+ is a way to make the cursor completely invisible, give
|
|
that as <STRONG>civis</STRONG>. The capability <STRONG>cnorm</STRONG> should be given which
|
|
undoes the effects of both of these modes.
|
|
|
|
If your terminal correctly generates underlined characters
|
|
- (with no special codes needed) even though it does not
|
|
- overstrike, then you should give the capability <STRONG>ul</STRONG>. If a
|
|
- character overstriking another leaves both characters on
|
|
+ (with no special codes needed) even though it does not
|
|
+ overstrike, then you should give the capability <STRONG>ul</STRONG>. If a
|
|
+ character overstriking another leaves both characters on
|
|
the screen, specify the capability <STRONG>os</STRONG>. If overstrikes are
|
|
- erasable with a blank, then this should be indicated by
|
|
+ erasable with a blank, then this should be indicated by
|
|
giving <STRONG>eo</STRONG>.
|
|
|
|
|
|
</PRE><H3><a name="h3-Keypad-and-Function-Keys">Keypad and Function Keys</a></H3><PRE>
|
|
If the terminal has a keypad that transmits codes when the
|
|
- keys are pressed, this information can be given. Note
|
|
+ keys are pressed, this information can be given. Note
|
|
that it is not possible to handle terminals where the key-
|
|
pad only works in local (this applies, for example, to the
|
|
- unshifted HP 2621 keys). If the keypad can be set to
|
|
- transmit or not transmit, give these codes as <STRONG>smkx</STRONG> and
|
|
+ unshifted HP 2621 keys). If the keypad can be set to
|
|
+ transmit or not transmit, give these codes as <STRONG>smkx</STRONG> and
|
|
<STRONG>rmkx</STRONG>. Otherwise the keypad is assumed to always transmit.
|
|
|
|
- The codes sent by the left arrow, right arrow, up arrow,
|
|
- down arrow, and home keys can be given as <STRONG>kcub1,</STRONG> <STRONG>kcuf1,</STRONG>
|
|
- <STRONG>kcuu1,</STRONG> <STRONG>kcud1,</STRONG> and <STRONG>khome</STRONG> respectively. If there are func-
|
|
- tion keys such as f0, f1, ..., f10, the codes they send
|
|
- can be given as <STRONG>kf0,</STRONG> <STRONG>kf1,</STRONG> <STRONG>...,</STRONG> <STRONG>kf10</STRONG>. If these keys have
|
|
- labels other than the default f0 through f10, the labels
|
|
+ The codes sent by the left arrow, right arrow, up arrow,
|
|
+ down arrow, and home keys can be given as <STRONG>kcub1,</STRONG> <STRONG>kcuf1,</STRONG>
|
|
+ <STRONG>kcuu1,</STRONG> <STRONG>kcud1,</STRONG> and <STRONG>khome</STRONG> respectively. If there are func-
|
|
+ tion keys such as f0, f1, ..., f10, the codes they send
|
|
+ can be given as <STRONG>kf0,</STRONG> <STRONG>kf1,</STRONG> <STRONG>...,</STRONG> <STRONG>kf10</STRONG>. If these keys have
|
|
+ labels other than the default f0 through f10, the labels
|
|
can be given as <STRONG>lf0,</STRONG> <STRONG>lf1,</STRONG> <STRONG>...,</STRONG> <STRONG>lf10</STRONG>.
|
|
|
|
The codes transmitted by certain other special keys can be
|
|
@@ -1839,60 +1846,60 @@
|
|
|
|
<STRONG>o</STRONG> <STRONG>khts</STRONG> (set a tab stop in this column).
|
|
|
|
- In addition, if the keypad has a 3 by 3 array of keys
|
|
- including the four arrow keys, the other five keys can be
|
|
+ In addition, if the keypad has a 3 by 3 array of keys
|
|
+ including the four arrow keys, the other five keys can be
|
|
given as <STRONG>ka1</STRONG>, <STRONG>ka3</STRONG>, <STRONG>kb2</STRONG>, <STRONG>kc1</STRONG>, and <STRONG>kc3</STRONG>. These keys are use-
|
|
- ful when the effects of a 3 by 3 directional pad are
|
|
+ ful when the effects of a 3 by 3 directional pad are
|
|
needed.
|
|
|
|
- Strings to program function keys can be given as <STRONG>pfkey</STRONG>,
|
|
- <STRONG>pfloc</STRONG>, and <STRONG>pfx</STRONG>. A string to program screen labels should
|
|
- be specified as <STRONG>pln</STRONG>. Each of these strings takes two
|
|
- parameters: the function key number to program (from 0 to
|
|
- 10) and the string to program it with. Function key num-
|
|
- bers out of this range may program undefined keys in a
|
|
- terminal dependent manner. The difference between the
|
|
- capabilities is that <STRONG>pfkey</STRONG> causes pressing the given key
|
|
- to be the same as the user typing the given string; <STRONG>pfloc</STRONG>
|
|
+ Strings to program function keys can be given as <STRONG>pfkey</STRONG>,
|
|
+ <STRONG>pfloc</STRONG>, and <STRONG>pfx</STRONG>. A string to program screen labels should
|
|
+ be specified as <STRONG>pln</STRONG>. Each of these strings takes two
|
|
+ parameters: the function key number to program (from 0 to
|
|
+ 10) and the string to program it with. Function key num-
|
|
+ bers out of this range may program undefined keys in a
|
|
+ terminal dependent manner. The difference between the
|
|
+ capabilities is that <STRONG>pfkey</STRONG> causes pressing the given key
|
|
+ to be the same as the user typing the given string; <STRONG>pfloc</STRONG>
|
|
causes the string to be executed by the terminal in local;
|
|
- and <STRONG>pfx</STRONG> causes the string to be transmitted to the com-
|
|
+ and <STRONG>pfx</STRONG> causes the string to be transmitted to the com-
|
|
puter.
|
|
|
|
The capabilities <STRONG>nlab</STRONG>, <STRONG>lw</STRONG> and <STRONG>lh</STRONG> define the number of pro-
|
|
- grammable screen labels and their width and height. If
|
|
- there are commands to turn the labels on and off, give
|
|
- them in <STRONG>smln</STRONG> and <STRONG>rmln</STRONG>. <STRONG>smln</STRONG> is normally output after one
|
|
+ grammable screen labels and their width and height. If
|
|
+ there are commands to turn the labels on and off, give
|
|
+ them in <STRONG>smln</STRONG> and <STRONG>rmln</STRONG>. <STRONG>smln</STRONG> is normally output after one
|
|
or more pln sequences to make sure that the change becomes
|
|
visible.
|
|
|
|
|
|
</PRE><H3><a name="h3-Tabs-and-Initialization">Tabs and Initialization</a></H3><PRE>
|
|
- If the terminal has hardware tabs, the command to advance
|
|
- to the next tab stop can be given as <STRONG>ht</STRONG> (usually control
|
|
+ If the terminal has hardware tabs, the command to advance
|
|
+ to the next tab stop can be given as <STRONG>ht</STRONG> (usually control
|
|
I). A "back-tab" command which moves leftward to the pre-
|
|
- ceding tab stop can be given as <STRONG>cbt</STRONG>. By convention, if
|
|
- the teletype modes indicate that tabs are being expanded
|
|
- by the computer rather than being sent to the terminal,
|
|
- programs should not use <STRONG>ht</STRONG> or <STRONG>cbt</STRONG> even if they are
|
|
- present, since the user may not have the tab stops prop-
|
|
- erly set. If the terminal has hardware tabs which are
|
|
- initially set every <EM>n</EM> spaces when the terminal is powered
|
|
- up, the numeric parameter <STRONG>it</STRONG> is given, showing the number
|
|
- of spaces the tabs are set to. This is normally used by
|
|
- the <EM>tset</EM> command to determine whether to set the mode for
|
|
- hardware tab expansion, and whether to set the tab stops.
|
|
- If the terminal has tab stops that can be saved in non-
|
|
- volatile memory, the terminfo description can assume that
|
|
+ ceding tab stop can be given as <STRONG>cbt</STRONG>. By convention, if
|
|
+ the teletype modes indicate that tabs are being expanded
|
|
+ by the computer rather than being sent to the terminal,
|
|
+ programs should not use <STRONG>ht</STRONG> or <STRONG>cbt</STRONG> even if they are
|
|
+ present, since the user may not have the tab stops prop-
|
|
+ erly set. If the terminal has hardware tabs which are
|
|
+ initially set every <EM>n</EM> spaces when the terminal is powered
|
|
+ up, the numeric parameter <STRONG>it</STRONG> is given, showing the number
|
|
+ of spaces the tabs are set to. This is normally used by
|
|
+ the <EM>tset</EM> command to determine whether to set the mode for
|
|
+ hardware tab expansion, and whether to set the tab stops.
|
|
+ If the terminal has tab stops that can be saved in non-
|
|
+ volatile memory, the terminfo description can assume that
|
|
they are properly set.
|
|
|
|
- Other capabilities include <STRONG>is1</STRONG>, <STRONG>is2</STRONG>, and <STRONG>is3</STRONG>, initializa-
|
|
- tion strings for the terminal, <STRONG>iprog</STRONG>, the path name of a
|
|
- program to be run to initialize the terminal, and <STRONG>if</STRONG>, the
|
|
- name of a file containing long initialization strings.
|
|
- These strings are expected to set the terminal into modes
|
|
- consistent with the rest of the terminfo description.
|
|
+ Other capabilities include <STRONG>is1</STRONG>, <STRONG>is2</STRONG>, and <STRONG>is3</STRONG>, initializa-
|
|
+ tion strings for the terminal, <STRONG>iprog</STRONG>, the path name of a
|
|
+ program to be run to initialize the terminal, and <STRONG>if</STRONG>, the
|
|
+ name of a file containing long initialization strings.
|
|
+ These strings are expected to set the terminal into modes
|
|
+ consistent with the rest of the terminfo description.
|
|
They are normally sent to the terminal, by the <EM>init</EM> option
|
|
- of the <EM>tput</EM> program, each time the user logs in. They
|
|
+ of the <EM>tput</EM> program, each time the user logs in. They
|
|
will be printed in the following order:
|
|
|
|
run the program
|
|
@@ -1912,107 +1919,107 @@
|
|
and finally
|
|
output <STRONG>is3</STRONG>.
|
|
|
|
- Most initialization is done with <STRONG>is2</STRONG>. Special terminal
|
|
+ Most initialization is done with <STRONG>is2</STRONG>. Special terminal
|
|
modes can be set up without duplicating strings by putting
|
|
- the common sequences in <STRONG>is2</STRONG> and special cases in <STRONG>is1</STRONG> and
|
|
+ the common sequences in <STRONG>is2</STRONG> and special cases in <STRONG>is1</STRONG> and
|
|
<STRONG>is3</STRONG>.
|
|
|
|
A set of sequences that does a harder reset from a totally
|
|
unknown state can be given as <STRONG>rs1</STRONG>, <STRONG>rs2</STRONG>, <STRONG>rf</STRONG> and <STRONG>rs3</STRONG>, analo-
|
|
- gous to <STRONG>is1</STRONG> <STRONG>,</STRONG> <STRONG>is2</STRONG> <STRONG>,</STRONG> <STRONG>if</STRONG> and <STRONG>is3</STRONG> respectively. These
|
|
- strings are output by the <EM>reset</EM> program, which is used
|
|
- when the terminal gets into a wedged state. Commands are
|
|
- normally placed in <STRONG>rs1</STRONG>, <STRONG>rs2</STRONG> <STRONG>rs3</STRONG> and <STRONG>rf</STRONG> only if they pro-
|
|
- duce annoying effects on the screen and are not necessary
|
|
- when logging in. For example, the command to set the
|
|
- vt100 into 80-column mode would normally be part of <STRONG>is2</STRONG>,
|
|
- but it causes an annoying glitch of the screen and is not
|
|
- normally needed since the terminal is usually already in
|
|
+ gous to <STRONG>is1</STRONG> <STRONG>,</STRONG> <STRONG>is2</STRONG> <STRONG>,</STRONG> <STRONG>if</STRONG> and <STRONG>is3</STRONG> respectively. These
|
|
+ strings are output by the <STRONG>reset</STRONG> program, which is used
|
|
+ when the terminal gets into a wedged state. Commands are
|
|
+ normally placed in <STRONG>rs1</STRONG>, <STRONG>rs2</STRONG> <STRONG>rs3</STRONG> and <STRONG>rf</STRONG> only if they pro-
|
|
+ duce annoying effects on the screen and are not necessary
|
|
+ when logging in. For example, the command to set the
|
|
+ vt100 into 80-column mode would normally be part of <STRONG>is2</STRONG>,
|
|
+ but it causes an annoying glitch of the screen and is not
|
|
+ normally needed since the terminal is usually already in
|
|
80 column mode.
|
|
|
|
- The <EM>reset</EM> program writes strings including <STRONG>iprog</STRONG>, etc., in
|
|
- the same order as the <EM>init</EM> program, using <STRONG>rs1</STRONG>, etc.,
|
|
+ The <STRONG>reset</STRONG> program writes strings including <STRONG>iprog</STRONG>, etc., in
|
|
+ the same order as the <EM>init</EM> program, using <STRONG>rs1</STRONG>, etc.,
|
|
instead of <STRONG>is1</STRONG>, etc. If any of <STRONG>rs1</STRONG>, <STRONG>rs2</STRONG>, <STRONG>rs3</STRONG>, or <STRONG>rf</STRONG> reset
|
|
- capability strings are missing, the <EM>reset</EM> program falls
|
|
+ capability strings are missing, the <STRONG>reset</STRONG> program falls
|
|
back upon the corresponding initialization capability
|
|
string.
|
|
|
|
If there are commands to set and clear tab stops, they can
|
|
- be given as <STRONG>tbc</STRONG> (clear all tab stops) and <STRONG>hts</STRONG> (set a tab
|
|
- stop in the current column of every row). If a more com-
|
|
- plex sequence is needed to set the tabs than can be
|
|
- described by this, the sequence can be placed in <STRONG>is2</STRONG> or
|
|
+ be given as <STRONG>tbc</STRONG> (clear all tab stops) and <STRONG>hts</STRONG> (set a tab
|
|
+ stop in the current column of every row). If a more com-
|
|
+ plex sequence is needed to set the tabs than can be
|
|
+ described by this, the sequence can be placed in <STRONG>is2</STRONG> or
|
|
<STRONG>if</STRONG>.
|
|
|
|
|
|
</PRE><H3><a name="h3-Delays-and-Padding">Delays and Padding</a></H3><PRE>
|
|
- Many older and slower terminals do not support either
|
|
+ Many older and slower terminals do not support either
|
|
XON/XOFF or DTR handshaking, including hard copy terminals
|
|
- and some very archaic CRTs (including, for example, DEC
|
|
- VT100s). These may require padding characters after cer-
|
|
+ and some very archaic CRTs (including, for example, DEC
|
|
+ VT100s). These may require padding characters after cer-
|
|
tain cursor motions and screen changes.
|
|
|
|
If the terminal uses xon/xoff handshaking for flow control
|
|
- (that is, it automatically emits ^S back to the host when
|
|
+ (that is, it automatically emits ^S back to the host when
|
|
its input buffers are close to full), set <STRONG>xon</STRONG>. This capa-
|
|
- bility suppresses the emission of padding. You can also
|
|
- set it for memory-mapped console devices effectively that
|
|
- do not have a speed limit. Padding information should
|
|
- still be included so that routines can make better deci-
|
|
+ bility suppresses the emission of padding. You can also
|
|
+ set it for memory-mapped console devices effectively that
|
|
+ do not have a speed limit. Padding information should
|
|
+ still be included so that routines can make better deci-
|
|
sions about relative costs, but actual pad characters will
|
|
not be transmitted.
|
|
|
|
- If <STRONG>pb</STRONG> (padding baud rate) is given, padding is suppressed
|
|
- at baud rates below the value of <STRONG>pb</STRONG>. If the entry has no
|
|
- padding baud rate, then whether padding is emitted or not
|
|
+ If <STRONG>pb</STRONG> (padding baud rate) is given, padding is suppressed
|
|
+ at baud rates below the value of <STRONG>pb</STRONG>. If the entry has no
|
|
+ padding baud rate, then whether padding is emitted or not
|
|
is completely controlled by <STRONG>xon</STRONG>.
|
|
|
|
- If the terminal requires other than a null (zero) charac-
|
|
- ter as a pad, then this can be given as <STRONG>pad</STRONG>. Only the
|
|
+ If the terminal requires other than a null (zero) charac-
|
|
+ ter as a pad, then this can be given as <STRONG>pad</STRONG>. Only the
|
|
first character of the <STRONG>pad</STRONG> string is used.
|
|
|
|
|
|
</PRE><H3><a name="h3-Status-Lines">Status Lines</a></H3><PRE>
|
|
- Some terminals have an extra "status line" which is not
|
|
- normally used by software (and thus not counted in the
|
|
+ Some terminals have an extra "status line" which is not
|
|
+ normally used by software (and thus not counted in the
|
|
terminal's <STRONG>lines</STRONG> capability).
|
|
|
|
- The simplest case is a status line which is cursor-
|
|
- addressable but not part of the main scrolling region on
|
|
- the screen; the Heathkit H19 has a status line of this
|
|
- kind, as would a 24-line VT100 with a 23-line scrolling
|
|
- region set up on initialization. This situation is indi-
|
|
+ The simplest case is a status line which is cursor-
|
|
+ addressable but not part of the main scrolling region on
|
|
+ the screen; the Heathkit H19 has a status line of this
|
|
+ kind, as would a 24-line VT100 with a 23-line scrolling
|
|
+ region set up on initialization. This situation is indi-
|
|
cated by the <STRONG>hs</STRONG> capability.
|
|
|
|
Some terminals with status lines need special sequences to
|
|
- access the status line. These may be expressed as a
|
|
+ access the status line. These may be expressed as a
|
|
string with single parameter <STRONG>tsl</STRONG> which takes the cursor to
|
|
- a given zero-origin column on the status line. The capa-
|
|
+ a given zero-origin column on the status line. The capa-
|
|
bility <STRONG>fsl</STRONG> must return to the main-screen cursor positions
|
|
- before the last <STRONG>tsl</STRONG>. You may need to embed the string
|
|
- values of <STRONG>sc</STRONG> (save cursor) and <STRONG>rc</STRONG> (restore cursor) in <STRONG>tsl</STRONG>
|
|
+ before the last <STRONG>tsl</STRONG>. You may need to embed the string
|
|
+ values of <STRONG>sc</STRONG> (save cursor) and <STRONG>rc</STRONG> (restore cursor) in <STRONG>tsl</STRONG>
|
|
and <STRONG>fsl</STRONG> to accomplish this.
|
|
|
|
- The status line is normally assumed to be the same width
|
|
- as the width of the terminal. If this is untrue, you can
|
|
+ The status line is normally assumed to be the same width
|
|
+ as the width of the terminal. If this is untrue, you can
|
|
specify it with the numeric capability <STRONG>wsl</STRONG>.
|
|
|
|
- A command to erase or blank the status line may be speci-
|
|
+ A command to erase or blank the status line may be speci-
|
|
fied as <STRONG>dsl</STRONG>.
|
|
|
|
- The boolean capability <STRONG>eslok</STRONG> specifies that escape
|
|
+ The boolean capability <STRONG>eslok</STRONG> specifies that escape
|
|
sequences, tabs, etc., work ordinarily in the status line.
|
|
|
|
- The <STRONG>ncurses</STRONG> implementation does not yet use any of these
|
|
- capabilities. They are documented here in case they ever
|
|
+ The <STRONG>ncurses</STRONG> implementation does not yet use any of these
|
|
+ capabilities. They are documented here in case they ever
|
|
become important.
|
|
|
|
|
|
</PRE><H3><a name="h3-Line-Graphics">Line Graphics</a></H3><PRE>
|
|
- Many terminals have alternate character sets useful for
|
|
- forms-drawing. Terminfo and <STRONG>curses</STRONG> build in support for
|
|
- the drawing characters supported by the VT100, with some
|
|
- characters from the AT&T 4410v1 added. This alternate
|
|
+ Many terminals have alternate character sets useful for
|
|
+ forms-drawing. Terminfo and <STRONG>curses</STRONG> build in support for
|
|
+ the drawing characters supported by the VT100, with some
|
|
+ characters from the AT&T 4410v1 added. This alternate
|
|
character set may be specified by the <STRONG>acsc</STRONG> capability.
|
|
|
|
<STRONG>Glyph</STRONG> <STRONG>ACS</STRONG> <STRONG>Ascii</STRONG> <STRONG>VT100</STRONG>
|
|
@@ -2050,58 +2057,58 @@
|
|
upper right corner ACS_URCORNER + k
|
|
vertical line ACS_VLINE | x
|
|
|
|
- The best way to define a new device's graphics set is to
|
|
- add a column to a copy of this table for your terminal,
|
|
- giving the character which (when emitted between
|
|
- <STRONG>smacs</STRONG>/<STRONG>rmacs</STRONG> switches) will be rendered as the correspond-
|
|
- ing graphic. Then read off the VT100/your terminal char-
|
|
- acter pairs right to left in sequence; these become the
|
|
+ The best way to define a new device's graphics set is to
|
|
+ add a column to a copy of this table for your terminal,
|
|
+ giving the character which (when emitted between
|
|
+ <STRONG>smacs</STRONG>/<STRONG>rmacs</STRONG> switches) will be rendered as the correspond-
|
|
+ ing graphic. Then read off the VT100/your terminal char-
|
|
+ acter pairs right to left in sequence; these become the
|
|
ACSC string.
|
|
|
|
|
|
</PRE><H3><a name="h3-Color-Handling">Color Handling</a></H3><PRE>
|
|
- Most color terminals are either "Tektronix-like" or "HP-
|
|
- like". Tektronix-like terminals have a predefined set of
|
|
- N colors (where N usually 8), and can set character-cell
|
|
+ Most color terminals are either "Tektronix-like" or "HP-
|
|
+ like". Tektronix-like terminals have a predefined set of
|
|
+ N colors (where N usually 8), and can set character-cell
|
|
foreground and background characters independently, mixing
|
|
- them into N * N color-pairs. On HP-like terminals, the
|
|
+ them into N * N color-pairs. On HP-like terminals, the
|
|
use must set each color pair up separately (foreground and
|
|
- background are not independently settable). Up to M
|
|
- color-pairs may be set up from 2*M different colors.
|
|
+ background are not independently settable). Up to M
|
|
+ color-pairs may be set up from 2*M different colors.
|
|
ANSI-compatible terminals are Tektronix-like.
|
|
|
|
Some basic color capabilities are independent of the color
|
|
method. The numeric capabilities <STRONG>colors</STRONG> and <STRONG>pairs</STRONG> specify
|
|
- the maximum numbers of colors and color-pairs that can be
|
|
- displayed simultaneously. The <STRONG>op</STRONG> (original pair) string
|
|
- resets foreground and background colors to their default
|
|
- values for the terminal. The <STRONG>oc</STRONG> string resets all colors
|
|
- or color-pairs to their default values for the terminal.
|
|
- Some terminals (including many PC terminal emulators)
|
|
- erase screen areas with the current background color
|
|
- rather than the power-up default background; these should
|
|
+ the maximum numbers of colors and color-pairs that can be
|
|
+ displayed simultaneously. The <STRONG>op</STRONG> (original pair) string
|
|
+ resets foreground and background colors to their default
|
|
+ values for the terminal. The <STRONG>oc</STRONG> string resets all colors
|
|
+ or color-pairs to their default values for the terminal.
|
|
+ Some terminals (including many PC terminal emulators)
|
|
+ erase screen areas with the current background color
|
|
+ rather than the power-up default background; these should
|
|
have the boolean capability <STRONG>bce</STRONG>.
|
|
|
|
- To change the current foreground or background color on a
|
|
- Tektronix-type terminal, use <STRONG>setaf</STRONG> (set ANSI foreground)
|
|
- and <STRONG>setab</STRONG> (set ANSI background) or <STRONG>setf</STRONG> (set foreground)
|
|
- and <STRONG>setb</STRONG> (set background). These take one parameter, the
|
|
+ To change the current foreground or background color on a
|
|
+ Tektronix-type terminal, use <STRONG>setaf</STRONG> (set ANSI foreground)
|
|
+ and <STRONG>setab</STRONG> (set ANSI background) or <STRONG>setf</STRONG> (set foreground)
|
|
+ and <STRONG>setb</STRONG> (set background). These take one parameter, the
|
|
color number. The SVr4 documentation describes only
|
|
- <STRONG>setaf</STRONG>/<STRONG>setab</STRONG>; the XPG4 draft says that "If the terminal
|
|
+ <STRONG>setaf</STRONG>/<STRONG>setab</STRONG>; the XPG4 draft says that "If the terminal
|
|
supports ANSI escape sequences to set background and fore-
|
|
- ground, they should be coded as <STRONG>setaf</STRONG> and <STRONG>setab</STRONG>, respec-
|
|
- tively. If the terminal supports other escape sequences
|
|
- to set background and foreground, they should be coded as
|
|
- <STRONG>setf</STRONG> and <STRONG>setb</STRONG>, respectively. The <EM>vidputs()</EM> function and
|
|
- the refresh functions use <STRONG>setaf</STRONG> and <STRONG>setab</STRONG> if they are
|
|
+ ground, they should be coded as <STRONG>setaf</STRONG> and <STRONG>setab</STRONG>, respec-
|
|
+ tively. If the terminal supports other escape sequences
|
|
+ to set background and foreground, they should be coded as
|
|
+ <STRONG>setf</STRONG> and <STRONG>setb</STRONG>, respectively. The <STRONG>vidputs</STRONG> function and the
|
|
+ refresh functions use <STRONG>setaf</STRONG> and <STRONG>setab</STRONG> if they are
|
|
defined."
|
|
|
|
- The <STRONG>setaf</STRONG>/<STRONG>setab</STRONG> and <STRONG>setf</STRONG>/<STRONG>setb</STRONG> capabilities take a single
|
|
+ The <STRONG>setaf</STRONG>/<STRONG>setab</STRONG> and <STRONG>setf</STRONG>/<STRONG>setb</STRONG> capabilities take a single
|
|
numeric argument each. Argument values 0-7 of <STRONG>setaf</STRONG>/<STRONG>setab</STRONG>
|
|
- are portably defined as follows (the middle column is the
|
|
+ are portably defined as follows (the middle column is the
|
|
symbolic #define available in the header for the <STRONG>curses</STRONG> or
|
|
- <STRONG>ncurses</STRONG> libraries). The terminal hardware is free to map
|
|
- these as it likes, but the RGB values indicate normal
|
|
+ <STRONG>ncurses</STRONG> libraries). The terminal hardware is free to map
|
|
+ these as it likes, but the RGB values indicate normal
|
|
locations in color space.
|
|
|
|
<STRONG>Color</STRONG> <STRONG>#define</STRONG> <STRONG>Value</STRONG> <STRONG>RGB</STRONG>
|
|
@@ -2114,7 +2121,7 @@
|
|
cyan <STRONG>COLOR_CYAN</STRONG> 6 0,max,max
|
|
white <STRONG>COLOR_WHITE</STRONG> 7 max,max,max
|
|
|
|
- The argument values of <STRONG>setf</STRONG>/<STRONG>setb</STRONG> historically correspond
|
|
+ The argument values of <STRONG>setf</STRONG>/<STRONG>setb</STRONG> historically correspond
|
|
to a different mapping, i.e.,
|
|
|
|
<STRONG>Color</STRONG> <STRONG>#define</STRONG> <STRONG>Value</STRONG> <STRONG>RGB</STRONG>
|
|
@@ -2128,32 +2135,32 @@
|
|
white <STRONG>COLOR_WHITE</STRONG> 7 max,max,max
|
|
|
|
It is important to not confuse the two sets of color capa-
|
|
- bilities; otherwise red/blue will be interchanged on the
|
|
+ bilities; otherwise red/blue will be interchanged on the
|
|
display.
|
|
|
|
- On an HP-like terminal, use <STRONG>scp</STRONG> with a color-pair number
|
|
+ On an HP-like terminal, use <STRONG>scp</STRONG> with a color-pair number
|
|
parameter to set which color pair is current.
|
|
|
|
- On a Tektronix-like terminal, the capability <STRONG>ccc</STRONG> may be
|
|
- present to indicate that colors can be modified. If so,
|
|
+ On a Tektronix-like terminal, the capability <STRONG>ccc</STRONG> may be
|
|
+ present to indicate that colors can be modified. If so,
|
|
the <STRONG>initc</STRONG> capability will take a color number (0 to <STRONG>colors</STRONG>
|
|
- - 1)and three more parameters which describe the color.
|
|
+ - 1)and three more parameters which describe the color.
|
|
These three parameters default to being interpreted as RGB
|
|
- (Red, Green, Blue) values. If the boolean capability <STRONG>hls</STRONG>
|
|
+ (Red, Green, Blue) values. If the boolean capability <STRONG>hls</STRONG>
|
|
is present, they are instead as HLS (Hue, Lightness, Satu-
|
|
ration) indices. The ranges are terminal-dependent.
|
|
|
|
- On an HP-like terminal, <STRONG>initp</STRONG> may give a capability for
|
|
- changing a color-pair value. It will take seven parame-
|
|
- ters; a color-pair number (0 to <STRONG>max_pairs</STRONG> - 1), and two
|
|
- triples describing first background and then foreground
|
|
- colors. These parameters must be (Red, Green, Blue) or
|
|
+ On an HP-like terminal, <STRONG>initp</STRONG> may give a capability for
|
|
+ changing a color-pair value. It will take seven parame-
|
|
+ ters; a color-pair number (0 to <STRONG>max_pairs</STRONG> - 1), and two
|
|
+ triples describing first background and then foreground
|
|
+ colors. These parameters must be (Red, Green, Blue) or
|
|
(Hue, Lightness, Saturation) depending on <STRONG>hls</STRONG>.
|
|
|
|
- On some color terminals, colors collide with highlights.
|
|
+ On some color terminals, colors collide with highlights.
|
|
You can register these collisions with the <STRONG>ncv</STRONG> capability.
|
|
- This is a bit-mask of attributes not to be used when col-
|
|
- ors are enabled. The correspondence with the attributes
|
|
+ This is a bit-mask of attributes not to be used when col-
|
|
+ ors are enabled. The correspondence with the attributes
|
|
understood by <STRONG>curses</STRONG> is as follows:
|
|
|
|
<STRONG>Attribute</STRONG> <STRONG>Bit</STRONG> <STRONG>Decimal</STRONG> <STRONG>Set</STRONG> <STRONG>by</STRONG>
|
|
@@ -2174,240 +2181,240 @@
|
|
A_VERTICAL 14 16384 sgr1
|
|
A_ITALIC 15 32768 sitm
|
|
|
|
- For example, on many IBM PC consoles, the underline
|
|
- attribute collides with the foreground color blue and is
|
|
- not available in color mode. These should have an <STRONG>ncv</STRONG>
|
|
+ For example, on many IBM PC consoles, the underline
|
|
+ attribute collides with the foreground color blue and is
|
|
+ not available in color mode. These should have an <STRONG>ncv</STRONG>
|
|
capability of 2.
|
|
|
|
- SVr4 curses does nothing with <STRONG>ncv</STRONG>, ncurses recognizes it
|
|
+ SVr4 curses does nothing with <STRONG>ncv</STRONG>, ncurses recognizes it
|
|
and optimizes the output in favor of colors.
|
|
|
|
|
|
</PRE><H3><a name="h3-Miscellaneous">Miscellaneous</a></H3><PRE>
|
|
- If the terminal requires other than a null (zero) charac-
|
|
- ter as a pad, then this can be given as pad. Only the
|
|
- first character of the pad string is used. If the termi-
|
|
+ If the terminal requires other than a null (zero) charac-
|
|
+ ter as a pad, then this can be given as pad. Only the
|
|
+ first character of the pad string is used. If the termi-
|
|
nal does not have a pad character, specify npc. Note that
|
|
- ncurses implements the termcap-compatible <STRONG>PC</STRONG> variable;
|
|
- though the application may set this value to something
|
|
- other than a null, ncurses will test <STRONG>npc</STRONG> first and use
|
|
+ ncurses implements the termcap-compatible <STRONG>PC</STRONG> variable;
|
|
+ though the application may set this value to something
|
|
+ other than a null, ncurses will test <STRONG>npc</STRONG> first and use
|
|
napms if the terminal has no pad character.
|
|
|
|
- If the terminal can move up or down half a line, this can
|
|
- be indicated with <STRONG>hu</STRONG> (half-line up) and <STRONG>hd</STRONG> (half-line
|
|
+ If the terminal can move up or down half a line, this can
|
|
+ be indicated with <STRONG>hu</STRONG> (half-line up) and <STRONG>hd</STRONG> (half-line
|
|
down). This is primarily useful for superscripts and sub-
|
|
- scripts on hard-copy terminals. If a hard-copy terminal
|
|
- can eject to the next page (form feed), give this as <STRONG>ff</STRONG>
|
|
+ scripts on hard-copy terminals. If a hard-copy terminal
|
|
+ can eject to the next page (form feed), give this as <STRONG>ff</STRONG>
|
|
(usually control L).
|
|
|
|
- If there is a command to repeat a given character a given
|
|
- number of times (to save time transmitting a large number
|
|
- of identical characters) this can be indicated with the
|
|
- parameterized string <STRONG>rep</STRONG>. The first parameter is the
|
|
- character to be repeated and the second is the number of
|
|
- times to repeat it. Thus, tparm(repeat_char, 'x', 10) is
|
|
+ If there is a command to repeat a given character a given
|
|
+ number of times (to save time transmitting a large number
|
|
+ of identical characters) this can be indicated with the
|
|
+ parameterized string <STRONG>rep</STRONG>. The first parameter is the
|
|
+ character to be repeated and the second is the number of
|
|
+ times to repeat it. Thus, tparm(repeat_char, 'x', 10) is
|
|
the same as "xxxxxxxxxx".
|
|
|
|
- If the terminal has a settable command character, such as
|
|
- the TEKTRONIX 4025, this can be indicated with <STRONG>cmdch</STRONG>. A
|
|
+ If the terminal has a settable command character, such as
|
|
+ the TEKTRONIX 4025, this can be indicated with <STRONG>cmdch</STRONG>. A
|
|
prototype command character is chosen which is used in all
|
|
- capabilities. This character is given in the <STRONG>cmdch</STRONG> capa-
|
|
- bility to identify it. The following convention is sup-
|
|
- ported on some UNIX systems: The environment is to be
|
|
- searched for a <STRONG>CC</STRONG> variable, and if found, all occurrences
|
|
+ capabilities. This character is given in the <STRONG>cmdch</STRONG> capa-
|
|
+ bility to identify it. The following convention is sup-
|
|
+ ported on some UNIX systems: The environment is to be
|
|
+ searched for a <STRONG>CC</STRONG> variable, and if found, all occurrences
|
|
of the prototype character are replaced with the character
|
|
in the environment variable.
|
|
|
|
- Terminal descriptions that do not represent a specific
|
|
+ Terminal descriptions that do not represent a specific
|
|
kind of known terminal, such as <EM>switch</EM>, <EM>dialup</EM>, <EM>patch</EM>, and
|
|
- <EM>network</EM>, should include the <STRONG>gn</STRONG> (generic) capability so
|
|
- that programs can complain that they do not know how to
|
|
- talk to the terminal. (This capability does not apply to
|
|
- <EM>virtual</EM> terminal descriptions for which the escape
|
|
+ <EM>network</EM>, should include the <STRONG>gn</STRONG> (generic) capability so
|
|
+ that programs can complain that they do not know how to
|
|
+ talk to the terminal. (This capability does not apply to
|
|
+ <EM>virtual</EM> terminal descriptions for which the escape
|
|
sequences are known.)
|
|
|
|
- If the terminal has a "meta key" which acts as a shift
|
|
- key, setting the 8th bit of any character transmitted,
|
|
- this fact can be indicated with <STRONG>km</STRONG>. Otherwise, software
|
|
+ If the terminal has a "meta key" which acts as a shift
|
|
+ key, setting the 8th bit of any character transmitted,
|
|
+ this fact can be indicated with <STRONG>km</STRONG>. Otherwise, software
|
|
will assume that the 8th bit is parity and it will usually
|
|
- be cleared. If strings exist to turn this "meta mode" on
|
|
+ be cleared. If strings exist to turn this "meta mode" on
|
|
and off, they can be given as <STRONG>smm</STRONG> and <STRONG>rmm</STRONG>.
|
|
|
|
- If the terminal has more lines of memory than will fit on
|
|
- the screen at once, the number of lines of memory can be
|
|
- indicated with <STRONG>lm</STRONG>. A value of <STRONG>lm</STRONG>#0 indicates that the
|
|
+ If the terminal has more lines of memory than will fit on
|
|
+ the screen at once, the number of lines of memory can be
|
|
+ indicated with <STRONG>lm</STRONG>. A value of <STRONG>lm</STRONG>#0 indicates that the
|
|
number of lines is not fixed, but that there is still more
|
|
memory than fits on the screen.
|
|
|
|
If the terminal is one of those supported by the UNIX vir-
|
|
- tual terminal protocol, the terminal number can be given
|
|
+ tual terminal protocol, the terminal number can be given
|
|
as <STRONG>vt</STRONG>.
|
|
|
|
Media copy strings which control an auxiliary printer con-
|
|
nected to the terminal can be given as <STRONG>mc0</STRONG>: print the con-
|
|
- tents of the screen, <STRONG>mc4</STRONG>: turn off the printer, and <STRONG>mc5</STRONG>:
|
|
- turn on the printer. When the printer is on, all text
|
|
- sent to the terminal will be sent to the printer. It is
|
|
+ tents of the screen, <STRONG>mc4</STRONG>: turn off the printer, and <STRONG>mc5</STRONG>:
|
|
+ turn on the printer. When the printer is on, all text
|
|
+ sent to the terminal will be sent to the printer. It is
|
|
undefined whether the text is also displayed on the termi-
|
|
nal screen when the printer is on. A variation <STRONG>mc5p</STRONG> takes
|
|
one parameter, and leaves the printer on for as many char-
|
|
- acters as the value of the parameter, then turns the
|
|
- printer off. The parameter should not exceed 255. All
|
|
+ acters as the value of the parameter, then turns the
|
|
+ printer off. The parameter should not exceed 255. All
|
|
text, including <STRONG>mc4</STRONG>, is transparently passed to the
|
|
printer while an <STRONG>mc5p</STRONG> is in effect.
|
|
|
|
|
|
</PRE><H3><a name="h3-Glitches-and-Braindamage">Glitches and Braindamage</a></H3><PRE>
|
|
- Hazeltine terminals, which do not allow "~" characters to
|
|
+ Hazeltine terminals, which do not allow "~" characters to
|
|
be displayed should indicate <STRONG>hz</STRONG>.
|
|
|
|
Terminals which ignore a line-feed immediately after an <STRONG>am</STRONG>
|
|
wrap, such as the Concept and vt100, should indicate <STRONG>xenl</STRONG>.
|
|
|
|
- If <STRONG>el</STRONG> is required to get rid of standout (instead of
|
|
- merely writing normal text on top of it), <STRONG>xhp</STRONG> should be
|
|
+ If <STRONG>el</STRONG> is required to get rid of standout (instead of
|
|
+ merely writing normal text on top of it), <STRONG>xhp</STRONG> should be
|
|
given.
|
|
|
|
- Teleray terminals, where tabs turn all characters moved
|
|
- over to blanks, should indicate <STRONG>xt</STRONG> (destructive tabs).
|
|
- Note: the variable indicating this is now
|
|
- "dest_tabs_magic_smso"; in older versions, it was tel-
|
|
+ Teleray terminals, where tabs turn all characters moved
|
|
+ over to blanks, should indicate <STRONG>xt</STRONG> (destructive tabs).
|
|
+ Note: the variable indicating this is now
|
|
+ "dest_tabs_magic_smso"; in older versions, it was tel-
|
|
eray_glitch. This glitch is also taken to mean that it is
|
|
- not possible to position the cursor on top of a "magic
|
|
- cookie", that to erase standout mode it is instead neces-
|
|
+ not possible to position the cursor on top of a "magic
|
|
+ cookie", that to erase standout mode it is instead neces-
|
|
sary to use delete and insert line. The ncurses implemen-
|
|
tation ignores this glitch.
|
|
|
|
- The Beehive Superbee, which is unable to correctly trans-
|
|
- mit the escape or control C characters, has <STRONG>xsb</STRONG>, indicat-
|
|
- ing that the f1 key is used for escape and f2 for control
|
|
- C. (Only certain Superbees have this problem, depending
|
|
- on the ROM.) Note that in older terminfo versions, this
|
|
- capability was called "beehive_glitch"; it is now
|
|
+ The Beehive Superbee, which is unable to correctly trans-
|
|
+ mit the escape or control C characters, has <STRONG>xsb</STRONG>, indicat-
|
|
+ ing that the f1 key is used for escape and f2 for control
|
|
+ C. (Only certain Superbees have this problem, depending
|
|
+ on the ROM.) Note that in older terminfo versions, this
|
|
+ capability was called "beehive_glitch"; it is now
|
|
"no_esc_ctl_c".
|
|
|
|
- Other specific terminal problems may be corrected by
|
|
+ Other specific terminal problems may be corrected by
|
|
adding more capabilities of the form <STRONG>x</STRONG><EM>x</EM>.
|
|
|
|
|
|
</PRE><H3><a name="h3-Similar-Terminals">Similar Terminals</a></H3><PRE>
|
|
If there are two very similar terminals, one (the variant)
|
|
- can be defined as being just like the other (the base)
|
|
- with certain exceptions. In the definition of the vari-
|
|
- ant, the string capability <STRONG>use</STRONG> can be given with the name
|
|
- of the base terminal. The capabilities given before <STRONG>use</STRONG>
|
|
- override those in the base type named by <STRONG>use</STRONG>. If there
|
|
- are multiple <STRONG>use</STRONG> capabilities, they are merged in reverse
|
|
- order. That is, the rightmost <STRONG>use</STRONG> reference is processed
|
|
- first, then the one to its left, and so forth. Capabili-
|
|
- ties given explicitly in the entry override those brought
|
|
+ can be defined as being just like the other (the base)
|
|
+ with certain exceptions. In the definition of the vari-
|
|
+ ant, the string capability <STRONG>use</STRONG> can be given with the name
|
|
+ of the base terminal. The capabilities given before <STRONG>use</STRONG>
|
|
+ override those in the base type named by <STRONG>use</STRONG>. If there
|
|
+ are multiple <STRONG>use</STRONG> capabilities, they are merged in reverse
|
|
+ order. That is, the rightmost <STRONG>use</STRONG> reference is processed
|
|
+ first, then the one to its left, and so forth. Capabili-
|
|
+ ties given explicitly in the entry override those brought
|
|
in by <STRONG>use</STRONG> references.
|
|
|
|
A capability can be canceled by placing <STRONG>xx@</STRONG> to the left of
|
|
- the use reference that imports it, where <EM>xx</EM> is the capa-
|
|
+ the use reference that imports it, where <EM>xx</EM> is the capa-
|
|
bility. For example, the entry
|
|
|
|
2621-nl, smkx@, rmkx@, use=2621,
|
|
|
|
- defines a 2621-nl that does not have the <STRONG>smkx</STRONG> or <STRONG>rmkx</STRONG>
|
|
- capabilities, and hence does not turn on the function key
|
|
- labels when in visual mode. This is useful for different
|
|
+ defines a 2621-nl that does not have the <STRONG>smkx</STRONG> or <STRONG>rmkx</STRONG>
|
|
+ capabilities, and hence does not turn on the function key
|
|
+ labels when in visual mode. This is useful for different
|
|
modes for a terminal, or for different user preferences.
|
|
|
|
|
|
</PRE><H3><a name="h3-Pitfalls-of-Long-Entries">Pitfalls of Long Entries</a></H3><PRE>
|
|
- Long terminfo entries are unlikely to be a problem; to
|
|
- date, no entry has even approached terminfo's 4096-byte
|
|
+ Long terminfo entries are unlikely to be a problem; to
|
|
+ date, no entry has even approached terminfo's 4096-byte
|
|
string-table maximum. Unfortunately, the termcap transla-
|
|
tions are much more strictly limited (to 1023 bytes), thus
|
|
- termcap translations of long terminfo entries can cause
|
|
+ termcap translations of long terminfo entries can cause
|
|
problems.
|
|
|
|
- The man pages for 4.3BSD and older versions of <STRONG>tgetent()</STRONG>
|
|
- instruct the user to allocate a 1024-byte buffer for the
|
|
- termcap entry. The entry gets null-terminated by the
|
|
+ The man pages for 4.3BSD and older versions of <STRONG>tgetent</STRONG>
|
|
+ instruct the user to allocate a 1024-byte buffer for the
|
|
+ termcap entry. The entry gets null-terminated by the
|
|
termcap library, so that makes the maximum safe length for
|
|
- a termcap entry 1k-1 (1023) bytes. Depending on what the
|
|
- application and the termcap library being used does, and
|
|
- where in the termcap file the terminal type that <STRONG>tgetent()</STRONG>
|
|
+ a termcap entry 1k-1 (1023) bytes. Depending on what the
|
|
+ application and the termcap library being used does, and
|
|
+ where in the termcap file the terminal type that <STRONG>tgetent</STRONG>
|
|
is searching for is, several bad things can happen.
|
|
|
|
- Some termcap libraries print a warning message or exit if
|
|
- they find an entry that's longer than 1023 bytes; others
|
|
- do not; others truncate the entries to 1023 bytes. Some
|
|
+ Some termcap libraries print a warning message or exit if
|
|
+ they find an entry that's longer than 1023 bytes; others
|
|
+ do not; others truncate the entries to 1023 bytes. Some
|
|
application programs allocate more than the recommended 1K
|
|
for the termcap entry; others do not.
|
|
|
|
Each termcap entry has two important sizes associated with
|
|
it: before "tc" expansion, and after "tc" expansion. "tc"
|
|
- is the capability that tacks on another termcap entry to
|
|
- the end of the current one, to add on its capabilities.
|
|
- If a termcap entry does not use the "tc" capability, then
|
|
+ is the capability that tacks on another termcap entry to
|
|
+ the end of the current one, to add on its capabilities.
|
|
+ If a termcap entry does not use the "tc" capability, then
|
|
of course the two lengths are the same.
|
|
|
|
- The "before tc expansion" length is the most important
|
|
- one, because it affects more than just users of that par-
|
|
- ticular terminal. This is the length of the entry as it
|
|
+ The "before tc expansion" length is the most important
|
|
+ one, because it affects more than just users of that par-
|
|
+ ticular terminal. This is the length of the entry as it
|
|
exists in /etc/termcap, minus the backslash-newline pairs,
|
|
- which <STRONG>tgetent()</STRONG> strips out while reading it. Some termcap
|
|
- libraries strip off the final newline, too (GNU termcap
|
|
+ which <STRONG>tgetent</STRONG> strips out while reading it. Some termcap
|
|
+ libraries strip off the final newline, too (GNU termcap
|
|
does not). Now suppose:
|
|
|
|
- <STRONG>o</STRONG> a termcap entry before expansion is more than 1023
|
|
+ <STRONG>o</STRONG> a termcap entry before expansion is more than 1023
|
|
bytes long,
|
|
|
|
<STRONG>o</STRONG> and the application has only allocated a 1k buffer,
|
|
|
|
- <STRONG>o</STRONG> and the termcap library (like the one in BSD/OS 1.1
|
|
- and GNU) reads the whole entry into the buffer, no
|
|
- matter what its length, to see if it is the entry it
|
|
+ <STRONG>o</STRONG> and the termcap library (like the one in BSD/OS 1.1
|
|
+ and GNU) reads the whole entry into the buffer, no
|
|
+ matter what its length, to see if it is the entry it
|
|
wants,
|
|
|
|
- <STRONG>o</STRONG> and <STRONG>tgetent()</STRONG> is searching for a terminal type that
|
|
- either is the long entry, appears in the termcap file
|
|
- after the long entry, or does not appear in the file
|
|
- at all (so that <STRONG>tgetent()</STRONG> has to search the whole
|
|
- termcap file).
|
|
-
|
|
- Then <STRONG>tgetent()</STRONG> will overwrite memory, perhaps its stack,
|
|
- and probably core dump the program. Programs like telnet
|
|
- are particularly vulnerable; modern telnets pass along
|
|
- values like the terminal type automatically. The results
|
|
- are almost as undesirable with a termcap library, like
|
|
- SunOS 4.1.3 and Ultrix 4.4, that prints warning messages
|
|
- when it reads an overly long termcap entry. If a termcap
|
|
- library truncates long entries, like OSF/1 3.0, it is
|
|
- immune to dying here but will return incorrect data for
|
|
- the terminal.
|
|
+ <STRONG>o</STRONG> and <STRONG>tgetent</STRONG> is searching for a terminal type that
|
|
+ either is the long entry, appears in the termcap file
|
|
+ after the long entry, or does not appear in the file
|
|
+ at all (so that <STRONG>tgetent</STRONG> has to search the whole term-
|
|
+ cap file).
|
|
+
|
|
+ Then <STRONG>tgetent</STRONG> will overwrite memory, perhaps its stack, and
|
|
+ probably core dump the program. Programs like telnet are
|
|
+ particularly vulnerable; modern telnets pass along values
|
|
+ like the terminal type automatically. The results are
|
|
+ almost as undesirable with a termcap library, like SunOS
|
|
+ 4.1.3 and Ultrix 4.4, that prints warning messages when it
|
|
+ reads an overly long termcap entry. If a termcap library
|
|
+ truncates long entries, like OSF/1 3.0, it is immune to
|
|
+ dying here but will return incorrect data for the termi-
|
|
+ nal.
|
|
|
|
The "after tc expansion" length will have a similar effect
|
|
to the above, but only for people who actually set TERM to
|
|
- that terminal type, since <STRONG>tgetent()</STRONG> only does "tc" expan-
|
|
- sion once it is found the terminal type it was looking
|
|
- for, not while searching.
|
|
+ that terminal type, since <STRONG>tgetent</STRONG> only does "tc" expansion
|
|
+ once it is found the terminal type it was looking for, not
|
|
+ while searching.
|
|
|
|
In summary, a termcap entry that is longer than 1023 bytes
|
|
- can cause, on various combinations of termcap libraries
|
|
- and applications, a core dump, warnings, or incorrect
|
|
- operation. If it is too long even before "tc" expansion,
|
|
+ can cause, on various combinations of termcap libraries
|
|
+ and applications, a core dump, warnings, or incorrect
|
|
+ operation. If it is too long even before "tc" expansion,
|
|
it will have this effect even for users of some other ter-
|
|
- minal types and users whose TERM variable does not have a
|
|
+ minal types and users whose TERM variable does not have a
|
|
termcap entry.
|
|
|
|
When in -C (translate to termcap) mode, the <STRONG>ncurses</STRONG> imple-
|
|
mentation of <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG> issues warning messages when the pre-
|
|
- tc length of a termcap translation is too long. The -c
|
|
- (check) option also checks resolved (after tc expansion)
|
|
+ tc length of a termcap translation is too long. The -c
|
|
+ (check) option also checks resolved (after tc expansion)
|
|
lengths.
|
|
|
|
|
|
</PRE><H3><a name="h3-Binary-Compatibility">Binary Compatibility</a></H3><PRE>
|
|
- It is not wise to count on portability of binary terminfo
|
|
- entries between commercial UNIX versions. The problem is
|
|
- that there are at least two versions of terminfo (under
|
|
+ It is not wise to count on portability of binary terminfo
|
|
+ entries between commercial UNIX versions. The problem is
|
|
+ that there are at least two versions of terminfo (under
|
|
HP-UX and AIX) which diverged from System V terminfo after
|
|
- SVr1, and have added extension capabilities to the string
|
|
- table that (in the binary format) collide with System V
|
|
+ SVr1, and have added extension capabilities to the string
|
|
+ table that (in the binary format) collide with System V
|
|
and XSI Curses extensions.
|
|
|
|
|
|
@@ -2415,66 +2422,66 @@
|
|
Searching for terminal descriptions in <STRONG>$HOME/.terminfo</STRONG> and
|
|
TERMINFO_DIRS is not supported by older implementations.
|
|
|
|
- Some SVr4 <STRONG>curses</STRONG> implementations, and all previous to
|
|
- SVr4, do not interpret the %A and %O operators in parame-
|
|
+ Some SVr4 <STRONG>curses</STRONG> implementations, and all previous to
|
|
+ SVr4, do not interpret the %A and %O operators in parame-
|
|
ter strings.
|
|
|
|
- SVr4/XPG4 do not specify whether <STRONG>msgr</STRONG> licenses movement
|
|
- while in an alternate-character-set mode (such modes may,
|
|
- among other things, map CR and NL to characters that do
|
|
- not trigger local motions). The <STRONG>ncurses</STRONG> implementation
|
|
- ignores <STRONG>msgr</STRONG> in <STRONG>ALTCHARSET</STRONG> mode. This raises the possi-
|
|
- bility that an XPG4 implementation making the opposite
|
|
- interpretation may need terminfo entries made for <STRONG>ncurses</STRONG>
|
|
+ SVr4/XPG4 do not specify whether <STRONG>msgr</STRONG> licenses movement
|
|
+ while in an alternate-character-set mode (such modes may,
|
|
+ among other things, map CR and NL to characters that do
|
|
+ not trigger local motions). The <STRONG>ncurses</STRONG> implementation
|
|
+ ignores <STRONG>msgr</STRONG> in <STRONG>ALTCHARSET</STRONG> mode. This raises the possi-
|
|
+ bility that an XPG4 implementation making the opposite
|
|
+ interpretation may need terminfo entries made for <STRONG>ncurses</STRONG>
|
|
to have <STRONG>msgr</STRONG> turned off.
|
|
|
|
- The <STRONG>ncurses</STRONG> library handles insert-character and insert-
|
|
+ The <STRONG>ncurses</STRONG> library handles insert-character and insert-
|
|
character modes in a slightly non-standard way to get bet-
|
|
- ter update efficiency. See the <STRONG>Insert/Delete</STRONG> <STRONG>Character</STRONG>
|
|
+ ter update efficiency. See the <STRONG>Insert/Delete</STRONG> <STRONG>Character</STRONG>
|
|
subsection above.
|
|
|
|
- The parameter substitutions for <STRONG>set_clock</STRONG> and <STRONG>dis-</STRONG>
|
|
- <STRONG>play_clock</STRONG> are not documented in SVr4 or the XSI Curses
|
|
+ The parameter substitutions for <STRONG>set_clock</STRONG> and <STRONG>dis-</STRONG>
|
|
+ <STRONG>play_clock</STRONG> are not documented in SVr4 or the XSI Curses
|
|
standard. They are deduced from the documentation for the
|
|
AT&T 505 terminal.
|
|
|
|
- Be careful assigning the <STRONG>kmous</STRONG> capability. The <STRONG>ncurses</STRONG>
|
|
- wants to interpret it as <STRONG>KEY_MOUSE</STRONG>, for use by terminals
|
|
- and emulators like xterm that can return mouse-tracking
|
|
+ Be careful assigning the <STRONG>kmous</STRONG> capability. The <STRONG>ncurses</STRONG>
|
|
+ wants to interpret it as <STRONG>KEY_MOUSE</STRONG>, for use by terminals
|
|
+ and emulators like xterm that can return mouse-tracking
|
|
information in the keyboard-input stream.
|
|
|
|
X/Open Curses does not mention italics. Portable applica-
|
|
- tions must assume that numeric capabilities are signed
|
|
- 16-bit values. This includes the <EM>no</EM><STRONG>_</STRONG><EM>color</EM><STRONG>_</STRONG><EM>video</EM> (ncv)
|
|
- capability. The 32768 mask value used for italics with
|
|
- ncv can be confused with an absent or cancelled ncv. If
|
|
- italics should work with colors, then the ncv value must
|
|
+ tions must assume that numeric capabilities are signed
|
|
+ 16-bit values. This includes the <EM>no</EM><STRONG>_</STRONG><EM>color</EM><STRONG>_</STRONG><EM>video</EM> (ncv)
|
|
+ capability. The 32768 mask value used for italics with
|
|
+ ncv can be confused with an absent or cancelled ncv. If
|
|
+ italics should work with colors, then the ncv value must
|
|
be specified, even if it is zero.
|
|
|
|
- Different commercial ports of terminfo and curses support
|
|
- different subsets of the XSI Curses standard and (in some
|
|
+ Different commercial ports of terminfo and curses support
|
|
+ different subsets of the XSI Curses standard and (in some
|
|
cases) different extension sets. Here is a summary, accu-
|
|
rate as of October 1995:
|
|
|
|
<STRONG>SVR4,</STRONG> <STRONG>Solaris,</STRONG> <STRONG>ncurses</STRONG> -- These support all SVr4 capabili-
|
|
ties.
|
|
|
|
- <STRONG>SGI</STRONG> -- Supports the SVr4 set, adds one undocumented
|
|
+ <STRONG>SGI</STRONG> -- Supports the SVr4 set, adds one undocumented
|
|
extended string capability (<STRONG>set_pglen</STRONG>).
|
|
|
|
- <STRONG>SVr1,</STRONG> <STRONG>Ultrix</STRONG> -- These support a restricted subset of ter-
|
|
- minfo capabilities. The booleans end with <STRONG>xon_xoff</STRONG>; the
|
|
- numerics with <STRONG>width_status_line</STRONG>; and the strings with
|
|
+ <STRONG>SVr1,</STRONG> <STRONG>Ultrix</STRONG> -- These support a restricted subset of ter-
|
|
+ minfo capabilities. The booleans end with <STRONG>xon_xoff</STRONG>; the
|
|
+ numerics with <STRONG>width_status_line</STRONG>; and the strings with
|
|
<STRONG>prtr_non</STRONG>.
|
|
|
|
- <STRONG>HP/UX</STRONG> -- Supports the SVr1 subset, plus the SVr[234]
|
|
+ <STRONG>HP/UX</STRONG> -- Supports the SVr1 subset, plus the SVr[234]
|
|
numerics <STRONG>num_labels</STRONG>, <STRONG>label_height</STRONG>, <STRONG>label_width</STRONG>, plus func-
|
|
- tion keys 11 through 63, plus <STRONG>plab_norm</STRONG>, <STRONG>label_on</STRONG>, and
|
|
+ tion keys 11 through 63, plus <STRONG>plab_norm</STRONG>, <STRONG>label_on</STRONG>, and
|
|
<STRONG>label_off</STRONG>, plus some incompatible extensions in the string
|
|
table.
|
|
|
|
- <STRONG>AIX</STRONG> -- Supports the SVr1 subset, plus function keys 11
|
|
- through 63, plus a number of incompatible string table
|
|
+ <STRONG>AIX</STRONG> -- Supports the SVr1 subset, plus function keys 11
|
|
+ through 63, plus a number of incompatible string table
|
|
extensions.
|
|
|
|
<STRONG>OSF</STRONG> -- Supports both the SVr4 set and the AIX extensions.
|
|
@@ -2486,12 +2493,12 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
|
|
- <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG>, <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>, <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG>printf(3)</STRONG>, <STRONG><A HREF="term.5.html">term(5)</A></STRONG>.
|
|
+ <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG>, <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>, <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG>printf(3)</STRONG>, <STRONG><A HREF="term.5.html">term(5)</A></STRONG>.
|
|
<STRONG><A HREF="term_variables.3x.html">term_variables(3x)</A></STRONG>.
|
|
|
|
|
|
</PRE><H2><a name="h2-AUTHORS">AUTHORS</a></H2><PRE>
|
|
- Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey.
|
|
+ Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey.
|
|
Based on pcurses by Pavel Curtis.
|
|
|
|
|
|
Index: doc/html/man/tic.1m.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/tic.1m.html 2016-09-10 22:14:42.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/tic.1m.html 2016-10-15 23:12:24.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
<!--
|
|
****************************************************************************
|
|
- * Copyright (c) 1998-2014,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
* sale, use or other dealings in this Software without prior written *
|
|
* authorization. *
|
|
****************************************************************************
|
|
- * @Id: tic.1m,v 1.61 2015/09/05 20:45:49 tom Exp @
|
|
+ * @Id: tic.1m,v 1.62 2016/10/01 17:14:50 tom Exp @
|
|
-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<HTML>
|
|
@@ -50,7 +50,7 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-SYNOPSIS">SYNOPSIS</a></H2><PRE>
|
|
- <STRONG>tic</STRONG> [<STRONG>-01CDGIKLNTUVacfgqrstx</STRONG>] [<STRONG>-e</STRONG> <EM>names</EM>] [<STRONG>-o</STRONG> <EM>dir</EM>] [<STRONG>-Q</STRONG>[<EM>n</EM>]]
|
|
+ <STRONG>tic</STRONG> [<STRONG>-01CDGIKLNTUVWacfgqrstx</STRONG>] [<STRONG>-e</STRONG> <EM>names</EM>] [<STRONG>-o</STRONG> <EM>dir</EM>] [<STRONG>-Q</STRONG>[<EM>n</EM>]]
|
|
[<STRONG>-R</STRONG> <EM>subset</EM>] [<STRONG>-v</STRONG>[<EM>n</EM>]] [<STRONG>-w</STRONG>[<EM>n</EM>]] <EM>file</EM>
|
|
|
|
|
|
@@ -304,25 +304,28 @@
|
|
If the debug level <EM>n</EM> is not given, it is taken to be
|
|
one.
|
|
|
|
- <STRONG>-w</STRONG><EM>n</EM> specifies the width of the output. The parameter is
|
|
+ <STRONG>-W</STRONG> By itself, the <STRONG>-w</STRONG> option will not force long strings
|
|
+ to be wrapped. Use the <STRONG>-W</STRONG> option to do this.
|
|
+
|
|
+ <STRONG>-w</STRONG><EM>n</EM> specifies the width of the output. The parameter is
|
|
optional. If it is omitted, it defaults to 60.
|
|
|
|
<STRONG>-x</STRONG> Treat unknown capabilities as user-defined. That is,
|
|
- if you supply a capability name which <STRONG>tic</STRONG> does not
|
|
+ if you supply a capability name which <STRONG>tic</STRONG> does not
|
|
recognize, it will infer its type (boolean, number or
|
|
- string) from the syntax and make an extended table
|
|
+ string) from the syntax and make an extended table
|
|
entry for that. User-defined capability strings
|
|
- whose name begins with "k" are treated as function
|
|
+ whose name begins with "k" are treated as function
|
|
keys.
|
|
|
|
|
|
</PRE><H3><a name="h3-PARAMETERS">PARAMETERS</a></H3><PRE>
|
|
<EM>file</EM> contains one or more <STRONG>terminfo</STRONG> terminal descriptions
|
|
- in source format [see <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>]. Each descrip-
|
|
- tion in the file describes the capabilities of a
|
|
+ in source format [see <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>]. Each descrip-
|
|
+ tion in the file describes the capabilities of a
|
|
particular terminal.
|
|
|
|
- If <EM>file</EM> is "-", then the data is read from the
|
|
+ If <EM>file</EM> is "-", then the data is read from the
|
|
standard input. The <EM>file</EM> parameter may also be the
|
|
path of a character-device.
|
|
|
|
@@ -332,60 +335,60 @@
|
|
umented in <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>. The exception is the <STRONG>use</STRONG> capabil-
|
|
ity.
|
|
|
|
- When a <STRONG>use</STRONG>=<EM>entry</EM>-<EM>name</EM> field is discovered in a terminal
|
|
- entry currently being compiled, <STRONG>tic</STRONG> reads in the binary
|
|
- from <STRONG>/usr/share/terminfo</STRONG> to complete the entry. (Entries
|
|
- created from <EM>file</EM> will be used first. <STRONG>tic</STRONG> duplicates the
|
|
+ When a <STRONG>use</STRONG>=<EM>entry</EM>-<EM>name</EM> field is discovered in a terminal
|
|
+ entry currently being compiled, <STRONG>tic</STRONG> reads in the binary
|
|
+ from <STRONG>/usr/share/terminfo</STRONG> to complete the entry. (Entries
|
|
+ created from <EM>file</EM> will be used first. <STRONG>tic</STRONG> duplicates the
|
|
capabilities in <EM>entry</EM>-<EM>name</EM> for the current entry, with the
|
|
- exception of those capabilities that explicitly are
|
|
+ exception of those capabilities that explicitly are
|
|
defined in the current entry.
|
|
|
|
- When an entry, e.g., <STRONG>entry_name_1</STRONG>, contains a
|
|
- <STRONG>use=</STRONG><EM>entry</EM>_<EM>name</EM>_<EM>2</EM> field, any canceled capabilities in
|
|
- <EM>entry</EM>_<EM>name</EM>_<EM>2</EM> must also appear in <STRONG>entry_name_1</STRONG> before <STRONG>use=</STRONG>
|
|
+ When an entry, e.g., <STRONG>entry_name_1</STRONG>, contains a
|
|
+ <STRONG>use=</STRONG><EM>entry</EM>_<EM>name</EM>_<EM>2</EM> field, any canceled capabilities in
|
|
+ <EM>entry</EM>_<EM>name</EM>_<EM>2</EM> must also appear in <STRONG>entry_name_1</STRONG> before <STRONG>use=</STRONG>
|
|
for these capabilities to be canceled in <STRONG>entry_name_1</STRONG>.
|
|
|
|
Total compiled entries cannot exceed 4096 bytes. The name
|
|
- field cannot exceed 512 bytes. Terminal names exceeding
|
|
- the maximum alias length (32 characters on systems with
|
|
+ field cannot exceed 512 bytes. Terminal names exceeding
|
|
+ the maximum alias length (32 characters on systems with
|
|
long filenames, 14 characters otherwise) will be truncated
|
|
- to the maximum alias length and a warning message will be
|
|
+ to the maximum alias length and a warning message will be
|
|
printed.
|
|
|
|
|
|
</PRE><H2><a name="h2-COMPATIBILITY">COMPATIBILITY</a></H2><PRE>
|
|
- There is some evidence that historic <STRONG>tic</STRONG> implementations
|
|
- treated description fields with no whitespace in them as
|
|
- additional aliases or short names. This <STRONG>tic</STRONG> does not do
|
|
- that, but it does warn when description fields may be
|
|
+ There is some evidence that historic <STRONG>tic</STRONG> implementations
|
|
+ treated description fields with no whitespace in them as
|
|
+ additional aliases or short names. This <STRONG>tic</STRONG> does not do
|
|
+ that, but it does warn when description fields may be
|
|
treated that way and check them for dangerous characters.
|
|
|
|
|
|
</PRE><H2><a name="h2-EXTENSIONS">EXTENSIONS</a></H2><PRE>
|
|
Unlike the SVr4 <STRONG>tic</STRONG> command, this implementation can actu-
|
|
- ally compile termcap sources. In fact, entries in ter-
|
|
- minfo and termcap syntax can be mixed in a single source
|
|
+ ally compile termcap sources. In fact, entries in ter-
|
|
+ minfo and termcap syntax can be mixed in a single source
|
|
file. See <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG> for the list of termcap names taken
|
|
to be equivalent to terminfo names.
|
|
|
|
- The SVr4 manual pages are not clear on the resolution
|
|
- rules for <STRONG>use</STRONG> capabilities. This implementation of <STRONG>tic</STRONG>
|
|
+ The SVr4 manual pages are not clear on the resolution
|
|
+ rules for <STRONG>use</STRONG> capabilities. This implementation of <STRONG>tic</STRONG>
|
|
will find <STRONG>use</STRONG> targets anywhere in the source file, or any-
|
|
- where in the file tree rooted at <STRONG>TERMINFO</STRONG> (if <STRONG>TERMINFO</STRONG> is
|
|
+ where in the file tree rooted at <STRONG>TERMINFO</STRONG> (if <STRONG>TERMINFO</STRONG> is
|
|
defined), or in the user's <EM>$HOME/.terminfo</EM> database (if it
|
|
- exists), or (finally) anywhere in the system's file tree
|
|
+ exists), or (finally) anywhere in the system's file tree
|
|
of compiled entries.
|
|
|
|
- The error messages from this <STRONG>tic</STRONG> have the same format as
|
|
- GNU C error messages, and can be parsed by GNU Emacs's
|
|
+ The error messages from this <STRONG>tic</STRONG> have the same format as
|
|
+ GNU C error messages, and can be parsed by GNU Emacs's
|
|
compile facility.
|
|
|
|
- The <STRONG>-0</STRONG>, <STRONG>-1</STRONG>, <STRONG>-C</STRONG>, <STRONG>-G</STRONG>, <STRONG>-I</STRONG>, <STRONG>-N</STRONG>, <STRONG>-R</STRONG>, <STRONG>-T</STRONG>, <STRONG>-V</STRONG>, <STRONG>-a</STRONG>, <STRONG>-e</STRONG>, <STRONG>-f</STRONG>, <STRONG>-g</STRONG>,
|
|
- <STRONG>-o</STRONG>, <STRONG>-r</STRONG>, <STRONG>-s</STRONG>, <STRONG>-t</STRONG> and <STRONG>-x</STRONG> options are not supported under
|
|
+ The <STRONG>-0</STRONG>, <STRONG>-1</STRONG>, <STRONG>-C</STRONG>, <STRONG>-G</STRONG>, <STRONG>-I</STRONG>, <STRONG>-N</STRONG>, <STRONG>-R</STRONG>, <STRONG>-T</STRONG>, <STRONG>-V</STRONG>, <STRONG>-a</STRONG>, <STRONG>-e</STRONG>, <STRONG>-f</STRONG>, <STRONG>-g</STRONG>,
|
|
+ <STRONG>-o</STRONG>, <STRONG>-r</STRONG>, <STRONG>-s</STRONG>, <STRONG>-t</STRONG> and <STRONG>-x</STRONG> options are not supported under
|
|
SVr4. The SVr4 <STRONG>-c</STRONG> mode does not report bad use links.
|
|
|
|
- System V does not compile entries to or read entries from
|
|
- your <EM>$HOME/.terminfo</EM> database unless TERMINFO is explic-
|
|
+ System V does not compile entries to or read entries from
|
|
+ your <EM>$HOME/.terminfo</EM> database unless TERMINFO is explic-
|
|
itly set to it.
|
|
|
|
|
|
@@ -395,10 +398,10 @@
|
|
|
|
|
|
</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
|
|
- <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>, <STRONG><A HREF="captoinfo.1m.html">captoinfo(1m)</A></STRONG>, <STRONG><A HREF="infotocap.1m.html">infotocap(1m)</A></STRONG>, <STRONG><A HREF="toe.1m.html">toe(1m)</A></STRONG>,
|
|
+ <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>, <STRONG><A HREF="captoinfo.1m.html">captoinfo(1m)</A></STRONG>, <STRONG><A HREF="infotocap.1m.html">infotocap(1m)</A></STRONG>, <STRONG><A HREF="toe.1m.html">toe(1m)</A></STRONG>,
|
|
<STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="term.5.html">term(5)</A></STRONG>. <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>.
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
</PRE><H2><a name="h2-AUTHOR">AUTHOR</a></H2><PRE>
|
|
Index: doc/html/man/toe.1m.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/toe.1m.html 2016-09-10 22:14:42.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/toe.1m.html 2016-10-15 23:12:24.000000000 +0000
|
|
@@ -117,7 +117,7 @@
|
|
<STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG>, <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>, <STRONG><A HREF="captoinfo.1m.html">captoinfo(1m)</A></STRONG>, <STRONG><A HREF="infotocap.1m.html">infotocap(1m)</A></STRONG>,
|
|
<STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>.
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
|
|
Index: doc/html/man/tput.1.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/tput.1.html 2016-09-10 22:14:42.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/tput.1.html 2016-10-15 23:12:24.000000000 +0000
|
|
@@ -438,7 +438,7 @@
|
|
<STRONG><A HREF="clear.1.html">clear(1)</A></STRONG>, <STRONG>stty(1)</STRONG>, <STRONG><A HREF="tabs.1.html">tabs(1)</A></STRONG>, <STRONG><A HREF="tset.1.html">tset(1)</A></STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>,
|
|
<STRONG><A HREF="curs_termcap.3x.html">curs_termcap(3x)</A></STRONG>.
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
|
|
Index: doc/html/man/tset.1.html
|
|
--- ncurses-6.0-20161008+/doc/html/man/tset.1.html 2016-09-10 22:14:42.000000000 +0000
|
|
+++ ncurses-6.0-20161015/doc/html/man/tset.1.html 2016-10-15 23:12:24.000000000 +0000
|
|
@@ -387,7 +387,7 @@
|
|
<STRONG>csh(1)</STRONG>, <STRONG>sh(1)</STRONG>, <STRONG>stty(1)</STRONG>, <STRONG><A HREF="curs_terminfo.3x.html">curs_terminfo(3x)</A></STRONG>, <STRONG>tty(4)</STRONG>,
|
|
<STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>, <STRONG>ttys(5)</STRONG>, <STRONG>environ(7)</STRONG>
|
|
|
|
- This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20160910).
|
|
+ This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20161015).
|
|
|
|
|
|
|
|
Index: man/captoinfo.1m
|
|
Prereq: 1.25
|
|
--- ncurses-6.0-20161008+/man/captoinfo.1m 2010-12-04 18:36:44.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/captoinfo.1m 2016-10-15 17:26:09.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
'\" t
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2007,2010 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2010,2016 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 +27,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: captoinfo.1m,v 1.25 2010/12/04 18:36:44 tom Exp $
|
|
+.\" $Id: captoinfo.1m,v 1.26 2016/10/15 17:26:09 tom Exp $
|
|
.TH @CAPTOINFO@ 1M ""
|
|
.ds n 5
|
|
.ds d @TERMINFO@
|
|
@@ -152,7 +152,7 @@
|
|
.TE
|
|
.PP
|
|
If the single-line capabilities occur in an entry, they will automatically
|
|
-be composed into an \fIacsc\fR string.
|
|
+be composed into an \fBacsc\fR string.
|
|
The double-line capabilities and
|
|
\fBGG\fR are discarded with a warning message.
|
|
.PP
|
|
@@ -174,10 +174,10 @@
|
|
.TE
|
|
.PP
|
|
Additionally, the AIX \fIbox1\fR capability will be automatically translated to
|
|
-an \fIacsc\fR string.
|
|
+an \fBacsc\fR string.
|
|
.PP
|
|
Hewlett-Packard's terminfo library supports two nonstandard terminfo
|
|
-capabilities \fImeml\fR (memory lock) and \fImemu\fR (memory unlock).
|
|
+capabilities \fBmeml\fR (memory lock) and \fBmemu\fR (memory unlock).
|
|
These will be discarded with a warning message.
|
|
.SH NOTES
|
|
This utility is actually a link to \fB@TIC@\fR(1M), running in \fI\-I\fR mode.
|
|
Index: man/curs_attr.3x
|
|
Prereq: 1.47
|
|
--- ncurses-6.0-20161008+/man/curs_attr.3x 2016-07-23 23:48:49.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_attr.3x 2016-10-15 17:09:05.000000000 +0000
|
|
@@ -27,7 +27,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_attr.3x,v 1.47 2016/07/23 23:48:49 tom Exp $
|
|
+.\" $Id: curs_attr.3x,v 1.48 2016/10/15 17:09:05 tom Exp $
|
|
.TH curs_attr 3X ""
|
|
.de bP
|
|
.IP \(bu 4
|
|
@@ -285,12 +285,13 @@
|
|
(specifically, \fBA_ALTCHARSET\fR, \fBA_PROTECT\fR, and \fBA_INVIS\fR).
|
|
.PP
|
|
This implementation provides the \fBA_ITALIC\fP attribute for terminals
|
|
-which have the \fIenter_italics_mode\fP (sitm) and \fIexit_italics_mode\fP (ritm) capabilities.
|
|
+which have the \fBenter_italics_mode\fP (\fBsitm\fP)
|
|
+and \fBexit_italics_mode\fP (\fBritm\fP) capabilities.
|
|
Italics are not mentioned in X/Open Curses.
|
|
-Unlike the other video attributes, \fBI_ITALIC\fP is unrelated
|
|
-to the \fIset_attributes\fP capabilities.
|
|
+Unlike the other video attributes, \fBA_ITALIC\fP is unrelated
|
|
+to the \fBset_attributes\fP capabilities.
|
|
This implementation makes the assumption that
|
|
-\fIexit_attribute_mode\fP may also reset italics.
|
|
+\fBexit_attribute_mode\fP may also reset italics.
|
|
.PP
|
|
XSI Curses added the new entry points, \fBattr_get\fR, \fBattr_on\fR,
|
|
\fBattr_off\fR, \fBattr_set\fR, \fBwattr_on\fR, \fBwattr_off\fR,
|
|
Index: man/curs_clear.3x
|
|
Prereq: 1.14
|
|
--- ncurses-6.0-20161008+/man/curs_clear.3x 2010-12-04 18:36:44.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_clear.3x 2016-10-15 17:02:31.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2007,2010 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2010,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_clear.3x,v 1.14 2010/12/04 18:36:44 tom Exp $
|
|
+.\" $Id: curs_clear.3x,v 1.15 2016/10/15 17:02:31 tom Exp $
|
|
.TH curs_clear 3X ""
|
|
.na
|
|
.hy 0
|
|
@@ -101,7 +101,7 @@
|
|
.PP
|
|
This implementation, and others such as Solaris,
|
|
sets the current position to 0,0 after erasing
|
|
-via \fBwerase()\fP and \fBwclear()\fP.
|
|
+via \fBwerase\fP and \fBwclear\fP.
|
|
That fact is not documented in other implementations,
|
|
and may not be true of implementations
|
|
which were not derived from SVr4 source.
|
|
Index: man/curs_color.3x
|
|
Prereq: 1.43
|
|
--- ncurses-6.0-20161008+/man/curs_color.3x 2016-07-30 15:22:11.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_color.3x 2016-10-15 17:10:19.000000000 +0000
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_color.3x,v 1.43 2016/07/30 15:22:11 tom Exp $
|
|
+.\" $Id: curs_color.3x,v 1.45 2016/10/15 17:10:19 tom Exp $
|
|
.TH curs_color 3X ""
|
|
.ie \n(.g .ds `` \(lq
|
|
.el .ds `` ``
|
|
@@ -295,7 +295,7 @@
|
|
\fBCOLOR_WHITE\fR
|
|
.fi
|
|
.SH RETURN VALUE
|
|
-The routines \fBcan_change_color()\fR and \fBhas_colors()\fR return \fBTRUE\fR
|
|
+The routines \fBcan_change_color\fR and \fBhas_colors\fR return \fBTRUE\fR
|
|
or \fBFALSE\fR.
|
|
.PP
|
|
All other routines return the integer \fBERR\fR upon failure and an \fBOK\fR
|
|
@@ -316,7 +316,7 @@
|
|
.TP 5
|
|
\fBinit_color\fP
|
|
returns an error if the terminal does not support
|
|
-this feature, e.g., if the \fIinitialize_color\fP capability is absent
|
|
+this feature, e.g., if the \fBinitialize_color\fP capability is absent
|
|
from the terminal description.
|
|
.TP 5
|
|
\fBstart_color\fP
|
|
Index: man/curs_extend.3x
|
|
Prereq: 1.20
|
|
--- ncurses-6.0-20161008+/man/curs_extend.3x 2016-05-14 23:10:54.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_extend.3x 2016-10-15 16:52:48.000000000 +0000
|
|
@@ -28,7 +28,7 @@
|
|
.\"
|
|
.\" Author: Thomas E. Dickey 1999-on
|
|
.\"
|
|
-.\" $Id: curs_extend.3x,v 1.20 2016/05/14 23:10:54 tom Exp $
|
|
+.\" $Id: curs_extend.3x,v 1.21 2016/10/15 16:52:48 tom Exp $
|
|
.TH curs_extend 3X ""
|
|
.SH NAME
|
|
\fBcurses_version\fP,
|
|
@@ -45,14 +45,12 @@
|
|
which do not fit easily into other categories.
|
|
.SS curses_version
|
|
.PP
|
|
-Use
|
|
-.I curses_version()
|
|
+Use \fBcurses_version\fP
|
|
to get the version number, including patch level of the library, e.g.,
|
|
.B 5.0.19991023
|
|
.SS use_extended_names
|
|
.PP
|
|
-The
|
|
-.I use_extended_names()
|
|
+The \fBuse_extended_names\fP
|
|
function controls whether the calling application
|
|
is able to use user-defined or nonstandard names
|
|
which may be compiled into the terminfo
|
|
Index: man/curs_getch.3x
|
|
Prereq: 1.48
|
|
--- ncurses-6.0-20161008+/man/curs_getch.3x 2016-09-10 21:56:25.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_getch.3x 2016-10-15 16:44:01.000000000 +0000
|
|
@@ -27,7 +27,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_getch.3x,v 1.48 2016/09/10 21:56:25 Leon.Winter Exp $
|
|
+.\" $Id: curs_getch.3x,v 1.49 2016/10/15 16:44:01 tom Exp $
|
|
.TH curs_getch 3X ""
|
|
.na
|
|
.hy 0
|
|
@@ -289,7 +289,7 @@
|
|
.PP
|
|
.SH RETURN VALUE
|
|
All routines return the integer \fBERR\fR upon failure and an integer value
|
|
-other than \fBERR\fR (\fBOK\fR in the case of ungetch()) upon successful
|
|
+other than \fBERR\fR (\fBOK\fR in the case of \fBungetch\fP) upon successful
|
|
completion.
|
|
.RS 3
|
|
.TP 5
|
|
Index: man/curs_initscr.3x
|
|
Prereq: 1.24
|
|
--- ncurses-6.0-20161008+/man/curs_initscr.3x 2015-07-21 23:01:38.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_initscr.3x 2016-10-15 17:02:31.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2014,2015 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_initscr.3x,v 1.24 2015/07/21 23:01:38 tom Exp $
|
|
+.\" $Id: curs_initscr.3x,v 1.25 2016/10/15 17:02:31 tom Exp $
|
|
.TH curs_initscr 3X ""
|
|
.de bP
|
|
.IP \(bu 4
|
|
@@ -189,7 +189,7 @@
|
|
.PP
|
|
\fICurses implementations may provide for special handling of the SIGINT,
|
|
SIGQUIT and SIGTSTP signals if their disposition is SIG_DFL at the time
|
|
-\fBinitscr()\fP is called \fP...
|
|
+\fBinitscr\fP is called \fP...
|
|
.PP
|
|
\fIAny special handling for these signals may remain in effect for the
|
|
life of the process or until the process changes the disposition of
|
|
Index: man/curs_inopts.3x
|
|
Prereq: 1.20
|
|
--- ncurses-6.0-20161008+/man/curs_inopts.3x 2015-11-28 19:03:12.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_inopts.3x 2016-10-15 17:13:45.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2013,2015 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_inopts.3x,v 1.20 2015/11/28 19:03:12 Benno.Schulenberg Exp $
|
|
+.\" $Id: curs_inopts.3x,v 1.22 2016/10/15 17:13:45 tom Exp $
|
|
.TH curs_inopts 3X ""
|
|
.ie \n(.g .ds `` \(lq
|
|
.el .ds `` ``
|
|
@@ -229,7 +229,7 @@
|
|
When
|
|
\fBqiflush\fR is called, the queues will be flushed when these control
|
|
characters are read.
|
|
-You may want to call \fBnoqiflush()\fR in a signal
|
|
+You may want to call \fBnoqiflush\fR in a signal
|
|
handler if you want output to continue as though the interrupt
|
|
had not occurred, after the handler exits.
|
|
.\"
|
|
@@ -308,7 +308,7 @@
|
|
On the other hand, an application can use \fBdefine_key\fP to establish
|
|
a specific keycode for a given string.
|
|
This makes it possible for an application to check for an extended
|
|
-capability's presence with \fItigetstr\fP,
|
|
+capability's presence with \fBtigetstr\fP,
|
|
and reassign the keycode to match its own needs.
|
|
.PP
|
|
Low-level applications can use \fBtigetstr\fP to obtain the definition
|
|
Index: man/curs_kernel.3x
|
|
Prereq: 1.20
|
|
--- ncurses-6.0-20161008+/man/curs_kernel.3x 2015-07-21 01:10:11.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_kernel.3x 2016-10-15 16:42:55.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_kernel.3x,v 1.20 2015/07/21 01:10:11 tom Exp $
|
|
+.\" $Id: curs_kernel.3x,v 1.21 2016/10/15 16:42:55 tom Exp $
|
|
.de bP
|
|
.IP \(bu 4
|
|
..
|
|
@@ -83,7 +83,7 @@
|
|
(not in \fBcurses\fR) state for use by the \fBreset_prog_mode\fR and
|
|
\fBreset_shell_mode\fR routines. This is done automatically by
|
|
\fBinitscr\fR. There is one such save area for each screen context
|
|
-allocated by \fBnewterm()\fR.
|
|
+allocated by \fBnewterm\fR.
|
|
.SS reset_prog_mode, reset_shell_mode
|
|
.PP
|
|
The \fBreset_prog_mode\fR and \fBreset_shell_mode\fR routines restore
|
|
Index: man/curs_outopts.3x
|
|
Prereq: 1.26
|
|
--- ncurses-6.0-20161008+/man/curs_outopts.3x 2015-07-21 00:23:43.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_outopts.3x 2016-10-15 17:02:31.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_outopts.3x,v 1.26 2015/07/21 00:23:43 tom Exp $
|
|
+.\" $Id: curs_outopts.3x,v 1.27 2016/10/15 17:02:31 tom Exp $
|
|
.TH curs_outopts 3X ""
|
|
.na
|
|
.hy 0
|
|
@@ -189,8 +189,8 @@
|
|
.SH PORTABILITY
|
|
These functions are described in the XSI Curses standard, Issue 4.
|
|
.PP
|
|
-The XSI Curses standard is ambiguous on the question of whether \fBraw\fR()
|
|
-should disable the CRLF translations controlled by \fBnl\fR() and \fBnonl\fR().
|
|
+The XSI Curses standard is ambiguous on the question of whether \fBraw\fR
|
|
+should disable the CRLF translations controlled by \fBnl\fR and \fBnonl\fR.
|
|
BSD curses did turn off these translations; AT&T curses (at least as late as
|
|
SVr1) did not.
|
|
We choose to do so, on the theory that a programmer requesting
|
|
Index: man/curs_refresh.3x
|
|
Prereq: 1.16
|
|
--- ncurses-6.0-20161008+/man/curs_refresh.3x 2016-01-30 15:52:36.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_refresh.3x 2016-10-15 16:45:45.000000000 +0000
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_refresh.3x,v 1.16 2016/01/30 15:52:36 tom Exp $
|
|
+.\" $Id: curs_refresh.3x,v 1.17 2016/10/15 16:45:45 tom Exp $
|
|
.TH curs_refresh 3X ""
|
|
.na
|
|
.hy 0
|
|
@@ -105,7 +105,7 @@
|
|
The \fBwredrawln\fR routine indicates to \fBcurses\fR that some screen lines
|
|
are corrupted and should be thrown away before anything is written over them.
|
|
It touches the indicated lines (marking them changed).
|
|
-The routine \fBredrawwin\fR() touches the entire window.
|
|
+The routine \fBredrawwin\fR touches the entire window.
|
|
.SH RETURN VALUE
|
|
Routines that return an integer return \fBERR\fR upon failure, and \fBOK\fR
|
|
(SVr4 only specifies "an integer value other than \fBERR\fR") upon successful
|
|
@@ -129,14 +129,14 @@
|
|
.SH PORTABILITY
|
|
The XSI Curses standard, Issue 4 describes these functions.
|
|
.PP
|
|
-Whether \fBwnoutrefresh()\fR copies to the virtual screen the entire contents
|
|
+Whether \fBwnoutrefresh\fR copies to the virtual screen the entire contents
|
|
of a window or just its changed portions has never been well-documented in
|
|
historic curses versions (including SVr4).
|
|
It might be unwise to rely on
|
|
either behavior in programs that might have to be linked with other curses
|
|
implementations.
|
|
-Instead, you can do an explicit \fBtouchwin()\fR before the
|
|
-\fBwnoutrefresh()\fR call to guarantee an entire-contents copy anywhere.
|
|
+Instead, you can do an explicit \fBtouchwin\fR before the
|
|
+\fBwnoutrefresh\fR call to guarantee an entire-contents copy anywhere.
|
|
.SH SEE ALSO
|
|
\fBcurses\fR(3X),
|
|
\fBcurs_outopts\fR(3X)
|
|
Index: man/curs_slk.3x
|
|
Prereq: 1.22
|
|
--- ncurses-6.0-20161008+/man/curs_slk.3x 2010-12-04 18:38:55.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_slk.3x 2016-10-15 17:02:31.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2007,2010 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2010,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_slk.3x,v 1.22 2010/12/04 18:38:55 tom Exp $
|
|
+.\" $Id: curs_slk.3x,v 1.23 2016/10/15 17:02:31 tom Exp $
|
|
.TH curs_slk 3X ""
|
|
.na
|
|
.hy 0
|
|
@@ -232,7 +232,7 @@
|
|
argument type of the attribute-manipulation functions \fBslk_attron\fR,
|
|
\fBslk_attroff\fR, \fBslk_attrset\fR to be \fBattr_t\fR, and adds \fBconst\fR
|
|
qualifiers.
|
|
-The format codes \fB2\fR and \fB3\fR for \fBslk_init()\fR and the
|
|
+The format codes \fB2\fR and \fB3\fR for \fBslk_init\fR and the
|
|
function \fBslk_attr\fR are specific to ncurses.
|
|
.SH SEE ALSO
|
|
\fBcurses\fR(3X),
|
|
Index: man/curs_terminfo.3x
|
|
Prereq: 1.44
|
|
--- ncurses-6.0-20161008+/man/curs_terminfo.3x 2016-08-20 23:26:10.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_terminfo.3x 2016-10-15 17:27:48.000000000 +0000
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_terminfo.3x,v 1.44 2016/08/20 23:26:10 tom Exp $
|
|
+.\" $Id: curs_terminfo.3x,v 1.46 2016/10/15 17:27:48 tom Exp $
|
|
.TH curs_terminfo 3X ""
|
|
.ie \n(.g .ds `` \(lq
|
|
.el .ds `` ``
|
|
@@ -172,7 +172,7 @@
|
|
means that the terminal is hardcopy, cannot be used for curses applications.
|
|
.IP
|
|
\fBsetupterm\fP determines if the entry is a hardcopy type by
|
|
-checking the \fIhc\fP (\fIhardcopy\fP) capability.
|
|
+checking the \fBhc\fP (\fBhardcopy\fP) capability.
|
|
.TP 5
|
|
.B 0
|
|
means that the terminal could not be found,
|
|
@@ -180,7 +180,7 @@
|
|
having too little information for curses applications to run.
|
|
.IP
|
|
\fBsetupterm\fP determines if the entry is a generic type by
|
|
-checking the \fIgn\fP (\fIgeneric\fP) capability.
|
|
+checking the \fBgn\fP (\fBgeneric\fP) capability.
|
|
.TP 5
|
|
.B \-1
|
|
means that the \fBterminfo\fR database could not be found.
|
|
@@ -249,10 +249,16 @@
|
|
.SS Output Functions
|
|
.PP
|
|
The \fBtputs\fR routine applies padding information to the string
|
|
-\fIstr\fR and outputs it. The \fIstr\fR must be a terminfo string
|
|
+\fIstr\fR and outputs it:
|
|
+.bP
|
|
+The \fIstr\fR must be a terminfo string
|
|
variable or the return value from \fBtparm\fR, \fBtgetstr\fR, or
|
|
-\fBtgoto\fR. \fIaffcnt\fR is the number of lines affected, or 1 if
|
|
-not applicable. \fIputc\fR is a \fBputchar\fR-like routine to which
|
|
+\fBtgoto\fR.
|
|
+.bP
|
|
+\fIaffcnt\fR is the number of lines affected, or 1 if
|
|
+not applicable.
|
|
+.bP
|
|
+\fIputc\fR is a \fBputchar\fR-like routine to which
|
|
the characters are passed, one at a time.
|
|
.PP
|
|
The \fBputp\fR routine calls \fBtputs(\fR\fIstr\fR\fB, 1, putchar)\fR.
|
|
Index: man/curs_trace.3x
|
|
Prereq: 1.13
|
|
--- ncurses-6.0-20161008+/man/curs_trace.3x 2015-07-20 22:54:44.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_trace.3x 2016-10-15 17:26:09.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 2000-2010,2015 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 2000-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_trace.3x,v 1.13 2015/07/20 22:54:44 tom Exp $
|
|
+.\" $Id: curs_trace.3x,v 1.14 2016/10/15 17:26:09 tom Exp $
|
|
.de bP
|
|
.IP \(bu 4
|
|
..
|
|
@@ -102,7 +102,7 @@
|
|
trace user and system times of updates.
|
|
.TP 5
|
|
.B TRACE_TPUTS
|
|
-trace tputs calls.
|
|
+trace \fBtputs\fP calls.
|
|
.TP 5
|
|
.B TRACE_UPDATE
|
|
trace update actions, old & new screens.
|
|
Index: man/curs_window.3x
|
|
Prereq: 1.19
|
|
--- ncurses-6.0-20161008+/man/curs_window.3x 2015-07-21 08:25:23.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/curs_window.3x 2016-10-15 17:26:09.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2014,2015 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: curs_window.3x,v 1.19 2015/07/21 08:25:23 tom Exp $
|
|
+.\" $Id: curs_window.3x,v 1.20 2016/10/15 17:26:09 tom Exp $
|
|
.TH curs_window 3X ""
|
|
.na
|
|
.hy 0
|
|
@@ -215,7 +215,7 @@
|
|
.PP
|
|
Note that \fBsyncok\fR may be a macro.
|
|
.SH BUGS
|
|
-The subwindow functions (\fIsubwin\fR, \fIderwin\fR, \fImvderwin\fR,
|
|
+The subwindow functions (\fBsubwin\fR, \fBderwin\fR, \fBmvderwin\fR,
|
|
\fBwsyncup\fR, \fBwsyncdown\fR, \fBwcursyncup\fR, \fBsyncok\fR) are flaky,
|
|
incompletely implemented, and not well tested.
|
|
.PP
|
|
Index: man/default_colors.3x
|
|
Prereq: 1.23
|
|
--- ncurses-6.0-20161008+/man/default_colors.3x 2011-01-03 21:52:27.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/default_colors.3x 2016-10-15 17:16:48.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2010,2011 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2011,2016 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 *
|
|
@@ -28,7 +28,7 @@
|
|
.\"
|
|
.\" Author: Thomas E. Dickey 1997,1999,2000,2005
|
|
.\"
|
|
-.\" $Id: default_colors.3x,v 1.23 2011/01/03 21:52:27 Tim.van.der.Molen Exp $
|
|
+.\" $Id: default_colors.3x,v 1.25 2016/10/15 17:16:48 tom Exp $
|
|
.TH default_colors 3X ""
|
|
.SH NAME
|
|
\fBuse_default_colors\fR,
|
|
@@ -40,10 +40,7 @@
|
|
.br
|
|
\fBint assume_default_colors(int fg, int bg);\fP
|
|
.SH DESCRIPTION
|
|
-The
|
|
-.I use_default_colors()
|
|
-and
|
|
-.I assume_default_colors()
|
|
+The \fBuse_default_colors\fP and \fBassume_default_colors\fP
|
|
functions are extensions to the curses library.
|
|
They are used with terminals that support ISO 6429 color, or equivalent.
|
|
These terminals allow the application to reset color to an unspecified
|
|
@@ -56,20 +53,18 @@
|
|
For example, there are several implementations of the \fBls\fP program
|
|
which use colors to denote different file types or permissions.
|
|
These "color ls" programs do not necessarily modify the background color,
|
|
-typically using only the \fIsetaf\fP terminfo capability to set the
|
|
+typically using only the \fBsetaf\fP terminfo capability to set the
|
|
foreground color.
|
|
Full-screen applications that use default colors can achieve similar
|
|
visual effects.
|
|
.PP
|
|
-The first function,
|
|
-.I use_default_colors()
|
|
+The first function, \fBuse_default_colors\fP
|
|
tells the curses library to assign terminal default
|
|
foreground/background colors to color number \-1. So init_pair(x,COLOR_RED,\-1)
|
|
will initialize pair x as red on default background and init_pair(x,\-1,COLOR_BLUE) will
|
|
initialize pair x as default foreground on blue.
|
|
.PP
|
|
-The other,
|
|
-.I assume_default_colors()
|
|
+The other, \fBassume_default_colors\fP
|
|
is a refinement which tells which colors to paint for color pair 0.
|
|
This function recognizes a special color number \-1,
|
|
which denotes the default terminal color.
|
|
@@ -85,29 +80,29 @@
|
|
These are ncurses extensions.
|
|
For other curses implementations, color
|
|
number \-1 does not mean anything, just as for ncurses before a
|
|
-successful call of \fIuse_default_colors()\fP or \fIassume_default_colors()\fP.
|
|
+successful call of \fBuse_default_colors\fP or \fBassume_default_colors\fP.
|
|
.PP
|
|
Other curses implementations do not allow an application to modify color pair 0.
|
|
They assume that the background is COLOR_BLACK,
|
|
but do not ensure that the color pair 0 is painted to match the
|
|
assumption.
|
|
If your application does not use either
|
|
-.I use_default_colors()
|
|
+.B use_default_colors
|
|
or
|
|
-.I assume_default_colors()
|
|
+.B assume_default_colors
|
|
ncurses will paint a white foreground (text) with black background
|
|
for color pair 0.
|
|
.SH RETURN VALUE
|
|
These functions return the integer \fBERR\fP upon failure and \fBOK\fP on success.
|
|
They will fail if either the terminal does not support
|
|
-the \fIorig_pair\fP or \fIorig_colors\fP capability.
|
|
-If the \fIinitialize_pair\fP capability is not found, this causes an
|
|
+the \fBorig_pair\fP or \fBorig_colors\fP capability.
|
|
+If the \fBinitialize_pair\fP capability is not found, this causes an
|
|
error as well.
|
|
.SH NOTES
|
|
Associated with this extension, the \fBinit_pair\fR function accepts
|
|
negative arguments to specify default foreground or background colors.
|
|
.PP
|
|
-The \fIuse_default_colors()\fP function was added to support \fIded\fP.
|
|
+The \fBuse_default_colors\fP function was added to support \fIded\fP.
|
|
This is a full-screen application which uses curses to manage only part
|
|
of the screen. The bottom portion of the screen, which is of adjustable
|
|
size, is left uncolored to display the results from shell commands.
|
|
@@ -120,9 +115,9 @@
|
|
which does not necessarily correspond to any of the ANSI colors.
|
|
While a special terminfo entry could be constructed using nine colors,
|
|
there was no mechanism provided within curses to account for the related
|
|
-\fIorig_pair\fP and \fIback_color_erase\fP capabilities.
|
|
+\fBorig_pair\fP and \fBback_color_erase\fP capabilities.
|
|
.PP
|
|
-The \fIassume_default_colors()\fP function was added to solve
|
|
+The \fBassume_default_colors\fP function was added to solve
|
|
a different problem: support for applications which would use
|
|
environment variables and other configuration to bypass curses'
|
|
notion of the terminal's default colors, setting specific values.
|
|
Index: man/infotocap.1m
|
|
Prereq: 1.11
|
|
--- ncurses-6.0-20161008+/man/infotocap.1m 2010-12-04 18:38:55.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/infotocap.1m 2016-10-15 17:26:09.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
'\" t
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1999-2006,2010 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1999-2010,2016 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 +27,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: infotocap.1m,v 1.11 2010/12/04 18:38:55 tom Exp $
|
|
+.\" $Id: infotocap.1m,v 1.12 2016/10/15 17:26:09 tom Exp $
|
|
.TH @INFOTOCAP@ 1M ""
|
|
.ds n 5
|
|
.ds d @TERMINFO@
|
|
@@ -61,8 +61,8 @@
|
|
\*d
|
|
Compiled terminal description database.
|
|
.SH NOTES
|
|
-This utility is actually a link to \fI@TIC@\fR, running in \fI\-C\fR mode.
|
|
-You can use other \fI@TIC@\fR options such as \fB\-f\fR and \fB\-x\fR.
|
|
+This utility is actually a link to \fB@TIC@\fR, running in \fI\-C\fR mode.
|
|
+You can use other \fB@TIC@\fR options such as \fB\-f\fR and \fB\-x\fR.
|
|
.SH SEE ALSO
|
|
\fBcurses\fR(3X),
|
|
\fB@TIC@\fR(1M),
|
|
Index: man/legacy_coding.3x
|
|
Prereq: 1.4
|
|
--- ncurses-6.0-20161008+/man/legacy_coding.3x 2010-12-04 18:49:20.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/legacy_coding.3x 2016-10-15 17:02:31.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 2005-2006,2010 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 2005-2010,2016 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 *
|
|
@@ -28,7 +28,7 @@
|
|
.\"
|
|
.\" Author: Thomas E. Dickey
|
|
.\"
|
|
-.\" $Id: legacy_coding.3x,v 1.4 2010/12/04 18:49:20 tom Exp $
|
|
+.\" $Id: legacy_coding.3x,v 1.5 2016/10/15 17:02:31 tom Exp $
|
|
.TH legacy_coding 3X ""
|
|
.SH NAME
|
|
\fBuse_legacy_coding\fR \- use terminal's default colors
|
|
@@ -37,9 +37,7 @@
|
|
.sp
|
|
\fBint use_legacy_coding(int level);\fP
|
|
.SH DESCRIPTION
|
|
-The
|
|
-.I use_legacy_coding()
|
|
-function is an extension to the curses library.
|
|
+The \fBuse_legacy_coding\fP function is an extension to the curses library.
|
|
It allows the caller to change the result of \fBunctrl\fP,
|
|
and suppress related checks within the library that would normally
|
|
cause nonprinting characters to be rendered in visible form.
|
|
Index: man/menu_format.3x
|
|
Prereq: 1.13
|
|
--- ncurses-6.0-20161008+/man/menu_format.3x 2015-12-05 23:01:16.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/menu_format.3x 2016-10-15 17:02:31.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
'\" t
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2015,2016 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 +27,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: menu_format.3x,v 1.13 2015/12/05 23:01:16 tom Exp $
|
|
+.\" $Id: menu_format.3x,v 1.14 2016/10/15 17:02:31 tom Exp $
|
|
.TH menu_format 3X ""
|
|
.SH NAME
|
|
\fBset_menu_format\fP,
|
|
@@ -43,7 +43,7 @@
|
|
The function \fBset_menu_format\fR sets the maximum display size of the given
|
|
menu. If this size is too small to display all menu items, the menu will be
|
|
made scrollable. If this size is larger than the menus subwindow and the
|
|
-subwindow is too small to display all menu items, \fBpost_menu()\fR will fail.
|
|
+subwindow is too small to display all menu items, \fBpost_menu\fR will fail.
|
|
.PP
|
|
The default format is 16 rows, 1 column. Calling \fBset_menu_format\fR with a
|
|
null menu pointer will change this default. A zero row or column argument to
|
|
Index: man/menu_post.3x
|
|
Prereq: 1.12
|
|
--- ncurses-6.0-20161008+/man/menu_post.3x 2015-12-05 23:42:45.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/menu_post.3x 2016-10-15 17:02:31.000000000 +0000
|
|
@@ -1,6 +1,6 @@
|
|
'\" t
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2015,2016 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 +27,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: menu_post.3x,v 1.12 2015/12/05 23:42:45 tom Exp $
|
|
+.\" $Id: menu_post.3x,v 1.13 2016/10/15 17:02:31 tom Exp $
|
|
.TH menu_post 3X ""
|
|
.SH NAME
|
|
\fBpost_menu\fR,
|
|
@@ -65,8 +65,8 @@
|
|
Routine was called from an initialization or termination function.
|
|
.TP 5
|
|
.B E_NO_ROOM
|
|
-Menu is too large for its window. You should consider to use
|
|
-\fBset_menu_format()\fR to solve the problem.
|
|
+Menu is too large for its window.
|
|
+You should consider using \fBset_menu_format\fR to solve the problem.
|
|
.TP 5
|
|
.B E_NOT_POSTED
|
|
The menu has not been posted.
|
|
Index: man/panel.3x
|
|
Prereq: 1.19
|
|
--- ncurses-6.0-20161008+/man/panel.3x 2015-12-05 23:42:45.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/panel.3x 2016-10-15 17:02:31.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: panel.3x,v 1.19 2015/12/05 23:42:45 tom Exp $
|
|
+.\" $Id: panel.3x,v 1.20 2016/10/15 17:02:31 tom Exp $
|
|
.TH panel 3X ""
|
|
.ds n 5
|
|
.ds d @TERMINFO@
|
|
@@ -90,14 +90,14 @@
|
|
to be displayed above any other panel) and returns a
|
|
pointer to the new panel.
|
|
.TP
|
|
-.B update_panels()
|
|
+.B update_panels
|
|
refreshes the virtual screen to reflect the relations between the
|
|
-panels in the stack, but does not call doupdate() to refresh the
|
|
+panels in the stack, but does not call \fBdoupdate\fP to refresh the
|
|
physical screen.
|
|
Use this function and not \fBwrefresh\fP or \fBwnoutrefresh\fP.
|
|
.B update_panels
|
|
may be called more than once before a call to
|
|
-doupdate(), but doupdate() is the function responsible for updating
|
|
+\fBdoupdate\fP, but \fBdoupdate\fP is the function responsible for updating
|
|
the physical screen.
|
|
.TP
|
|
.B del_panel(pan)
|
|
@@ -127,7 +127,7 @@
|
|
.B move_panel(pan,starty,startx)
|
|
moves the given panel window so that its upper-left corner is at
|
|
\fBstarty\fR, \fBstartx\fR. It does not change the position of the
|
|
-panel in the stack. Be sure to use this function, not \fBmvwin()\fR,
|
|
+panel in the stack. Be sure to use this function, not \fBmvwin\fR,
|
|
to move a panel window.
|
|
.TP
|
|
.B replace_panel(pan,window)
|
|
@@ -163,11 +163,11 @@
|
|
The \fBPANEL\fR data structures are merely similar. The programmer
|
|
is cautioned not to directly use \fBPANEL\fR fields.
|
|
.P
|
|
-The functions \fBshow_panel()\fR and \fBtop_panel()\fR are identical
|
|
+The functions \fBshow_panel\fR and \fBtop_panel\fR are identical
|
|
in this implementation, and work equally well with displayed or hidden
|
|
-panels. In the native System V implementation, \fBshow_panel()\fR is
|
|
+panels. In the native System V implementation, \fBshow_panel\fR is
|
|
intended for making a hidden panel visible (at the top of the stack)
|
|
-and \fBtop_panel()\fR is intended for making an already-visible panel
|
|
+and \fBtop_panel\fR is intended for making an already-visible panel
|
|
move to the top of the stack. You are cautioned to use the correct
|
|
function to ensure compatibility with native panel libraries.
|
|
.SH NOTE
|
|
Index: man/tabs.1
|
|
Prereq: 1.12
|
|
--- ncurses-6.0-20161008+/man/tabs.1 2016-04-02 23:40:46.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/tabs.1 2016-10-15 16:16:38.000000000 +0000
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: tabs.1,v 1.12 2016/04/02 23:40:46 tom Exp $
|
|
+.\" $Id: tabs.1,v 1.13 2016/10/15 16:16:38 tom Exp $
|
|
.TH @TABS@ 1 ""
|
|
.ds n 5
|
|
.de bP
|
|
@@ -133,7 +133,7 @@
|
|
Very few of the entries in the terminal database provide this capability.
|
|
.bP
|
|
There is no counterpart in X/Open Curses Issue 7 for this utility,
|
|
-unlike @TPUT@(3X).
|
|
+unlike @TPUT@(1).
|
|
.PP
|
|
The \fB\-d\fP (debug) and \fB\-n\fP (no-op) options are extensions not provided
|
|
by other implementations.
|
|
Index: man/term.5
|
|
Prereq: 1.22
|
|
--- ncurses-6.0-20161008+/man/term.5 2015-04-26 14:50:23.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/term.5 2016-10-15 17:02:31.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2015,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: term.5,v 1.22 2015/04/26 14:50:23 tom Exp $
|
|
+.\" $Id: term.5,v 1.23 2016/10/15 17:02:31 tom Exp $
|
|
.TH term 5
|
|
.ds n 5
|
|
.ds d @TERMINFO@
|
|
@@ -76,7 +76,7 @@
|
|
The compiled file is created with the
|
|
.B @TIC@
|
|
program, and read by the routine
|
|
-.IR setupterm .
|
|
+.BR setupterm .
|
|
The file is divided into six parts:
|
|
the header,
|
|
terminal names,
|
|
@@ -197,18 +197,18 @@
|
|
.
|
|
.SH PORTABILITY
|
|
Note that it is possible for
|
|
-.I setupterm
|
|
+.B setupterm
|
|
to expect a different set of capabilities
|
|
than are actually present in the file.
|
|
Either the database may have been updated since
|
|
-.I setupterm
|
|
+.B setupterm
|
|
has been recompiled
|
|
(resulting in extra unrecognized entries in the file)
|
|
or the program may have been recompiled more recently
|
|
than the database was updated
|
|
(resulting in missing entries).
|
|
The routine
|
|
-.I setupterm
|
|
+.B setupterm
|
|
must be prepared for both possibilities \-
|
|
this is why the numbers and sizes are included.
|
|
Also, new capabilities must always be added at the end of the lists
|
|
Index: man/terminfo.head
|
|
Prereq: 1.21
|
|
--- ncurses-6.0-20161008+/man/terminfo.head 2013-03-09 22:11:36.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/terminfo.head 2016-10-15 17:02:31.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
.\"***************************************************************************
|
|
-.\" Copyright (c) 1998-2012,2013 Free Software Foundation, Inc. *
|
|
+.\" Copyright (c) 1998-2013,2016 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 *
|
|
@@ -26,7 +26,7 @@
|
|
.\" authorization. *
|
|
.\"***************************************************************************
|
|
.\"
|
|
-.\" $Id: terminfo.head,v 1.21 2013/03/09 22:11:36 tom Exp $
|
|
+.\" $Id: terminfo.head,v 1.22 2016/10/15 17:02:31 tom Exp $
|
|
.TH terminfo 5 "" "" "File Formats"
|
|
.ds n 5
|
|
.ds d @TERMINFO@
|
|
Index: man/terminfo.tail
|
|
Prereq: 1.69
|
|
--- ncurses-6.0-20161008+/man/terminfo.tail 2015-04-26 14:47:23.000000000 +0000
|
|
+++ ncurses-6.0-20161015/man/terminfo.tail 2016-10-15 18:34:58.000000000 +0000
|
|
@@ -1,4 +1,4 @@
|
|
-.\" $Id: terminfo.tail,v 1.69 2015/04/26 14:47:23 tom Exp $
|
|
+.\" $Id: terminfo.tail,v 1.72 2016/10/15 18:34:58 tom Exp $
|
|
.\" Beginning of terminfo.tail file
|
|
.\" This file is part of ncurses.
|
|
.\" See "terminfo.head" for copyright.
|
|
@@ -156,20 +156,23 @@
|
|
Finally, characters may be given as three octal digits after a \fB\e\fR.
|
|
.PP
|
|
A delay in milliseconds may appear anywhere in a string capability, enclosed in
|
|
-$<..> brackets, as in \fBel\fP=\eEK$<5>, and padding characters are supplied by
|
|
-.I tputs
|
|
+$<..> brackets, as in \fBel\fP=\eEK$<5>,
|
|
+and padding characters are supplied by \fBtputs\fP
|
|
to provide this delay.
|
|
+.bP
|
|
The delay must be a number with at most one decimal
|
|
place of precision; it may be followed by suffixes \*(``*\*('' or \*(``/\*('' or both.
|
|
+.bP
|
|
A \*(``*\*(''
|
|
indicates that the padding required is proportional to the number of lines
|
|
affected by the operation, and the amount given is the per-affected-unit
|
|
padding required.
|
|
(In the case of insert character, the factor is still the
|
|
-number of
|
|
-.IR lines
|
|
-affected.) Normally, padding is advisory if the device has the \fBxon\fR
|
|
+number of \fIlines\fP affected.)
|
|
+.IP
|
|
+Normally, padding is advisory if the device has the \fBxon\fR
|
|
capability; it is used for cost computation but does not trigger delays.
|
|
+.bP
|
|
A \*(``/\*(''
|
|
suffix indicates that the padding is mandatory and forces a delay of the given
|
|
number of milliseconds even on devices for which \fBxon\fR is present to
|
|
@@ -409,16 +412,16 @@
|
|
avoiding interpreting "%\-" as an operator.
|
|
.TP
|
|
\f(CW%c\fP
|
|
-print pop() like %c in \fBprintf\fP
|
|
+print \fIpop()\fP like %c in \fBprintf\fP
|
|
.TP
|
|
\fB%s\fP
|
|
-print pop() like %s in \fBprintf\fP
|
|
+print \fIpop()\fP like %s in \fBprintf\fP
|
|
.TP
|
|
\fB%p\fP\fI[1\-9]\fP
|
|
push \fIi\fP'th parameter
|
|
.TP
|
|
\fB%P\fP\fI[a\-z]\fP
|
|
-set dynamic variable \fI[a\-z]\fP to pop()
|
|
+set dynamic variable \fI[a\-z]\fP to \fIpop()\fP
|
|
.TP
|
|
\fB%g\fP\fI[a\-z]/\fP
|
|
get dynamic variable \fI[a\-z]\fP and push it
|
|
@@ -445,7 +448,7 @@
|
|
push strlen(pop)
|
|
.TP
|
|
\fB%+\fP, \fB%\-\fP, \fB%*\fP, \fB%/\fP, \fB%m\fP
|
|
-arithmetic (%m is mod): \fIpush(pop() op pop())\fP
|
|
+arithmetic (%m is \fImod\fP): \fIpush(pop() op pop())\fP
|
|
.TP
|
|
\fB%&\fP, \fB%|\fP, \fB%^\fP
|
|
bit operations (AND, OR and exclusive-OR): \fIpush(pop() op pop())\fP
|
|
@@ -457,7 +460,7 @@
|
|
logical AND and OR operations (for conditionals)
|
|
.TP
|
|
\fB%!\fP, \fB%~\fP
|
|
-unary operations (logical and bit complement): push(op pop())
|
|
+unary operations (logical and bit complement): \fIpush(op pop())\fP
|
|
.TP
|
|
\fB%i\fP
|
|
add 1 to first two parameters (for ANSI terminals)
|
|
@@ -1156,9 +1159,8 @@
|
|
and
|
|
.BR is3
|
|
respectively.
|
|
-These strings are output by the
|
|
-.IR reset
|
|
-program, which is used when the terminal gets into a wedged state.
|
|
+These strings are output by the \fB@RESET@\fP program,
|
|
+which is used when the terminal gets into a wedged state.
|
|
Commands are normally placed in
|
|
.BR rs1 ,
|
|
.BR rs2
|
|
@@ -1173,10 +1175,7 @@
|
|
but it causes an annoying glitch of the screen and is not normally
|
|
needed since the terminal is usually already in 80 column mode.
|
|
.PP
|
|
-The
|
|
-.IR reset
|
|
-program writes strings
|
|
-including
|
|
+The \fB@RESET@\fP program writes strings including
|
|
.BR iprog ,
|
|
etc., in the same order as the
|
|
.IR init
|
|
@@ -1191,8 +1190,7 @@
|
|
.BR rs3 ,
|
|
or
|
|
.BR rf
|
|
-reset capability strings are missing, the
|
|
-.IR reset
|
|
+reset capability strings are missing, the \fB@RESET@\fP
|
|
program falls back upon the corresponding initialization capability string.
|
|
.PP
|
|
If there are commands to set and clear tab stops, they can be given as
|
|
@@ -1365,7 +1363,7 @@
|
|
If the terminal
|
|
supports other escape sequences to set background and foreground, they should
|
|
be coded as \fBsetf\fR and \fBsetb\fR, respectively.
|
|
-The \fIvidputs()\fR
|
|
+The \fBvidputs\fR
|
|
function and the refresh functions use \fBsetaf\fR and \fBsetab\fR if they are
|
|
defined."
|
|
.PP
|
|
@@ -1656,13 +1654,13 @@
|
|
translations are much more strictly limited (to 1023 bytes), thus termcap translations
|
|
of long terminfo entries can cause problems.
|
|
.PP
|
|
-The man pages for 4.3BSD and older versions of \fBtgetent()\fP instruct the user to
|
|
+The man pages for 4.3BSD and older versions of \fBtgetent\fP instruct the user to
|
|
allocate a 1024-byte buffer for the termcap entry.
|
|
The entry gets null-terminated by
|
|
the termcap library, so that makes the maximum safe length for a termcap entry
|
|
1k\-1 (1023) bytes.
|
|
Depending on what the application and the termcap library
|
|
-being used does, and where in the termcap file the terminal type that \fBtgetent()\fP
|
|
+being used does, and where in the termcap file the terminal type that \fBtgetent\fP
|
|
is searching for is, several bad things can happen.
|
|
.PP
|
|
Some termcap libraries print a warning message or exit if they find an
|
|
@@ -1683,7 +1681,7 @@
|
|
affects more than just users of that particular terminal.
|
|
This is the
|
|
length of the entry as it exists in /etc/termcap, minus the
|
|
-backslash-newline pairs, which \fBtgetent()\fP strips out while reading it.
|
|
+backslash-newline pairs, which \fBtgetent\fP strips out while reading it.
|
|
Some termcap libraries strip off the final newline, too (GNU termcap does not).
|
|
Now suppose:
|
|
.bP
|
|
@@ -1695,12 +1693,12 @@
|
|
the whole entry into the buffer, no matter what its length, to see
|
|
if it is the entry it wants,
|
|
.bP
|
|
-and \fBtgetent()\fP is searching for a terminal type that either is the
|
|
+and \fBtgetent\fP is searching for a terminal type that either is the
|
|
long entry, appears in the termcap file after the long entry, or
|
|
-does not appear in the file at all (so that \fBtgetent()\fP has to search
|
|
+does not appear in the file at all (so that \fBtgetent\fP has to search
|
|
the whole termcap file).
|
|
.PP
|
|
-Then \fBtgetent()\fP will overwrite memory, perhaps its stack, and probably core dump
|
|
+Then \fBtgetent\fP will overwrite memory, perhaps its stack, and probably core dump
|
|
the program.
|
|
Programs like telnet are particularly vulnerable; modern telnets
|
|
pass along values like the terminal type automatically.
|
|
@@ -1713,7 +1711,7 @@
|
|
.PP
|
|
The "after tc expansion" length will have a similar effect to the
|
|
above, but only for people who actually set TERM to that terminal
|
|
-type, since \fBtgetent()\fP only does "tc" expansion once it is found the
|
|
+type, since \fBtgetent\fP only does "tc" expansion once it is found the
|
|
terminal type it was looking for, not while searching.
|
|
.PP
|
|
In summary, a termcap entry that is longer than 1023 bytes can cause,
|
|
Index: ncurses/llib-lncurses
|
|
--- ncurses-6.0-20161008+/ncurses/llib-lncurses 2015-08-15 19:06:20.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-lncurses 2016-10-15 23:25:20.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 1998-2013,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 1998-2015,2016 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 *
|
|
@@ -3000,8 +3000,8 @@
|
|
/* ./tinfo/lib_baudrate.c */
|
|
|
|
struct speed {
|
|
- short s;
|
|
- int sp;
|
|
+ int given_speed;
|
|
+ int actual_speed;
|
|
};
|
|
|
|
#undef _nc_baudrate
|
|
@@ -4269,6 +4269,14 @@
|
|
TERMTYPE *const tp)
|
|
{ /* void */ }
|
|
|
|
+#undef _nc_write_object
|
|
+int _nc_write_object(
|
|
+ TERMTYPE *tp,
|
|
+ char *buffer,
|
|
+ unsigned *offset,
|
|
+ unsigned limit)
|
|
+ { return(*(int *)0); }
|
|
+
|
|
#undef _nc_tic_written
|
|
int _nc_tic_written(void)
|
|
{ return(*(int *)0); }
|
|
Index: ncurses/llib-lncursest
|
|
--- ncurses-6.0-20161008+/ncurses/llib-lncursest 2015-08-15 20:08:58.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-lncursest 2016-10-15 23:25:20.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 2008-2013,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2008-2015,2016 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 *
|
|
@@ -3015,8 +3015,8 @@
|
|
/* ./tinfo/lib_baudrate.c */
|
|
|
|
struct speed {
|
|
- short s;
|
|
- int sp;
|
|
+ int given_speed;
|
|
+ int actual_speed;
|
|
};
|
|
|
|
#undef _nc_baudrate
|
|
@@ -4382,6 +4382,14 @@
|
|
TERMTYPE *const tp)
|
|
{ /* void */ }
|
|
|
|
+#undef _nc_write_object
|
|
+int _nc_write_object(
|
|
+ TERMTYPE *tp,
|
|
+ char *buffer,
|
|
+ unsigned *offset,
|
|
+ unsigned limit)
|
|
+ { return(*(int *)0); }
|
|
+
|
|
#undef _nc_tic_written
|
|
int _nc_tic_written(void)
|
|
{ return(*(int *)0); }
|
|
Index: ncurses/llib-lncursestw
|
|
--- ncurses-6.0-20161008+/ncurses/llib-lncursestw 2015-08-15 19:07:52.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-lncursestw 2016-10-15 23:25:20.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 2009-2013,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2009-2015,2016 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 *
|
|
@@ -3798,8 +3798,8 @@
|
|
/* ./tinfo/lib_baudrate.c */
|
|
|
|
struct speed {
|
|
- short s;
|
|
- int sp;
|
|
+ int given_speed;
|
|
+ int actual_speed;
|
|
};
|
|
|
|
#undef _nc_baudrate
|
|
@@ -5198,6 +5198,14 @@
|
|
TERMTYPE *const tp)
|
|
{ /* void */ }
|
|
|
|
+#undef _nc_write_object
|
|
+int _nc_write_object(
|
|
+ TERMTYPE *tp,
|
|
+ char *buffer,
|
|
+ unsigned *offset,
|
|
+ unsigned limit)
|
|
+ { return(*(int *)0); }
|
|
+
|
|
#undef _nc_tic_written
|
|
int _nc_tic_written(void)
|
|
{ return(*(int *)0); }
|
|
Index: ncurses/llib-lncursesw
|
|
--- ncurses-6.0-20161008+/ncurses/llib-lncursesw 2015-08-15 20:03:43.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-lncursesw 2016-10-15 23:25:20.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 2001-2013,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2001-2015,2016 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 *
|
|
@@ -3783,8 +3783,8 @@
|
|
/* ./tinfo/lib_baudrate.c */
|
|
|
|
struct speed {
|
|
- short s;
|
|
- int sp;
|
|
+ int given_speed;
|
|
+ int actual_speed;
|
|
};
|
|
|
|
#undef _nc_baudrate
|
|
@@ -5085,6 +5085,14 @@
|
|
TERMTYPE *const tp)
|
|
{ /* void */ }
|
|
|
|
+#undef _nc_write_object
|
|
+int _nc_write_object(
|
|
+ TERMTYPE *tp,
|
|
+ char *buffer,
|
|
+ unsigned *offset,
|
|
+ unsigned limit)
|
|
+ { return(*(int *)0); }
|
|
+
|
|
#undef _nc_tic_written
|
|
int _nc_tic_written(void)
|
|
{ return(*(int *)0); }
|
|
Index: ncurses/llib-ltic
|
|
--- ncurses-6.0-20161008+/ncurses/llib-ltic 2015-08-15 19:06:29.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-ltic 2016-10-15 23:24:41.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 2012,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2012-2015,2016 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 *
|
|
@@ -34,6 +34,7 @@
|
|
/* ./tinfo/alloc_entry.c */
|
|
|
|
#include <curses.priv.h>
|
|
+
|
|
#undef _nc_init_entry
|
|
void _nc_init_entry(
|
|
TERMTYPE *const tp)
|
|
@@ -196,6 +197,14 @@
|
|
TERMTYPE *const tp)
|
|
{ /* void */ }
|
|
|
|
+#undef _nc_write_object
|
|
+int _nc_write_object(
|
|
+ TERMTYPE *tp,
|
|
+ char *buffer,
|
|
+ unsigned *offset,
|
|
+ unsigned limit)
|
|
+ { return(*(int *)0); }
|
|
+
|
|
#undef _nc_tic_written
|
|
int _nc_tic_written(void)
|
|
{ return(*(int *)0); }
|
|
Index: ncurses/llib-ltict
|
|
--- ncurses-6.0-20161008+/ncurses/llib-ltict 2015-08-15 19:08:45.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-ltict 2016-10-15 23:24:41.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 2013,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2013-2015,2016 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 *
|
|
@@ -34,6 +34,7 @@
|
|
/* ./tinfo/alloc_entry.c */
|
|
|
|
#include <curses.priv.h>
|
|
+
|
|
#undef _nc_init_entry
|
|
void _nc_init_entry(
|
|
TERMTYPE *const tp)
|
|
@@ -196,6 +197,14 @@
|
|
TERMTYPE *const tp)
|
|
{ /* void */ }
|
|
|
|
+#undef _nc_write_object
|
|
+int _nc_write_object(
|
|
+ TERMTYPE *tp,
|
|
+ char *buffer,
|
|
+ unsigned *offset,
|
|
+ unsigned limit)
|
|
+ { return(*(int *)0); }
|
|
+
|
|
#undef _nc_tic_written
|
|
int _nc_tic_written(void)
|
|
{ return(*(int *)0); }
|
|
Index: ncurses/llib-ltictw
|
|
--- ncurses-6.0-20161008+/ncurses/llib-ltictw 2015-08-15 19:08:02.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-ltictw 2016-10-15 23:24:41.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 2012,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2012-2015,2016 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 *
|
|
@@ -34,6 +34,7 @@
|
|
/* ./tinfo/alloc_entry.c */
|
|
|
|
#include <curses.priv.h>
|
|
+
|
|
#undef _nc_init_entry
|
|
void _nc_init_entry(
|
|
TERMTYPE *const tp)
|
|
@@ -196,6 +197,14 @@
|
|
TERMTYPE *const tp)
|
|
{ /* void */ }
|
|
|
|
+#undef _nc_write_object
|
|
+int _nc_write_object(
|
|
+ TERMTYPE *tp,
|
|
+ char *buffer,
|
|
+ unsigned *offset,
|
|
+ unsigned limit)
|
|
+ { return(*(int *)0); }
|
|
+
|
|
#undef _nc_tic_written
|
|
int _nc_tic_written(void)
|
|
{ return(*(int *)0); }
|
|
Index: ncurses/llib-lticw
|
|
--- ncurses-6.0-20161008+/ncurses/llib-lticw 2015-08-15 19:07:15.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-lticw 2016-10-15 23:24:41.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 2012,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2012-2015,2016 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 *
|
|
@@ -34,6 +34,7 @@
|
|
/* ./tinfo/alloc_entry.c */
|
|
|
|
#include <curses.priv.h>
|
|
+
|
|
#undef _nc_init_entry
|
|
void _nc_init_entry(
|
|
TERMTYPE *const tp)
|
|
@@ -196,6 +197,14 @@
|
|
TERMTYPE *const tp)
|
|
{ /* void */ }
|
|
|
|
+#undef _nc_write_object
|
|
+int _nc_write_object(
|
|
+ TERMTYPE *tp,
|
|
+ char *buffer,
|
|
+ unsigned *offset,
|
|
+ unsigned limit)
|
|
+ { return(*(int *)0); }
|
|
+
|
|
#undef _nc_tic_written
|
|
int _nc_tic_written(void)
|
|
{ return(*(int *)0); }
|
|
Index: ncurses/llib-ltinfo
|
|
--- ncurses-6.0-20161008+/ncurses/llib-ltinfo 2015-08-15 19:06:34.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-ltinfo 2016-10-15 23:24:41.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 2012-2013,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2012-2015,2016 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 *
|
|
@@ -34,6 +34,7 @@
|
|
/* ./tinfo/access.c */
|
|
|
|
#include <curses.priv.h>
|
|
+
|
|
#undef _nc_rootname
|
|
char *_nc_rootname(
|
|
char *path)
|
|
@@ -318,8 +319,8 @@
|
|
/* ./tinfo/lib_baudrate.c */
|
|
|
|
struct speed {
|
|
- short s;
|
|
- int sp;
|
|
+ int given_speed;
|
|
+ int actual_speed;
|
|
};
|
|
|
|
#undef _nc_baudrate
|
|
Index: ncurses/llib-ltinfot
|
|
--- ncurses-6.0-20161008+/ncurses/llib-ltinfot 2015-08-15 19:08:50.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-ltinfot 2016-10-15 23:24:41.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 2013,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2013-2015,2016 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 *
|
|
@@ -34,6 +34,7 @@
|
|
/* ./tinfo/access.c */
|
|
|
|
#include <curses.priv.h>
|
|
+
|
|
#undef _nc_rootname
|
|
char *_nc_rootname(
|
|
char *path)
|
|
@@ -324,8 +325,8 @@
|
|
/* ./tinfo/lib_baudrate.c */
|
|
|
|
struct speed {
|
|
- short s;
|
|
- int sp;
|
|
+ int given_speed;
|
|
+ int actual_speed;
|
|
};
|
|
|
|
#undef _nc_baudrate
|
|
Index: ncurses/llib-ltinfotw
|
|
--- ncurses-6.0-20161008+/ncurses/llib-ltinfotw 2015-08-15 19:08:08.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-ltinfotw 2016-10-15 23:24:41.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 2012-2013,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2012-2015,2016 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 *
|
|
@@ -34,6 +34,7 @@
|
|
/* ./tinfo/access.c */
|
|
|
|
#include <curses.priv.h>
|
|
+
|
|
#undef _nc_rootname
|
|
char *_nc_rootname(
|
|
char *path)
|
|
@@ -324,8 +325,8 @@
|
|
/* ./tinfo/lib_baudrate.c */
|
|
|
|
struct speed {
|
|
- short s;
|
|
- int sp;
|
|
+ int given_speed;
|
|
+ int actual_speed;
|
|
};
|
|
|
|
#undef _nc_baudrate
|
|
Index: ncurses/llib-ltinfow
|
|
--- ncurses-6.0-20161008+/ncurses/llib-ltinfow 2015-08-15 19:07:20.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/llib-ltinfow 2016-10-15 23:24:41.000000000 +0000
|
|
@@ -1,5 +1,5 @@
|
|
/****************************************************************************
|
|
- * Copyright (c) 2012-2013,2015 Free Software Foundation, Inc. *
|
|
+ * Copyright (c) 2012-2015,2016 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 *
|
|
@@ -34,6 +34,7 @@
|
|
/* ./tinfo/access.c */
|
|
|
|
#include <curses.priv.h>
|
|
+
|
|
#undef _nc_rootname
|
|
char *_nc_rootname(
|
|
char *path)
|
|
@@ -318,8 +319,8 @@
|
|
/* ./tinfo/lib_baudrate.c */
|
|
|
|
struct speed {
|
|
- short s;
|
|
- int sp;
|
|
+ int given_speed;
|
|
+ int actual_speed;
|
|
};
|
|
|
|
#undef _nc_baudrate
|
|
Index: ncurses/tty/tty_update.c
|
|
Prereq: 1.283
|
|
--- ncurses-6.0-20161008+/ncurses/tty/tty_update.c 2016-05-28 23:32:40.000000000 +0000
|
|
+++ ncurses-6.0-20161015/ncurses/tty/tty_update.c 2016-10-15 23:00:29.000000000 +0000
|
|
@@ -82,7 +82,7 @@
|
|
|
|
#include <ctype.h>
|
|
|
|
-MODULE_ID("$Id: tty_update.c,v 1.283 2016/05/28 23:32:40 tom Exp $")
|
|
+MODULE_ID("$Id: tty_update.c,v 1.284 2016/10/15 23:00:29 tom Exp $")
|
|
|
|
/*
|
|
* This define controls the line-breakout optimization. Every once in a
|
|
@@ -676,7 +676,7 @@
|
|
TPARM_2(repeat_char,
|
|
CharOf(ntext0),
|
|
rep_count),
|
|
- rep_count,
|
|
+ 1,
|
|
NCURSES_SP_NAME(_nc_outch));
|
|
SP_PARM->_curscol += rep_count;
|
|
|
|
@@ -1736,7 +1736,7 @@
|
|
TPUTS_TRACE("parm_ich");
|
|
NCURSES_SP_NAME(tputs) (NCURSES_SP_ARGx
|
|
TPARM_1(parm_ich, count),
|
|
- count,
|
|
+ 1,
|
|
NCURSES_SP_NAME(_nc_outch));
|
|
while (count) {
|
|
PutAttrChar(NCURSES_SP_ARGx CHREF(*line));
|
|
@@ -1789,7 +1789,7 @@
|
|
TPUTS_TRACE("parm_dch");
|
|
NCURSES_SP_NAME(tputs) (NCURSES_SP_ARGx
|
|
TPARM_1(parm_dch, count),
|
|
- count,
|
|
+ 1,
|
|
NCURSES_SP_NAME(_nc_outch));
|
|
} else {
|
|
int n;
|
|
Index: package/debian-mingw/changelog
|
|
--- ncurses-6.0-20161008+/package/debian-mingw/changelog 2016-10-03 00:57:15.000000000 +0000
|
|
+++ ncurses-6.0-20161015/package/debian-mingw/changelog 2016-10-15 15:43:49.000000000 +0000
|
|
@@ -1,8 +1,8 @@
|
|
-ncurses6 (6.0+20161008) unstable; urgency=low
|
|
+ncurses6 (6.0+20161015) unstable; urgency=low
|
|
|
|
* latest weekly patch
|
|
|
|
- -- Thomas E. Dickey <dickey@invisible-island.net> Sun, 02 Oct 2016 20:57:15 -0400
|
|
+ -- Thomas E. Dickey <dickey@invisible-island.net> Sat, 15 Oct 2016 11:43:49 -0400
|
|
|
|
ncurses6 (5.9-20131005) unstable; urgency=low
|
|
|
|
Index: package/debian-mingw64/changelog
|
|
--- ncurses-6.0-20161008+/package/debian-mingw64/changelog 2016-10-03 00:57:15.000000000 +0000
|
|
+++ ncurses-6.0-20161015/package/debian-mingw64/changelog 2016-10-15 15:43:49.000000000 +0000
|
|
@@ -1,8 +1,8 @@
|
|
-ncurses6 (6.0+20161008) unstable; urgency=low
|
|
+ncurses6 (6.0+20161015) unstable; urgency=low
|
|
|
|
* latest weekly patch
|
|
|
|
- -- Thomas E. Dickey <dickey@invisible-island.net> Sun, 02 Oct 2016 20:57:15 -0400
|
|
+ -- Thomas E. Dickey <dickey@invisible-island.net> Sat, 15 Oct 2016 11:43:49 -0400
|
|
|
|
ncurses6 (5.9-20131005) unstable; urgency=low
|
|
|
|
Index: package/debian/changelog
|
|
--- ncurses-6.0-20161008+/package/debian/changelog 2016-10-03 00:57:15.000000000 +0000
|
|
+++ ncurses-6.0-20161015/package/debian/changelog 2016-10-15 15:43:49.000000000 +0000
|
|
@@ -1,8 +1,8 @@
|
|
-ncurses6 (6.0+20161008) unstable; urgency=low
|
|
+ncurses6 (6.0+20161015) unstable; urgency=low
|
|
|
|
* latest weekly patch
|
|
|
|
- -- Thomas E. Dickey <dickey@invisible-island.net> Sun, 02 Oct 2016 20:57:15 -0400
|
|
+ -- Thomas E. Dickey <dickey@invisible-island.net> Sat, 15 Oct 2016 11:43:49 -0400
|
|
|
|
ncurses6 (5.9-20120608) unstable; urgency=low
|
|
|
|
Index: package/mingw-ncurses.nsi
|
|
Prereq: 1.179
|
|
--- ncurses-6.0-20161008+/package/mingw-ncurses.nsi 2016-10-03 00:57:15.000000000 +0000
|
|
+++ ncurses-6.0-20161015/package/mingw-ncurses.nsi 2016-10-15 15:43:49.000000000 +0000
|
|
@@ -1,4 +1,4 @@
|
|
-; $Id: mingw-ncurses.nsi,v 1.179 2016/10/03 00:57:15 tom Exp $
|
|
+; $Id: mingw-ncurses.nsi,v 1.180 2016/10/15 15:43:49 tom Exp $
|
|
|
|
; TODO add examples
|
|
; TODO bump ABI to 6
|
|
@@ -10,7 +10,7 @@
|
|
!define VERSION_MAJOR "6"
|
|
!define VERSION_MINOR "0"
|
|
!define VERSION_YYYY "2016"
|
|
-!define VERSION_MMDD "1008"
|
|
+!define VERSION_MMDD "1015"
|
|
!define VERSION_PATCH ${VERSION_YYYY}${VERSION_MMDD}
|
|
|
|
!define MY_ABI "5"
|
|
Index: package/mingw-ncurses.spec
|
|
--- ncurses-6.0-20161008+/package/mingw-ncurses.spec 2016-10-03 00:57:15.000000000 +0000
|
|
+++ ncurses-6.0-20161015/package/mingw-ncurses.spec 2016-10-15 15:43:49.000000000 +0000
|
|
@@ -3,7 +3,7 @@
|
|
Summary: shared libraries for terminal handling
|
|
Name: mingw32-ncurses6
|
|
Version: 6.0
|
|
-Release: 20161008
|
|
+Release: 20161015
|
|
License: X11
|
|
Group: Development/Libraries
|
|
Source: ncurses-%{version}-%{release}.tgz
|
|
Index: package/ncurses.spec
|
|
--- ncurses-6.0-20161008+/package/ncurses.spec 2016-10-03 00:57:15.000000000 +0000
|
|
+++ ncurses-6.0-20161015/package/ncurses.spec 2016-10-15 15:43:49.000000000 +0000
|
|
@@ -1,7 +1,7 @@
|
|
Summary: shared libraries for terminal handling
|
|
Name: ncurses6
|
|
Version: 6.0
|
|
-Release: 20161008
|
|
+Release: 20161015
|
|
License: X11
|
|
Group: Development/Libraries
|
|
Source: ncurses-%{version}-%{release}.tgz
|