ncurses 6.0 - patch 20170422

[ncurses.git] / doc / html / man / terminfo.5.html

diff --git a/doc/html/man/terminfo.5.html b/doc/html/man/terminfo.5.html
index 1f1f78f34c602ecba1701cf0025c883a3ef4da7d..37564f4206fae734409f8644ab5bf6b6f28710ef 100644 (file)
--- a/doc/html/man/terminfo.5.html
+++ b/doc/html/man/terminfo.5.html
@@ -31,9 +31,9 @@
   * sale, use or other dealings in this Software without prior written       *
   * authorization.                                                           *
   ****************************************************************************
   * sale, use or other dealings in this Software without prior written       *
   * authorization.                                                           *
   ****************************************************************************

-  * @Id: terminfo.head,v 1.31 2017/03/06 09:58:14 tom Exp @
+  * @Id: terminfo.head,v 1.32 2017/04/22 13:52:49 tom Exp @

   * Head of terminfo man page ends here
   * Head of terminfo man page ends here

-  * @Id: terminfo.tail,v 1.78 2017/03/04 23:52:35 tom Exp @
+  * @Id: terminfo.tail,v 1.84 2017/04/22 16:00:56 tom Exp @

   * Beginning of terminfo.tail file
   * This file is part of ncurses.
   * See "terminfo.head" for copyright.
   * 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.
        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 20170401).
+       This describes <STRONG>ncurses</STRONG> version 6.0 (patch 20170422).

 
 
 </PRE><H3><a name="h3-Terminfo-Entry-Syntax">Terminfo Entry Syntax</a></H3><PRE>
 
 
 </PRE><H3><a name="h3-Terminfo-Entry-Syntax">Terminfo Entry Syntax</a></H3><PRE>


@@ -1127,10 +1127,10 @@
        encounters  a capability name which it does not recognize,
        it infers its type (boolean, number or  string)  from  the
        syntax and makes an extended table entry for that capabil-
        encounters  a capability name which it does not recognize,
        it infers its type (boolean, number or  string)  from  the
        syntax and makes an extended table entry for that capabil-

-       ity.  The <STRONG>use_extended_names</STRONG> function makes this  informa-
-       tion conditionally available to applications.  The ncurses
-       library provides the data leaving most of the behavior  to
-       applications:
+       ity.   The  <STRONG><A HREF="curs_extend.3x.html">use_extended_names(3x)</A></STRONG>  function  makes   this
+       information  conditionally available to applications.  The
+       ncurses library provides the  data  leaving  most  of  the
+       behavior to applications:

 
        <STRONG>o</STRONG>   User-defined capability strings whose name begins with
            "k" are treated as function keys.
 
        <STRONG>o</STRONG>   User-defined capability strings whose name begins with
            "k" are treated as function keys.


@@ -1225,11 +1225,30 @@
        ",".
 
        A number of escape sequences are provided  in  the  string
        ",".
 
        A number of escape sequences are provided  in  the  string

-       valued capabilities for easy encoding of characters there.
-       Both <STRONG>\E</STRONG> and <STRONG>\e</STRONG> map to an ESCAPE character, <STRONG>^x</STRONG>  maps  to  a
-       control-x  for  any appropriate x, and the sequences <STRONG>\n</STRONG> <STRONG>\l</STRONG>
-       <STRONG>\r</STRONG> <STRONG>\t</STRONG> <STRONG>\b</STRONG> <STRONG>\f</STRONG> <STRONG>\s</STRONG> give a  newline,  line-feed,  return,  tab,
-       backspace, form-feed, and space.  Other escapes include
+       valued capabilities for easy encoding of characters there:
+
+       <STRONG>o</STRONG>   Both <STRONG>\E</STRONG> and <STRONG>\e</STRONG> map to an ESCAPE character,
+
+       <STRONG>o</STRONG>   <STRONG>^x</STRONG> maps to a control-x for any appropriate <EM>x</EM>, and
+
+       <STRONG>o</STRONG>   the sequences
+
+             <STRONG>\n</STRONG>, <STRONG>\l</STRONG>, <STRONG>\r</STRONG>, <STRONG>\t</STRONG>, <STRONG>\b</STRONG>, <STRONG>\f</STRONG>, and <STRONG>\s</STRONG>
+
+           produce
+
+             <EM>newline</EM>,  <EM>line-feed</EM>,  <EM>return</EM>,  <EM>tab</EM>, <EM>backspace</EM>, <EM>form-</EM>
+             <EM>feed</EM>, and <EM>space</EM>,
+
+           respectively.
+
+       X/Open Curses does not say what "appropriate <EM>x</EM>" might  be.
+       In  practice, that is a printable ASCII graphic character.
+       The special case "^?" is interpreted as DEL (127).  In all
+       other  cases, the character value is AND'd with 0x1f, map-
+       ping to ASCII control codes in the range 0 through 31.
+
+       Other escapes include

 
        <STRONG>o</STRONG>   <STRONG>\^</STRONG> for <STRONG>^</STRONG>,
 
 
        <STRONG>o</STRONG>   <STRONG>\^</STRONG> for <STRONG>^</STRONG>,
 


@@ -1241,80 +1260,80 @@
 
        <STRONG>o</STRONG>   and <STRONG>\0</STRONG> for null.
 
 
        <STRONG>o</STRONG>   and <STRONG>\0</STRONG> for null.
 

-           <STRONG>\0</STRONG>  will  produce  \200,  which  does  not terminate a
-           string but behaves as a null character on most  termi-
+           <STRONG>\0</STRONG> will produce  \200,  which  does  not  terminate  a
+           string  but behaves as a null character on most termi-

            nals, providing CS7 is specified.  See <STRONG>stty(1)</STRONG>.
 
            nals, providing CS7 is specified.  See <STRONG>stty(1)</STRONG>.
 

-           The  reason  for this quirk is to maintain binary com-
-           patibility of the compiled terminfo files  with  other
-           implementations,  e.g.,  the SVr4 systems, which docu-
-           ment this.  Compiled terminfo  files  use  null-termi-
-           nated  strings, with no lengths.  Modifying this would
+           The reason for this quirk is to maintain  binary  com-
+           patibility  of  the compiled terminfo files with other
+           implementations, e.g., the SVr4 systems,  which  docu-
+           ment  this.   Compiled  terminfo files use null-termi-
+           nated strings, with no lengths.  Modifying this  would

            require a new binary format, which would not work with
            other implementations.
 
            require a new binary format, which would not work with
            other implementations.
 

-       Finally,  characters  may  be  given as three octal digits
+       Finally, characters may be given  as  three  octal  digits

        after a <STRONG>\</STRONG>.
 
        after a <STRONG>\</STRONG>.
 

-       A delay in milliseconds may appear anywhere  in  a  string
-       capability,  enclosed in $&lt;..&gt; brackets, as in <STRONG>el</STRONG>=\EK$&lt;5&gt;,
-       and padding characters are supplied by <STRONG><A HREF="curs_terminfo.3x.html">tputs(3x)</A></STRONG>  to  pro-
+       A  delay  in  milliseconds may appear anywhere in a string
+       capability, enclosed in $&lt;..&gt; brackets, as in  <STRONG>el</STRONG>=\EK$&lt;5&gt;,
+       and  padding  characters are supplied by <STRONG><A HREF="curs_terminfo.3x.html">tputs(3x)</A></STRONG> to pro-

        vide this delay.
 
        vide this delay.
 

-       <STRONG>o</STRONG>   The  delay  must  be a number with at most one decimal
+       <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.
 
            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,
+       <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.)
 
            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
+           Normally, padding is advisory if the  device  has  the
+           <STRONG>xon</STRONG>  capability;  it  is used for cost computation but

            does not trigger delays.
 
            does not trigger delays.
 

-       <STRONG>o</STRONG>   A  "/"  suffix indicates that the padding is mandatory
+       <STRONG>o</STRONG>   A "/" suffix indicates that the padding  is  mandatory

            and forces a delay of the given number of milliseconds
            and forces a delay of the given number of milliseconds

-           even  on  devices for which <STRONG>xon</STRONG> is present to indicate
+           even on devices for which <STRONG>xon</STRONG> is present  to  indicate

            flow control.
 
            flow control.
 

-       Sometimes individual capabilities must be  commented  out.
-       To  do this, put a period before the capability name.  For
+       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>
        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.
        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.
 
        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.
 
            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.
 
            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-
            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.
 
            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:
 
            <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
 
                (/usr/local/ncurses/share/terminfo:/usr/share/ter-
                minfo), and
 


@@ -1323,91 +1342,91 @@
 
 
 </PRE><H3><a name="h3-Preparing-Descriptions">Preparing Descriptions</a></H3><PRE>
 
 
 </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
        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-
        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.
 
        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
        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>
        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
        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-
        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-
        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>.
 
        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
        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.
 
        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
        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
        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
        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 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.
        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
        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,
        described as
 
        33|tty33|tty|model 33 teletype,


@@ -1421,21 +1440,21 @@
 
 
 </PRE><H3><a name="h3-Parameterized-Strings">Parameterized Strings</a></H3><PRE>
 
 
 </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
        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>.
 
        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.
 
        stack.  It is noted that more complex operations are often
        necessary, e.g., in the <STRONG>sgr</STRONG> string.
 


@@ -1444,8 +1463,8 @@
        <STRONG>%%</STRONG>   outputs "%"
 
        <STRONG>%</STRONG><EM>[[</EM>:<EM>]flags][width[.precision]][</EM><STRONG>doxXs</STRONG><EM>]</EM>
        <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 <EM>pop()</EM> like %c in <STRONG>printf</STRONG>
             ing interpreting "%-" as an operator.
 
        %c   print <EM>pop()</EM> like %c in <STRONG>printf</STRONG>


@@ -1467,12 +1486,12 @@
        <STRONG>%g</STRONG><EM>[A-Z]</EM>
             get static variable <EM>[a-z]</EM> and push it
 
        <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><A HREF="curs_terminfo.3x.html">tparm(3x)</A></STRONG>.   However, that fact is not documented
-            in  other  implementations.   Relying  on   it   will
-            adversely  impact  portability  to  other implementa-
+            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><A HREF="curs_terminfo.3x.html">tparm(3x)</A></STRONG>.  However, that fact is  not  documented
+            in   other   implementations.   Relying  on  it  will
+            adversely impact  portability  to  other  implementa-

             tions.
 
        <STRONG>%'</STRONG><EM>c</EM><STRONG>'</STRONG> char constant <EM>c</EM>
             tions.
 
        <STRONG>%'</STRONG><EM>c</EM><STRONG>'</STRONG> char constant <EM>c</EM>


@@ -1496,16 +1515,16 @@
             logical AND and OR operations (for conditionals)
 
        <STRONG>%!</STRONG>, <STRONG>%~</STRONG>
             logical AND and OR operations (for conditionals)
 
        <STRONG>%!</STRONG>, <STRONG>%~</STRONG>

-            unary   operations   (logical  and  bit  complement):
+            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>
             <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:
             control passes to the <STRONG>%e</STRONG> (else) part.
 
             It is possible to form else-if's a la Algol 68:


@@ -1514,221 +1533,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-
             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>
             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
             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,
        escape-string evaluations.
 
        Consider the HP2645, which, to get to row 3 and column 12,

-       needs to be sent \E&amp;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&amp;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&amp;%p2%2dc%p1%2dY".
 
        The Microterm ACT-IV needs the current row and column sent
        its.  Thus its <STRONG>cup</STRONG> capability is "cup=6\E&amp;%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
        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%'
        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
        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,
        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-
        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
        <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-
        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
        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
        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
        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
        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
        <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
        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>
        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
        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>.
 
        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.
 
        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
        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
        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).
 
        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.
 
        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
        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>ndsrc</STRONG> is defined.
 
        If the terminal has the ability to define a window as part
        implementation is more liberal and will do explicit erases
        after scrolling if <STRONG>ndsrc</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
        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.
 
        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>
        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.
 
        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
        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".
 
        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.
 
        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
        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-
        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.
 
        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
        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
        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
        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
        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.
 
        capability, with one parameter, <EM>n</EM>, will repeat the effects
        of <STRONG>ich1</STRONG> <EM>n</EM> times.
 


@@ -1736,62 +1755,62 @@
        in insert mode, give this as a number of milliseconds pad-
        ding in <STRONG>rmp</STRONG>.
 
        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.
 
        (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).
 
        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
        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-
        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.
 
        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>.
 
        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.
 
        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-
        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:
        corresponding separate attribute commands exist.
 
        For example, the DEC vt220 supports most of the modes:


@@ -1809,22 +1828,22 @@
         p8                   protect          not used
         p9                   altcharset       ^O (off) ^N (on)
 
         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
        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.
 
        \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.
 
        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>
        dencies yields
 
       <STRONG>sequence</STRONG>             <STRONG>when</STRONG> <STRONG>to</STRONG> <STRONG>output</STRONG>      <STRONG>terminfo</STRONG> <STRONG>translation</STRONG>


@@ -1843,62 +1862,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%;,
 
            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.
 
        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
        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.
 
        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.
 
        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
        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
        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
        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
        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
        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
        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.
 
        <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
        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


@@ -1938,60 +1957,60 @@
 
        <STRONG>o</STRONG>   <STRONG>khts</STRONG> (set a tab stop in this column).
 
 
        <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-
        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.
 
        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;
        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-
        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>
        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-
        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 <STRONG>tset</STRONG> 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  <STRONG>tset</STRONG> 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.
 
        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
        They are normally sent to the terminal, by the <EM>init</EM> option

-       of  the  <STRONG>tput</STRONG>  program,  each time the user logs in.  They
+       of the <STRONG>tput</STRONG> program, each time the  user  logs  in.   They

        will be printed in the following order:
 
               run the program
        will be printed in the following order:
 
               run the program


@@ -2011,213 +2030,228 @@
               and finally
                      output <STRONG>is3</STRONG>.
 
               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
        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-
        <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 <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
+       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 <STRONG>reset</STRONG> program writes strings including <STRONG>iprog</STRONG>, etc., in
        80 column mode.
 
        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.,
+       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
        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 <STRONG>reset</STRONG> 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
        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>
        <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
        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
        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-
        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.
 
        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>.
 
        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>
        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).
 
        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
        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
        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
        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.
 
        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>.
 
        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>.
 
        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.
 
        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>
        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&amp;T  4410v1  added.   This  alternate
+       Many terminals have alternate character  sets  useful  for
+       forms-drawing.   Terminfo  and <STRONG>curses</STRONG> built-in support for
+       the drawing characters supported by the VT100,  with  some
+       characters  from  the  AT&amp;T  4410v1 added.  This alternate

        character set may be specified by the <STRONG>acsc</STRONG> capability.
 
        character set may be specified by the <STRONG>acsc</STRONG> capability.
 

-       <STRONG>Glyph</STRONG>                       <STRONG>ACS</STRONG>           <STRONG>Ascii</STRONG>     <STRONG>VT100</STRONG>
-       <STRONG>Name</STRONG>                        <STRONG>Name</STRONG>          <STRONG>Default</STRONG>   <STRONG>Name</STRONG>
-       UK pound sign               ACS_STERLING  f         }
-       arrow pointing down         ACS_DARROW    v         .
-       arrow pointing left         ACS_LARROW    &lt;         ,
-       arrow pointing right        ACS_RARROW    &gt;         +
-       arrow pointing up           ACS_UARROW    ^         -
-       board of squares            ACS_BOARD     #         h
-       bullet                      ACS_BULLET    o         ~
-       checker board (stipple)     ACS_CKBOARD   :         a
-       degree symbol               ACS_DEGREE    \         f
-       diamond                     ACS_DIAMOND   +         `
-       greater-than-or-equal-to    ACS_GEQUAL    &gt;         z
-       greek pi                    ACS_PI        *         {
-
-       horizontal line             ACS_HLINE     -         q
-       lantern symbol              ACS_LANTERN   #         i
-       large plus or crossover     ACS_PLUS      +         n
-       less-than-or-equal-to       ACS_LEQUAL    &lt;         y
-       lower left corner           ACS_LLCORNER  +         m
-       lower right corner          ACS_LRCORNER  +         j
-       not-equal                   ACS_NEQUAL    !         |
-       plus/minus                  ACS_PLMINUS   #         g
-       scan line 1                 ACS_S1        ~         o
-       scan line 3                 ACS_S3        -         p
-       scan line 7                 ACS_S7        -         r
-       scan line 9                 ACS_S9        _         s
-       solid square block          ACS_BLOCK     #         0
-       tee pointing down           ACS_TTEE      +         w
-       tee pointing left           ACS_RTEE      +         u
-       tee pointing right          ACS_LTEE      +         t
-       tee pointing up             ACS_BTEE      +         v
-       upper left corner           ACS_ULCORNER  +         l
-       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
+       <STRONG>Glyph</STRONG>                    <STRONG>ACS</STRONG>          <STRONG>Ascii</STRONG>  <STRONG>VT100</STRONG>  <STRONG>VT100</STRONG>
+
+       <STRONG>Name</STRONG>                     <STRONG>Name</STRONG>         <STRONG>DefaultChar</STRONG>   <STRONG>Code</STRONG>
+       -----------------------------------------------------------
+       arrow pointing right     ACS_RARROW   &gt;      +      0x2b
+       arrow pointing left      ACS_LARROW   &lt;      ,      0x2c
+       arrow pointing up        ACS_UARROW   ^      -      0x2d
+       arrow pointing down      ACS_DARROW   v      .      0x2e
+       solid square block       ACS_BLOCK    #      0      0x30
+       diamond                  ACS_DIAMOND  +      `      0x60
+       checker board (stipple)  ACS_CKBOARD  :      a      0x61
+       degree symbol            ACS_DEGREE   \      f      0x66
+       plus/minus               ACS_PLMINUS  #      g      0x67
+       board of squares         ACS_BOARD    #      h      0x68
+       lantern symbol           ACS_LANTERN  #      i      0x69
+       lower right corner       ACS_LRCORNER +      j      0x6a
+       upper right corner       ACS_URCORNER +      k      0x6b
+       upper left corner        ACS_ULCORNER +      l      0x6c
+       lower left corner        ACS_LLCORNER +      m      0x6d
+       large plus or crossover  ACS_PLUS     +      n      0x6e
+       scan line 1              ACS_S1       ~      o      0x6f
+       scan line 3              ACS_S3       -      p      0x70
+       horizontal line          ACS_HLINE    -      q      0x71
+       scan line 7              ACS_S7       -      r      0x72
+       scan line 9              ACS_S9       _      s      0x73
+       tee pointing right       ACS_LTEE     +      t      0x74
+       tee pointing left        ACS_RTEE     +      u      0x75
+       tee pointing up          ACS_BTEE     +      v      0x76
+       tee pointing down        ACS_TTEE     +      w      0x77
+       vertical line            ACS_VLINE    |      x      0x78
+       less-than-or-equal-to    ACS_LEQUAL   &lt;      y      0x79
+       greater-than-or-equal-to ACS_GEQUAL   &gt;      z      0x7a
+       greek pi                 ACS_PI       *      {      0x7b
+       not-equal                ACS_NEQUAL   !      |      0x7c
+       UK pound sign            ACS_STERLING f      }      0x7d
+       bullet                   ACS_BULLET   o      ~      0x7e
+
+       A few notes apply to the table itself:
+
+       <STRONG>o</STRONG>   X/Open Curses incorrectly states that the mapping  for
+           <EM>lantern</EM> is uppercase "I" although Unix implementations
+           use the lowercase "i" mapping.
+
+       <STRONG>o</STRONG>   The DEC VT100 implemented graphics using the alternate
+           character set feature, temporarily switching <EM>modes</EM> and
+           sending characters in the  range  0x60  (96)  to  0x7e
+           (126).
+
+       <STRONG>o</STRONG>   The  AT&amp;T  terminal  added graphics characters outside
+           that range.
+
+       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>
        ACSC string.
 
 
 </PRE><H3><a name="h3-Color-Handling">Color Handling</a></H3><PRE>

-       The  curses  library  functions  <STRONG>init_pair</STRONG>  and <STRONG>init_color</STRONG>
-       manipulate the <EM>color</EM> <EM>pairs</EM> and <EM>color</EM> <EM>values</EM>  discussed  in
-       this  section (see <STRONG><A HREF="curs_color.3x.html">curs_color(3x)</A></STRONG> for details on these and
+       The curses  library  functions  <STRONG>init_pair</STRONG>  and  <STRONG>init_color</STRONG>
+       manipulate  the  <EM>color</EM> <EM>pairs</EM> and <EM>color</EM> <EM>values</EM> discussed in
+       this section (see <STRONG><A HREF="curs_color.3x.html">curs_color(3x)</A></STRONG> for details on these  and

        related functions).
 
        related functions).
 

-       Most color terminals are either "Tektronix-like"  or  "HP-
+       Most  color  terminals are either "Tektronix-like" or "HP-

        like":
 
        like":
 

-       <STRONG>o</STRONG>   Tektronix-like  terminals  have  a predefined set of <EM>N</EM>
-           colors (where <EM>N</EM> is usually 8), and can set  character-
-           cell  foreground  and  background  characters indepen-
+       <STRONG>o</STRONG>   Tektronix-like terminals have a predefined  set  of  <EM>N</EM>
+           colors  (where <EM>N</EM> is usually 8), and can set character-
+           cell foreground  and  background  characters  indepen-

            dently, mixing them into <EM>N</EM> * <EM>N</EM> color-pairs.
 
            dently, mixing them into <EM>N</EM> * <EM>N</EM> color-pairs.
 

-       <STRONG>o</STRONG>   On HP-like terminals, the user  must  set  each  color
-           pair  up separately (foreground and background are not
-           independently settable).  Up to <EM>M</EM> color-pairs  may  be
-           set  up  from  2*<EM>M</EM>  different colors.  ANSI-compatible
+       <STRONG>o</STRONG>   On  HP-like  terminals,  the  user must set each color
+           pair up separately (foreground and background are  not
+           independently  settable).   Up to <EM>M</EM> color-pairs may be
+           set up from  2*<EM>M</EM>  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
            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>.
 
        have the boolean capability <STRONG>bce</STRONG>.
 

-       While the curses library works with <EM>color</EM> <EM>pairs</EM>  (reflect-
-       ing  the  inability  of some devices to set foreground and
+       While  the curses library works with <EM>color</EM> <EM>pairs</EM> (reflect-
+       ing the inability of some devices to  set  foreground  and

        background colors independently), there are separate capa-
        bilities for setting these features:
 
        background colors independently), there are separate capa-
        bilities for setting these features:
 

-       <STRONG>o</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 color number.  The SVr4 docu-
-           mentation describes only <STRONG>setaf</STRONG>/<STRONG>setab</STRONG>; the  XPG4  draft
+       <STRONG>o</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 color number.  The SVr4  docu-
+           mentation  describes  only <STRONG>setaf</STRONG>/<STRONG>setab</STRONG>; the XPG4 draft

            says  that  "If  the  terminal  supports  ANSI  escape
            sequences  to  set  background  and  foreground,  they
            should be coded as <STRONG>setaf</STRONG> and <STRONG>setab</STRONG>, respectively.
 
        <STRONG>o</STRONG>   If the terminal supports other escape sequences to set
            says  that  "If  the  terminal  supports  ANSI  escape
            sequences  to  set  background  and  foreground,  they
            should be coded as <STRONG>setaf</STRONG> and <STRONG>setab</STRONG>, respectively.
 
        <STRONG>o</STRONG>   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> and the
+           background  and  foreground,  they  should be coded as
+           <STRONG>setf</STRONG> and <STRONG>setb</STRONG>,  respectively.   The  <STRONG>vidputs</STRONG>  and  the

            <STRONG><A HREF="curs_refresh.3x.html">refresh(3x)</A></STRONG> functions use the <STRONG>setaf</STRONG> and <STRONG>setab</STRONG> capabil-
            ities if they are defined.
 
            <STRONG><A HREF="curs_refresh.3x.html">refresh(3x)</A></STRONG> functions use the <STRONG>setaf</STRONG> and <STRONG>setab</STRONG> capabil-
            ities 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>
        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
        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>
        locations in color space.
 
              <STRONG>Color</STRONG>       <STRONG>#define</STRONG>       <STRONG>Value</STRONG>       <STRONG>RGB</STRONG>


@@ -2230,7 +2264,7 @@
              cyan      <STRONG>COLOR_CYAN</STRONG>        6     0,max,max
              white     <STRONG>COLOR_WHITE</STRONG>       7     max,max,max
 
              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>
        to a different mapping, i.e.,
 
              <STRONG>Color</STRONG>       <STRONG>#define</STRONG>       <STRONG>Value</STRONG>       <STRONG>RGB</STRONG>


@@ -2244,36 +2278,36 @@
              white     <STRONG>COLOR_WHITE</STRONG>       7     max,max,max
 
        It is important to not confuse the two sets of color capa-
              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.
 
        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.
 
        Some terminals allow the <EM>color</EM> <EM>values</EM> to be modified:
 
        parameter to set which color pair is current.
 
        Some terminals allow the <EM>color</EM> <EM>values</EM> to be modified:
 

-       <STRONG>o</STRONG>   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
+       <STRONG>o</STRONG>   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.  These three parameters default to
            describe the color.  These three parameters default to

-           being interpreted as RGB (Red,  Green,  Blue)  values.
-           If  the  boolean  capability  <STRONG>hls</STRONG> is present, they are
-           instead as HLS (Hue, Lightness,  Saturation)  indices.
+           being  interpreted  as  RGB (Red, Green, Blue) values.
+           If the boolean capability <STRONG>hls</STRONG>  is  present,  they  are
+           instead  as  HLS (Hue, Lightness, Saturation) indices.

            The ranges are terminal-dependent.
 
            The ranges are terminal-dependent.
 

-       <STRONG>o</STRONG>   On  an  HP-like  terminal, <STRONG>initp</STRONG> may give a capability
-           for changing a color-pair value.  It will  take  seven
-           parameters;  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,
+       <STRONG>o</STRONG>   On an HP-like terminal, <STRONG>initp</STRONG> may  give  a  capability
+           for  changing  a color-pair value.  It will take seven
+           parameters; 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>.
 
            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.
        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>
        understood by <STRONG>curses</STRONG> is as follows:
 
           <STRONG>Attribute</STRONG>              <STRONG>Bit</STRONG>   <STRONG>Decimal</STRONG>      <STRONG>Set</STRONG> <STRONG>by</STRONG>


@@ -2294,185 +2328,185 @@
           A_VERTICAL             14    16384        sgr1
           A_ITALIC               15    32768        sitm
 
           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.
 
        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>
        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
        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.
 
        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-
        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).
 
        (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".
 
        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
        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.
 
        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
        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.)
 
        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
        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>.
 
        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-
        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-
        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-
        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>
        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>.
 
        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.
 
        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
        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.
 
        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".
 
        "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-Pitfalls-of-Long-Entries">Pitfalls of Long Entries</a></H3><PRE>
        adding more capabilities of the form <STRONG>x</STRONG><EM>x</EM>.
 
 
 </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
        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.
 
        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
        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.
 
        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"
        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.
 
        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,
        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:
 
        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,
 
            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,
 
            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  term-
+       <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
            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
+       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
        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-
+       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
        nal.
 
        The "after tc expansion" length will have a similar effect


@@ -2482,27 +2516,27 @@
        while searching.
 
        In summary, a termcap entry that is longer than 1023 bytes
        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-
        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-
        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>
        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
        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.
 
 
        and XSI Curses extensions.
 
 


@@ -2510,69 +2544,69 @@
        Searching for terminal descriptions in <STRONG>$HOME/.terminfo</STRONG> and
        TERMINFO_DIRS is not supported by older implementations.
 
        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.
 
        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.
 
        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-
        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.
 
        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&amp;T 505 terminal.
 
        standard.  They are deduced from the documentation for the
        AT&amp;T 505 terminal.
 

-       Be careful assigning the <STRONG>kmous</STRONG>  capability.   The  <STRONG>ncurses</STRONG>
-       library  wants  to  interpret  it as <STRONG>KEY_MOUSE</STRONG>, for use by
-       terminals and emulators like xterm that can return  mouse-
+       Be  careful  assigning  the <STRONG>kmous</STRONG> capability.  The <STRONG>ncurses</STRONG>
+       library 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-
        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.
 
        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>o</STRONG>   <STRONG>SVR4,</STRONG> <STRONG>Solaris,</STRONG> <STRONG>ncurses</STRONG> -- These support all SVr4 capa-
            bilities.
 
        cases) different extension sets.  Here is a summary, accu-
        rate as of October 1995:
 
        <STRONG>o</STRONG>   <STRONG>SVR4,</STRONG> <STRONG>Solaris,</STRONG> <STRONG>ncurses</STRONG> -- These support all SVr4 capa-
            bilities.
 

-       <STRONG>o</STRONG>   <STRONG>SGI</STRONG>  --  Supports  the SVr4 set, adds one undocumented
+       <STRONG>o</STRONG>   <STRONG>SGI</STRONG> -- Supports the SVr4 set,  adds  one  undocumented

            extended string capability (<STRONG>set_pglen</STRONG>).
 
            extended string capability (<STRONG>set_pglen</STRONG>).
 

-       <STRONG>o</STRONG>   <STRONG>SVr1,</STRONG> <STRONG>Ultrix</STRONG> -- These support a restricted  subset  of
-           terminfo   capabilities.    The   booleans   end  with
+       <STRONG>o</STRONG>   <STRONG>SVr1,</STRONG>  <STRONG>Ultrix</STRONG>  -- These support a restricted subset of
+           terminfo  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>xon_xoff</STRONG>; the numerics with <STRONG>width_status_line</STRONG>; and the
            strings with <STRONG>prtr_non</STRONG>.
 

-       <STRONG>o</STRONG>   <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
+       <STRONG>o</STRONG>   <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

            function keys 11 through 63, plus <STRONG>plab_norm</STRONG>, <STRONG>label_on</STRONG>,
            function keys 11 through 63, plus <STRONG>plab_norm</STRONG>, <STRONG>label_on</STRONG>,

-           and <STRONG>label_off</STRONG>, plus some  incompatible  extensions  in
+           and  <STRONG>label_off</STRONG>,  plus  some incompatible extensions in

            the string table.
 
        <STRONG>o</STRONG>   <STRONG>AIX</STRONG> -- Supports the SVr1 subset, plus function keys 11
            through 63, plus a number of incompatible string table
            extensions.
 
            the string table.
 
        <STRONG>o</STRONG>   <STRONG>AIX</STRONG> -- Supports the SVr1 subset, plus function keys 11
            through 63, plus a number of incompatible string table
            extensions.
 

-       <STRONG>o</STRONG>   <STRONG>OSF</STRONG>  --  Supports both the SVr4 set and the AIX exten-
+       <STRONG>o</STRONG>   <STRONG>OSF</STRONG> -- Supports both the SVr4 set and the  AIX  exten-

            sions.
 
 
            sions.
 
 


@@ -2587,7 +2621,7 @@
 
 
 </PRE><H2><a name="h2-AUTHORS">AUTHORS</a></H2><PRE>
 
 
 </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.
 
 
        Based on pcurses by Pavel Curtis.