dmbcs/i-bash
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Imported from ../bash-1.14.7.tar.gz.

Browse source
This commit is contained in:
Jari Aalto 1996-08-26 18:22:31 +00:00
commit 726f63884d
402 changed files with 150297 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

339
lib/termcap/grot/COPYING Normal file
View file

@ -0,0 +1,339 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.

48
lib/termcap/grot/ChangeLog Normal file
View file

@ -0,0 +1,48 @@
Thu Apr 15 12:45:10 1993 David J. MacKenzie (djm@kropotkin.gnu.ai.mit.edu)
* Version 1.2.
* tparam.c [!emacs] (xmalloc, xrealloc, memory_out): New functions.
(tparam1): Use them.
* termcap.c, tparam.c: Use NULL or '\0' where appropriate
instead of 0. Rename some vars.
* termcap.c (tgetent): If EOF is reached on termcap file,
free allocated resources before returning.
* termcap.c (tgetent): Use /etc/termcap if TERMCAP is an entry
for a term type other than TERM.
From pjr@jet.UK (Paul J Rippin).
Sat Apr 10 23:55:12 1993 Richard Stallman (rms@mole.gnu.ai.mit.edu)
* tparam.c (tparam1): Don't set the 0200 bit on a non-0 character code.
From junio@twinsun.COM (Junio Hamano).
Tue Dec 8 22:02:15 1992 David J. MacKenzie (djm@kropotkin.gnu.ai.mit.edu)
* termcap.c, tparam.c: Use HAVE_STRING_H instead of USG.
Thu Dec 3 13:47:56 1992 David J. MacKenzie (djm@nutrimat.gnu.ai.mit.edu)
* termcap.c, tparam.c [HAVE_CONFIG_H]: Include config.h.
Fri Oct 23 12:35:29 1992 David J. MacKenzie (djm@goldman.gnu.ai.mit.edu)
* termcap.h [__STDC__]: Add consts. From Franc,ois Pinard.
Tue Oct 13 15:52:21 1992 David J. MacKenzie (djm@goldman.gnu.ai.mit.edu)
* Version 1.1.
Tue Sep 29 21:04:39 1992 David J. MacKenzie (djm@geech.gnu.ai.mit.edu)
* termcap.[ch], tparam.c: Fix some lint.
* version.c: New file.
Local Variables:
mode: indented-text
left-margin: 8
version-control: never
End:

117
lib/termcap/grot/INSTALL Normal file
View file

@ -0,0 +1,117 @@
This is a generic INSTALL file for utilities distributions.
If this package does not come with, e.g., installable documentation or
data files, please ignore the references to them below.
To compile this package:
1. Configure the package for your system. In the directory that this
file is in, type `./configure'. If you're using `csh' on an old
version of System V, you might need to type `sh configure' instead to
prevent `csh' from trying to execute `configure' itself.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation, and
creates the Makefile(s) (one in each subdirectory of the source
directory). In some packages it creates a C header file containing
system-dependent definitions. It also creates a file `config.status'
that you can run in the future to recreate the current configuration.
Running `configure' takes a minute or two. While it is running, it
prints some messages that tell what it is doing. If you don't want to
see the messages, run `configure' with its standard output redirected
to `/dev/null'; for example, `./configure >/dev/null'.
To compile the package in a different directory from the one
containing the source code, you must use a version of `make' that
supports the VPATH variable, such as GNU `make'. `cd' to the directory
where you want the object files and executables to go and run
`configure'. `configure' automatically checks for the source code in
the directory that `configure' is in and in `..'. If for some reason
`configure' is not in the source code directory that you are
configuring, then it will report that it can't find the source code.
In that case, run `configure' with the option `--srcdir=DIR', where
DIR is the directory that contains the source code.
By default, `make install' will install the package's files in
/usr/local/bin, /usr/local/lib, /usr/local/man, etc. You can specify
an installation prefix other than /usr/local by giving `configure' the
option `--prefix=PATH'. Alternately, you can do so by giving a value
for the `prefix' variable when you run `make', e.g.,
make prefix=/usr/gnu
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If
you give `configure' the option `--exec-prefix=PATH' or set the
`make' variable `exec_prefix' to PATH, the package will use PATH as
the prefix for installing programs and libraries. Data files and
documentation will still use the regular prefix. Normally, all files
are installed using the regular prefix.
Another `configure' option is useful mainly in `Makefile' rules for
updating `config.status' and `Makefile'. The `--no-create' option
figures out the configuration for your system and records it in
`config.status', without actually configuring the package (creating
`Makefile's and perhaps a configuration header file). Later, you can
run `./config.status' to actually configure the package. You can also
give `config.status' the `--recheck' option, which makes it re-run
`configure' with the same arguments you used before. This option is
useful if you change `configure'.
Some packages pay attention to `--with-PACKAGE' options to `configure',
where PACKAGE is something like `gnu-libc' or `x' (for the X Window System).
The README should mention any --with- options that the package recognizes.
`configure' ignores any other arguments that you give it.
If your system requires unusual options for compilation or linking
that `configure' doesn't know about, you can give `configure' initial
values for some variables by setting them in the environment. In
Bourne-compatible shells, you can do that on the command line like
this:
CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure
The `make' variables that you might want to override with environment
variables when running `configure' are:
(For these variables, any value given in the environment overrides the
value that `configure' would choose:)
CC C compiler program.
Default is `cc', or `gcc' if `gcc' is in your PATH.
INSTALL Program to use to install files.
Default is `install' if you have it, `cp' otherwise.
(For these variables, any value given in the environment is added to
the value that `configure' chooses:)
DEFS Configuration options, in the form `-Dfoo -Dbar ...'
Do not use this variable in packages that create a
configuration header file.
LIBS Libraries to link with, in the form `-lfoo -lbar ...'
If you need to do unusual things to compile the package, we encourage
you to figure out how `configure' could check whether to do them, and
mail diffs or instructions to the address given in the README so we
can include them in the next release.
2. Type `make' to compile the package. If you want, you can override
the `make' variables CFLAGS and LDFLAGS like this:
make CFLAGS=-O2 LDFLAGS=-s
3. If the package comes with self-tests and you want to run them,
type `make check'. If you're not sure whether there are any, try it;
if `make' responds with something like
make: *** No way to make target `check'. Stop.
then the package does not come with self-tests.
4. Type `make install' to install programs, data files, and
documentation.
5. You can remove the program binaries and object files from the
source directory by typing `make clean'. To also remove the
Makefile(s), the header file containing system-dependent definitions
(if the package uses one), and `config.status' (all the files that
`configure' created), type `make distclean'.
The file `configure.in' is used as a template to create `configure' by
a program called `autoconf'. You will only need it if you want to
regenerate `configure' using a newer version of `autoconf'.

118
lib/termcap/grot/Makefile.in Normal file
View file

@ -0,0 +1,118 @@
# Makefile for GNU termcap library.
# Copyright (C) 1992, 1993 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
#### Start of system configuration section. ####
srcdir = @srcdir@
VPATH = @srcdir@
CC = @CC@
# If you don't have a BSD or GNU install program, use cp.
INSTALL = @INSTALL@
INSTALL_DATA = @INSTALL_DATA@
MAKEINFO = makeinfo
# Things you might add to DEFS:
# -DHAVE_STRING_H If you have memcpy instead of bcopy.
# -DNO_ARG_ARRAY If you can't take the address of the first of
# a group of arguments and treat it as an array.
# We always define this, because it's not a big loss
# and can't be detected when cross-autoconfiguring.
DEFS = @DEFS@ -DNO_ARG_ARRAY
CFLAGS = -g
prefix = /usr/local
exec_prefix = $(prefix)
# Directory in which to install libtermcap.a.
libdir = $(exec_prefix)/lib
# Directory in which to install termcap.h.
includedir = $(prefix)/include
# Directory in which to optionally also install termcap.h,
# so compilers besides gcc can find it by default.
# If it is empty or not defined, termcap.h will only be installed in
# includedir.
oldincludedir = /usr/include
# Directory in which to install the documentation info files.
infodir = $(prefix)/info
#### End of system configuration section. ####
SHELL = /bin/sh
SRCS = termcap.c tparam.c version.c
OBJS = termcap.o tparam.o version.o
HDRS = termcap.h
DISTFILES = $(SRCS) $(HDRS) ChangeLog COPYING README INSTALL NEWS \
termcap.texi termcap.info* \
texinfo.tex Makefile.in configure configure.in
all: libtermcap.a termcap.info
.c.o:
$(CC) -c $(CPPFLAGS) $(DEFS) -I$(srcdir) $(CFLAGS) $<
install: all
$(INSTALL_DATA) libtermcap.a $(libdir)/libtermcap.a
-ranlib $(libdir)/libtermcap.a
test -d $(includedir) || mkdir $(includedir)
cd $(srcdir); $(INSTALL_DATA) termcap.h $(includedir)/termcap.h
-cd $(srcdir); test -z "$(oldincludedir)" || \
$(INSTALL_DATA) termcap.h $(oldincludedir)/termcap.h
cd $(srcdir); for f in termcap.info*; \
do $(INSTALL_DATA) $$f $(infodir)/$$f; done
uninstall:
rm -f $(libdir)/libtermcap.a $(includedir)/termcap.h
test -z "$(oldincludedir)" || rm -f $(oldincludedir)/termcap.h
rm -f $(infodir)/termcap.info*
libtermcap.a: $(OBJS)
ar rc $@ $(OBJS)
-ranlib $@
termcap.info: termcap.texi
$(MAKEINFO) $(srcdir)/termcap.texi --output=$(srcdir)/termcap.info
TAGS: $(SRCS)
etags $(SRCS)
clean:
rm -f *.a *.o core
mostlyclean: clean
distclean: clean
rm -f Makefile config.status
realclean: distclean
rm -f TAGS *.info*
dist: $(DISTFILES)
echo termcap-`sed -e '/version_string/!d' -e 's/[^0-9]*\([0-9a-z.]*\).*/\1/' -e q version.c` > .fname
rm -rf `cat .fname`
mkdir `cat .fname`
ln $(DISTFILES) `cat .fname`
tar chzf `cat .fname`.tar.z `cat .fname`
rm -rf `cat .fname` .fname

12
lib/termcap/grot/NEWS Normal file
View file

@ -0,0 +1,12 @@
Major changes in release 1.2:
For `%.', only set the high bit on NUL.
Fix a file descriptor and memory leak.
Add const in termcap.h prototypes.
Configuration improvements.
Major changes in release 1.1:
Fix portability problems.
Improve configuration and installation.
Fix compiler warnings.

14
lib/termcap/grot/README Normal file
View file

@ -0,0 +1,14 @@
This is the GNU termcap library -- a library of C functions that
enable programs to send control strings to terminals in a way
independent of the terminal type. Most of this package is also
distributed with GNU Emacs, but it is available in this separate
distribution to make it easier to install as -ltermcap.
The GNU termcap library does not place an arbitrary limit on the size
of termcap entries, unlike most other termcap libraries.
See the file INSTALL for compilation and installation instructions.
Please report any bugs in this library to bug-gnu-emacs@prep.ai.mit.edu.
You can check which version of the library you have by using the RCS
`ident' command on libtermcap.a.

346
lib/termcap/grot/configure vendored Executable file
View file

@ -0,0 +1,346 @@
#!/bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated automatically using autoconf.
# Copyright (C) 1991, 1992, 1993 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
# Usage: configure [--srcdir=DIR] [--host=HOST] [--gas] [--nfp] [--no-create]
# [--prefix=PREFIX] [--exec-prefix=PREFIX] [--with-PACKAGE] [TARGET]
# Ignores all args except --srcdir, --prefix, --exec-prefix, --no-create, and
# --with-PACKAGE unless this script has special code to handle it.
for arg
do
# Handle --exec-prefix with a space before the argument.
if test x$next_exec_prefix = xyes; then exec_prefix=$arg; next_exec_prefix=
# Handle --host with a space before the argument.
elif test x$next_host = xyes; then next_host=
# Handle --prefix with a space before the argument.
elif test x$next_prefix = xyes; then prefix=$arg; next_prefix=
# Handle --srcdir with a space before the argument.
elif test x$next_srcdir = xyes; then srcdir=$arg; next_srcdir=
else
case $arg in
# For backward compatibility, also recognize exact --exec_prefix.
-exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* | --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* | --exec=* | --exe=* | --ex=* | --e=*)
exec_prefix=`echo $arg | sed 's/[-a-z_]*=//'` ;;
-exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi | --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- | --exec | --exe | --ex | --e)
next_exec_prefix=yes ;;
-gas | --gas | --ga | --g) ;;
-host=* | --host=* | --hos=* | --ho=* | --h=*) ;;
-host | --host | --hos | --ho | --h)
next_host=yes ;;
-nfp | --nfp | --nf) ;;
-no-create | --no-create | --no-creat | --no-crea | --no-cre | --no-cr | --no-c | --no- | --no)
no_create=1 ;;
-prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*)
prefix=`echo $arg | sed 's/[-a-z_]*=//'` ;;
-prefix | --prefix | --prefi | --pref | --pre | --pr | --p)
next_prefix=yes ;;
-srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=* | --s=*)
srcdir=`echo $arg | sed 's/[-a-z_]*=//'` ;;
-srcdir | --srcdir | --srcdi | --srcd | --src | --sr | --s)
next_srcdir=yes ;;
-with-* | --with-*)
package=`echo $arg|sed 's/-*with-//'`
# Delete all the valid chars; see if any are left.
if test -n "`echo $package|sed 's/[-a-zA-Z0-9_]*//g'`"; then
echo "configure: $package: invalid package name" >&2; exit 1
fi
eval "with_`echo $package|sed s/-/_/g`=1" ;;
-v | -verbose | --verbose | --verbos | --verbo | --verb | --ver | --ve | --v)
verbose=yes ;;
*) ;;
esac
fi
done
trap 'rm -f conftest* core; exit 1' 1 3 15
rm -f conftest*
compile='${CC-cc} $CFLAGS $DEFS conftest.c -o conftest $LIBS >/dev/null 2>&1'
# A filename unique to this package, relative to the directory that
# configure is in, which we can look for to find out if srcdir is correct.
unique_file=termcap.h
# Find the source files, if location was not specified.
if test -z "$srcdir"; then
srcdirdefaulted=yes
# Try the directory containing this script, then `..'.
prog=$0
confdir=`echo $prog|sed 's%/[^/][^/]*$%%'`
test "X$confdir" = "X$prog" && confdir=.
srcdir=$confdir
if test ! -r $srcdir/$unique_file; then
srcdir=..
fi
fi
if test ! -r $srcdir/$unique_file; then
if test x$srcdirdefaulted = xyes; then
echo "configure: Can not find sources in \`${confdir}' or \`..'." 1>&2
else
echo "configure: Can not find sources in \`${srcdir}'." 1>&2
fi
exit 1
fi
# Preserve a srcdir of `.' to avoid automounter screwups with pwd.
# But we can't avoid them for `..', to make subdirectories work.
case $srcdir in
.|/*|~*) ;;
*) srcdir=`cd $srcdir; pwd` ;; # Make relative path absolute.
esac
if test -z "$CC"; then
echo checking for gcc
saveifs="$IFS"; IFS="${IFS}:"
for dir in $PATH; do
test -z "$dir" && dir=.
if test -f $dir/gcc; then
CC="gcc"
break
fi
done
IFS="$saveifs"
fi
test -z "$CC" && CC="cc"
# Find out if we are using GNU C, under whatever name.
cat > conftest.c <<EOF
#ifdef __GNUC__
yes
#endif
EOF
${CC-cc} -E conftest.c > conftest.out 2>&1
if egrep yes conftest.out >/dev/null 2>&1; then
GCC=1 # For later tests.
fi
rm -f conftest*
echo checking how to run the C preprocessor
if test -z "$CPP"; then
CPP='${CC-cc} -E'
cat > conftest.c <<EOF
#include <stdio.h>
EOF
err=`eval "($CPP $DEFS conftest.c >/dev/null) 2>&1"`
if test -z "$err"; then
:
else
CPP=/lib/cpp
fi
rm -f conftest*
fi
# Make sure to not get the incompatible SysV /etc/install and
# /usr/sbin/install, which might be in PATH before a BSD-like install,
# or the SunOS /usr/etc/install directory, or the AIX /bin/install,
# or the AFS install, which mishandles nonexistent args. (Sigh.)
if test -z "$INSTALL"; then
echo checking for install
saveifs="$IFS"; IFS="${IFS}:"
for dir in $PATH; do
test -z "$dir" && dir=.
case $dir in
/etc|/usr/sbin|/usr/etc|/usr/afsws/bin) ;;
*)
if test -f $dir/installbsd; then
INSTALL="$dir/installbsd -c" # OSF1
INSTALL_PROGRAM='$(INSTALL)'
INSTALL_DATA='$(INSTALL) -m 644'
break
fi
if test -f $dir/install; then
if grep dspmsg $dir/install >/dev/null 2>&1; then
: # AIX
else
INSTALL="$dir/install -c"
INSTALL_PROGRAM='$(INSTALL)'
INSTALL_DATA='$(INSTALL) -m 644'
break
fi
fi
;;
esac
done
IFS="$saveifs"
fi
INSTALL=${INSTALL-cp}
INSTALL_PROGRAM=${INSTALL_PROGRAM-'$(INSTALL)'}
INSTALL_DATA=${INSTALL_DATA-'$(INSTALL)'}
for hdr in string.h
do
trhdr=HAVE_`echo $hdr | tr '[a-z]./' '[A-Z]__'`
echo checking for ${hdr}
cat > conftest.c <<EOF
#include <${hdr}>
EOF
err=`eval "($CPP $DEFS conftest.c >/dev/null) 2>&1"`
if test -z "$err"; then
{
test -n "$verbose" && \
echo ' defining' ${trhdr}
DEFS="$DEFS -D${trhdr}=1"
}
fi
rm -f conftest*
done
echo checking for unistd.h
cat > conftest.c <<EOF
#include <unistd.h>
EOF
err=`eval "($CPP $DEFS conftest.c >/dev/null) 2>&1"`
if test -z "$err"; then
{
test -n "$verbose" && \
echo ' defining' HAVE_UNISTD_H
DEFS="$DEFS -DHAVE_UNISTD_H=1"
}
fi
rm -f conftest*
echo checking for ANSI C header files
cat > conftest.c <<EOF
#include <stdlib.h>
#include <stdarg.h>
#include <string.h>
#include <float.h>
EOF
err=`eval "($CPP $DEFS conftest.c >/dev/null) 2>&1"`
if test -z "$err"; then
# SunOS 4.x string.h does not declare mem*, contrary to ANSI.
echo '#include <string.h>' > conftest.c
eval "$CPP $DEFS conftest.c > conftest.out 2>&1"
if egrep "memchr" conftest.out >/dev/null 2>&1; then
# SGI's /bin/cc from Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi.
cat > conftest.c <<EOF
#include <ctype.h>
#define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
#define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c))
#define XOR(e,f) (((e) && !(f)) || (!(e) && (f)))
int main () { int i; for (i = 0; i < 256; i++)
if (XOR (islower (i), ISLOWER (i)) || toupper (i) != TOUPPER (i)) exit(2);
exit (0); }
EOF
eval $compile
if test -s conftest && (./conftest; exit) 2>/dev/null; then
{
test -n "$verbose" && \
echo ' defining' STDC_HEADERS
DEFS="$DEFS -DSTDC_HEADERS=1"
}
fi
rm -f conftest*
fi
rm -f conftest*
fi
rm -f conftest*
if test -n "$prefix"; then
test -z "$exec_prefix" && exec_prefix='${prefix}'
prsub="s%^prefix\\([ ]*\\)=\\([ ]*\\).*$%prefix\\1=\\2$prefix%"
fi
if test -n "$exec_prefix"; then
prsub="$prsub
s%^exec_prefix\\([ ]*\\)=\\([ ]*\\).*$%\
exec_prefix\\1=\\2$exec_prefix%"
fi
trap 'rm -f config.status; exit 1' 1 3 15
echo creating config.status
rm -f config.status
cat > config.status <<EOF
#!/bin/sh
# Generated automatically by configure.
# Run this file to recreate the current configuration.
# This directory was configured as follows,
# on host `(hostname || uname -n) 2>/dev/null | sed 1q`:
#
# $0 $*
for arg
do
case "\$arg" in
-recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
exec /bin/sh $0 $* ;;
*) echo "Usage: config.status --recheck" 2>&1; exit 1 ;;
esac
done
trap 'rm -f Makefile; exit 1' 1 3 15
PROGS='$PROGS'
CC='$CC'
CPP='$CPP'
INSTALL='$INSTALL'
INSTALL_PROGRAM='$INSTALL_PROGRAM'
INSTALL_DATA='$INSTALL_DATA'
LIBS='$LIBS'
srcdir='$srcdir'
DEFS='$DEFS'
prefix='$prefix'
exec_prefix='$exec_prefix'
prsub='$prsub'
EOF
cat >> config.status <<\EOF
top_srcdir=$srcdir
for file in .. Makefile; do if [ "x$file" != "x.." ]; then
srcdir=$top_srcdir
# Remove last slash and all that follows it. Not all systems have dirname.
dir=`echo $file|sed 's%/[^/][^/]*$%%'`
if test "$dir" != "$file"; then
test "$top_srcdir" != . && srcdir=$top_srcdir/$dir
test ! -d $dir && mkdir $dir
fi
echo creating $file
rm -f $file
echo "# Generated automatically from `echo $file|sed 's|.*/||'`.in by configure." > $file
sed -e "
$prsub
s%@PROGS@%$PROGS%g
s%@CC@%$CC%g
s%@CPP@%$CPP%g
s%@INSTALL@%$INSTALL%g
s%@INSTALL_PROGRAM@%$INSTALL_PROGRAM%g
s%@INSTALL_DATA@%$INSTALL_DATA%g
s%@LIBS@%$LIBS%g
s%@srcdir@%$srcdir%g
s%@DEFS@%$DEFS%
" $top_srcdir/${file}.in >> $file
fi; done
exit 0
EOF
chmod +x config.status
test -n "$no_create" || ./config.status

10
lib/termcap/grot/configure.in Normal file
View file

@ -0,0 +1,10 @@
dnl Process this file with autoconf to produce a configure script.
AC_INIT(termcap.h)
AC_SUBST(PROGS)dnl
AC_PROG_CC
AC_PROG_CPP
AC_PROG_INSTALL
AC_HAVE_HEADERS(string.h)
AC_UNISTD_H
AC_STDC_HEADERS
AC_OUTPUT(Makefile)

80
lib/termcap/grot/termcap.info Normal file
View file

@ -0,0 +1,80 @@
This is Info file /home/gd/gnu/termcap/termcap.info, produced by
Makeinfo-1.52 from the input file /home/gd/gnu/termcap/termcap.texi.
This file documents the termcap library of the GNU system.
Copyright (C) 1988 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of
this manual under the conditions for verbatim copying, provided that
the entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
versions, except that this permission notice may be stated in a
translation approved by the Foundation.

Indirect:
termcap.info-1: 912
termcap.info-2: 47539
termcap.info-3: 90314
termcap.info-4: 138449

Tag Table:
(Indirect)
Node: Top912
Node: Introduction4143
Node: Library5870
Node: Preparation6889
Node: Find8072
Node: Interrogate11620
Node: Initialize16928
Node: Padding18568
Node: Why Pad19274
Node: Not Enough20896
Node: Describe Padding23464
Node: Output Padding24954
Node: Parameters28569
Node: Encode Parameters30229
Node: Using Parameters36313
Node: tparam36908
Node: tgoto38934
Node: Data Base41489
Node: Format42385
Node: Capability Format44474
Node: Naming47539
Node: Inheriting52108
Node: Changing54352
Node: Capabilities55516
Node: Basic58255
Node: Screen Size62308
Node: Cursor Motion64048
Node: Wrapping74190
Node: Scrolling77015
Node: Windows82904
Node: Clearing83638
Node: Insdel Line85402
Node: Insdel Char90314
Node: Standout100299
Node: Underlining109357
Node: Cursor Visibility111776
Node: Bell112524
Node: Keypad113073
Node: Meta Key117794
Node: Initialization118748
Node: Pad Specs121112
Node: Status Line123165
Node: Half-Line125049
Node: Printer125851
Node: Summary127530
Node: Var Index137736
Node: Cap Index138449
Node: Index145507

End Tag Table

1115
lib/termcap/grot/termcap.info-1 Normal file
View file

File diff suppressed because it is too large Load diff

969
lib/termcap/grot/termcap.info-2 Normal file
View file

@ -0,0 +1,969 @@
This is Info file /home/gd/gnu/termcap/termcap.info, produced by
Makeinfo-1.52 from the input file /home/gd/gnu/termcap/termcap.texi.
This file documents the termcap library of the GNU system.
Copyright (C) 1988 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of
this manual under the conditions for verbatim copying, provided that
the entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
versions, except that this permission notice may be stated in a
translation approved by the Foundation.

File: termcap.info, Node: Naming, Next: Inheriting, Prev: Capability Format, Up: Data Base
Terminal Type Name Conventions
==============================
There are conventions for choosing names of terminal types. For one
thing, all letters should be in lower case. The terminal type for a
terminal in its most usual or most fundamental mode of operation should
not have a hyphen in it.
If the same terminal has other modes of operation which require
different terminal descriptions, these variant descriptions are given
names made by adding suffixes with hyphens. Such alternate descriptions
are used for two reasons:
* When the terminal has a switch that changes its behavior. Since
the computer cannot tell how the switch is set, the user must tell
the computer by choosing the appropriate terminal type name.
For example, the VT-100 has a setup flag that controls whether the
cursor wraps at the right margin. If this flag is set to "wrap",
you must use the terminal type `vt100-am'. Otherwise you must use
`vt100-nam'. Plain `vt100' is defined as a synonym for either
`vt100-am' or `vt100-nam' depending on the preferences of the
local site.
The standard suffix `-am' stands for "automatic margins".
* To give the user a choice in how to use the terminal. This is done
when the terminal has a switch that the computer normally controls.
For example, the Ann Arbor Ambassador can be configured with many
screen sizes ranging from 20 to 60 lines. Fewer lines make bigger
characters but more lines let you see more of what you are editing.
As a result, users have different preferences. Therefore, termcap
provides terminal types for many screen sizes. If you choose type
`aaa-30', the terminal will be configured to use 30 lines; if you
choose `aaa-48', 48 lines will be used, and so on.
Here is a list of standard suffixes and their conventional meanings:
`-w'
Short for "wide". This is a mode that gives the terminal more
columns than usual. This is normally a user option.
`-am'
"Automatic margins". This is an alternate description for use when
the terminal's margin-wrap switch is on; it contains the `am'
flag. The implication is that normally the switch is off and the
usual description for the terminal says that the switch is off.
`-nam'
"No automatic margins". The opposite of `-am', this names an
alternative description which lacks the `am' flag. This implies
that the terminal is normally operated with the margin-wrap switch
turned on, and the normal description of the terminal says so.
`-na'
"No arrows". This terminal description initializes the terminal to
keep its arrow keys in local mode. This is a user option.
`-rv'
"Reverse video". This terminal description causes text output for
normal video to appear as reverse, and text output for reverse
video to come out as normal. Often this description differs from
the usual one by interchanging the two strings which turn reverse
video on and off.
This is a user option; you can choose either the "reverse video"
variant terminal type or the normal terminal type, and termcap will
obey.
`-s'
"Status". Says to enable use of a status line which ordinary
output does not touch (*note Status Line::.).
Some terminals have a special line that is used only as a status
line. For these terminals, there is no need for an `-s' variant;
the status line commands should be defined by default. On other
terminals, enabling a status line means removing one screen line
from ordinary use and reducing the effective screen height. For
these terminals, the user can choose the `-s' variant type to
request use of a status line.
`-NLINES'
Says to operate with NLINES lines on the screen, for terminals
such as the Ambassador which provide this as an option. Normally
this is a user option; by choosing the terminal type, you control
how many lines termcap will use.
`-NPAGESp'
Says that the terminal has NPAGES pages worth of screen memory,
for terminals where this is a hardware option.
`-unk'
Says that description is not for direct use, but only for
reference in `tc' capabilities. Such a description is a kind of
subroutine, because it describes the common characteristics of
several variant descriptions that would use other suffixes in
place of `-unk'.

File: termcap.info, Node: Inheriting, Next: Changing, Prev: Naming, Up: Data Base
Inheriting from Related Descriptions
====================================
When two terminal descriptions are similar, their identical parts do
not need to be given twice. Instead, one of the two can be defined in
terms of the other, using the `tc' capability. We say that one
description "refers to" the other, or "inherits from" the other.
The `tc' capability must be the last one in the terminal description,
and its value is a string which is the name of another terminal type
which is referred to. For example,
N9|aaa|ambassador|aaa-30|ann arbor ambassador/30 lines:\
:ti=\E[2J\E[30;0;0;30p:\
:te=\E[60;0;0;30p\E[30;1H\E[J:\
:li#30:tc=aaa-unk:
defines the terminal type `aaa-30' (also known as plain `aaa') in terms
of `aaa-unk', which defines everything about the Ambassador that is
independent of screen height. The types `aaa-36', `aaa-48' and so on
for other screen heights are likewise defined to inherit from `aaa-unk'.
The capabilities overridden by `aaa-30' include `li', which says how
many lines there are, and `ti' and `te', which configure the terminal
to use that many lines.
The effective terminal description for type `aaa' consists of the
text shown above followed by the text of the description of `aaa-unk'.
The `tc' capability is handled automatically by `tgetent', which finds
the description thus referenced and combines the two descriptions
(*note Find::.). Therefore, only the implementor of the terminal
descriptions needs to think about using `tc'. Users and application
programmers do not need to be concerned with it.
Since the reference terminal description is used last, capabilities
specified in the referring description override any specifications of
the same capabilities in the reference description.
The referring description can cancel out a capability without
specifying any new value for it by means of a special trick. Write the
capability in the referring description, with the character `@' after
the capability name, as follows:
NZ|aaa-30-nam|ann arbor ambassador/30 lines/no automatic-margins:\
:am@:tc=aaa-30:

File: termcap.info, Node: Changing, Prev: Inheriting, Up: Data Base
When Changes in the Data Base Take Effect
=========================================
Each application program must read the terminal description from the
data base, so a change in the data base is effective for all jobs
started after the change is made.
The change will usually have no effect on a job that have been in
existence since before the change. The program probably read the
terminal description once, when it was started, and is continuing to
use what it read then. If the program does not have a feature for
reexamining the data base, then you will need to run it again (probably
killing the old job).
If the description in use is coming from the `TERMCAP' environment
variable, then the data base file is effectively overridden, and
changes in it will have no effect until you change the `TERMCAP'
variable as well. For example, some users' `.login' files
automatically copy the terminal description into `TERMCAP' to speed
startup of applications. If you have done this, you will need to
change the `TERMCAP' variable to make the changed data base take effect.

File: termcap.info, Node: Capabilities, Next: Summary, Prev: Data Base, Up: Top
Definitions of the Terminal Capabilities
****************************************
This section is divided into many subsections, each for one aspect of
use of display terminals. For writing a display program, you usually
need only check the subsections for the operations you want to use.
For writing a terminal description, you must read each subsection and
fill in the capabilities described there.
String capabilities that are display commands may require numeric
parameters (*note Parameters::.). Most such capabilities do not use
parameters. When a capability requires parameters, this is explicitly
stated at the beginning of its definition. In simple cases, the first
or second sentence of the definition mentions all the parameters, in
the order they should be given, using a name in upper case for each
one. For example, the `rp' capability is a command that requires two
parameters; its definition begins as follows:
String of commands to output a graphic character C, repeated N
times.
In complex cases or when there are many parameters, they are
described explicitly.
When a capability is described as obsolete, this means that programs
should not be written to look for it, but terminal descriptions should
still be written to provide it.
When a capability is described as very obsolete, this means that it
should be omitted from terminal descriptions as well.
* Menu:
* Basic:: Basic characteristics.
* Screen Size:: Screen size, and what happens when it changes.
* Cursor Motion:: Various ways to move the cursor.
* Wrapping:: What happens if you write a character in the last column.
* Scrolling:: Pushing text up and down on the screen.
* Windows:: Limiting the part of the window that output affects.
* Clearing:: Erasing one or many lines.
* Insdel Line:: Making new blank lines in mid-screen; deleting lines.
* Insdel Char:: Inserting and deleting characters within a line.
* Standout:: Highlighting some of the text.
* Underlining:: Underlining some of the text.
* Cursor Visibility:: Making the cursor more or less easy to spot.
* Bell:: Attracts user's attention; not localized on the screen.
* Keypad:: Recognizing when function keys or arrows are typed.
* Meta Key:: META acts like an extra shift key.
* Initialization:: Commands used to initialize or reset the terminal.
* Pad Specs:: Info for the kernel on how much padding is needed.
* Status Line:: A status line displays "background" information.
* Half-Line:: Moving by half-lines, for superscripts and subscripts.
* Printer:: Controlling auxiliary printers of display terminals.

File: termcap.info, Node: Basic, Next: Screen Size, Up: Capabilities
Basic Characteristics
=====================
This section documents the capabilities that describe the basic and
nature of the terminal, and also those that are relevant to the output
of graphic characters.
`os'
Flag whose presence means that the terminal can overstrike. This
means that outputting a graphic character does not erase whatever
was present in the same character position before. The terminals
that can overstrike include printing terminals, storage tubes (all
obsolete nowadays), and many bit-map displays.
`eo'
Flag whose presence means that outputting a space erases a
character position even if the terminal supports overstriking. If
this flag is not present and overstriking is supported, output of
a space has no effect except to move the cursor.
(On terminals that do not support overstriking, you can always
assume that outputting a space at a position erases whatever
character was previously displayed there.)
`gn'
Flag whose presence means that this terminal type is a generic type
which does not really describe any particular terminal. Generic
types are intended for use as the default type assigned when the
user connects to the system, with the intention that the user
should specify what type he really has. One example of a generic
type is the type `network'.
Since the generic type cannot say how to do anything interesting
with the terminal, termcap-using programs will always find that the
terminal is too weak to be supported if the user has failed to
specify a real terminal type in place of the generic one. The
`gn' flag directs these programs to use a different error message:
"You have not specified your real terminal type", rather than
"Your terminal is not powerful enough to be used".
`hc'
Flag whose presence means this is a hardcopy terminal.
`rp'
String of commands to output a graphic character C, repeated N
times. The first parameter value is the ASCII code for the desired
character, and the second parameter is the number of times to
repeat the character. Often this command requires padding
proportional to the number of times the character is repeated.
This effect can be had by using parameter arithmetic with
`%'-sequences to compute the amount of padding, then generating
the result as a number at the front of the string so that `tputs'
will treat it as padding.
`hz'
Flag whose presence means that the ASCII character `~' cannot be
output on this terminal because it is used for display commands.
Programs handle this flag by checking all text to be output and
replacing each `~' with some other character(s). If this is not
done, the screen will be thoroughly garbled.
The old Hazeltine terminals that required such treatment are
probably very rare today, so you might as well not bother to
support this flag.
`CC'
String whose presence means the terminal has a settable command
character. The value of the string is the default command
character (which is usually ESC).
All the strings of commands in the terminal description should be
written to use the default command character. If you are writing
an application program that changes the command character, use the
`CC' capability to figure out how to translate all the display
commands to work with the new command character.
Most programs have no reason to look at the `CC' capability.
`xb'
Flag whose presence identifies Superbee terminals which are unable
to transmit the characters ESC and `Control-C'. Programs which
support this flag are supposed to check the input for the code
sequences sent by the F1 and F2 keys, and pretend that ESC or
`Control-C' (respectively) had been read. But this flag is
obsolete, and not worth supporting.

File: termcap.info, Node: Screen Size, Next: Cursor Motion, Prev: Basic, Up: Capabilities
Screen Size
===========
A terminal description has two capabilities, `co' and `li', that
describe the screen size in columns and lines. But there is more to
the question of screen size than this.
On some operating systems the "screen" is really a window and the
effective width can vary. On some of these systems, `tgetnum' uses the
actual width of the window to decide what value to return for the `co'
capability, overriding what is actually written in the terminal
description. On other systems, it is up to the application program to
check the actual window width using a system call. For example, on BSD
4.3 systems, the system call `ioctl' with code `TIOCGWINSZ' will tell
you the current screen size.
On all window systems, termcap is powerless to advise the application
program if the user resizes the window. Application programs must deal
with this possibility in a system-dependent fashion. On some systems
the C shell handles part of the problem by detecting changes in window
size and setting the `TERMCAP' environment variable appropriately.
This takes care of application programs that are started subsequently.
It does not help application programs already running.
On some systems, including BSD 4.3, all programs using a terminal get
a signal named `SIGWINCH' whenever the screen size changes. Programs
that use termcap should handle this signal by using `ioctl TIOCGWINSZ'
to learn the new screen size.
`co'
Numeric value, the width of the screen in character positions.
Even hardcopy terminals normally have a `co' capability.
`li'
Numeric value, the height of the screen in lines.

File: termcap.info, Node: Cursor Motion, Next: Wrapping, Prev: Screen Size, Up: Capabilities
Cursor Motion
=============
Termcap assumes that the terminal has a "cursor", a spot on the
screen where a visible mark is displayed, and that most display
commands take effect at the position of the cursor. It follows that
moving the cursor to a specified location is very important.
There are many terminal capabilities for different cursor motion
operations. A terminal description should define as many as possible,
but most programs do not need to use most of them. One capability,
`cm', moves the cursor to an arbitrary place on the screen; this by
itself is sufficient for any application as long as there is no need to
support hardcopy terminals or certain old, weak displays that have only
relative motion commands. Use of other cursor motion capabilities is an
optimization, enabling the program to output fewer characters in some
common cases.
If you plan to use the relative cursor motion commands in an
application program, you must know what the starting cursor position
is. To do this, you must keep track of the cursor position and update
the records each time anything is output to the terminal, including
graphic characters. In addition, it is necessary to know whether the
terminal wraps after writing in the rightmost column. *Note Wrapping::.
One other motion capability needs special mention: `nw' moves the
cursor to the beginning of the following line, perhaps clearing all the
starting line after the cursor, or perhaps not clearing at all. This
capability is a least common denominator that is probably supported
even by terminals that cannot do most other things such as `cm' or `do'.
Even hardcopy terminals can support `nw'.
`cm'
String of commands to position the cursor at line L, column C.
Both parameters are origin-zero, and are defined relative to the
screen, not relative to display memory.
All display terminals except a few very obsolete ones support `cm',
so it is acceptable for an application program to refuse to
operate on terminals lacking `cm'.
`ho'
String of commands to move the cursor to the upper left corner of
the screen (this position is called the "home position"). In
terminals where the upper left corner of the screen is not the
same as the beginning of display memory, this command must go to
the upper left corner of the screen, not the beginning of display
memory.
Every display terminal supports this capability, and many
application programs refuse to operate if the `ho' capability is
missing.
`ll'
String of commands to move the cursor to the lower left corner of
the screen. On some terminals, moving up from home position does
this, but programs should never assume that will work. Just
output the `ll' string (if it is provided); if moving to home
position and then moving up is the best way to get there, the `ll'
command will do that.
`cr'
String of commands to move the cursor to the beginning of the line
it is on. If this capability is not specified, many programs
assume they can use the ASCII carriage return character for this.
`le'
String of commands to move the cursor left one column. Unless the
`bw' flag capability is specified, the effect is undefined if the
cursor is at the left margin; do not use this command there. If
`bw' is present, this command may be used at the left margin, and
it wraps the cursor to the last column of the preceding line.
`nd'
String of commands to move the cursor right one column. The
effect is undefined if the cursor is at the right margin; do not
use this command there, not even if `am' is present.
`up'
String of commands to move the cursor vertically up one line. The
effect of sending this string when on the top line is undefined;
programs should never use it that way.
`do'
String of commands to move the cursor vertically down one line.
The effect of sending this string when on the bottom line is
undefined; programs should never use it that way.
Some programs do use `do' to scroll up one line if used at the
bottom line, if `sf' is not defined but `sr' is. This is only to
compensate for certain old, incorrect terminal descriptions. (In
principle this might actually lead to incorrect behavior on other
terminals, but that seems to happen rarely if ever.) But the
proper solution is that the terminal description should define
`sf' as well as `do' if the command is suitable for scrolling.
The original idea was that this string would not contain a newline
character and therefore could be used without disabling the
kernel's usual habit of converting of newline into a
carriage-return newline sequence. But many terminal descriptions
do use newline in the `do' string, so this is not possible; a
program which sends the `do' string must disable output conversion
in the kernel (*note Initialize::.).
`bw'
Flag whose presence says that `le' may be used in column zero to
move to the last column of the preceding line. If this flag is
not present, `le' should not be used in column zero.
`nw'
String of commands to move the cursor to start of next line,
possibly clearing rest of line (following the cursor) before
moving.
`DO', `UP', `LE', `RI'
Strings of commands to move the cursor N lines down vertically, up
vertically, or N columns left or right. Do not attempt to move
past any edge of the screen with these commands; the effect of
trying that is undefined. Only a few terminal descriptions provide
these commands, and most programs do not use them.
`CM'
String of commands to position the cursor at line L, column C,
relative to display memory. Both parameters are origin-zero.
This capability is present only in terminals where there is a
difference between screen-relative and memory-relative addressing,
and not even in all such terminals.
`ch'
String of commands to position the cursor at column C in the same
line it is on. This is a special case of `cm' in which the
vertical position is not changed. The `ch' capability is provided
only when it is faster to output than `cm' would be in this
special case. Programs should not assume most display terminals
have `ch'.
`cv'
String of commands to position the cursor at line L in the same
column. This is a special case of `cm' in which the horizontal
position is not changed. The `cv' capability is provided only
when it is faster to output than `cm' would be in this special
case. Programs should not assume most display terminals have `cv'.
`sc'
String of commands to make the terminal save the current cursor
position. Only the last saved position can be used. If this
capability is present, `rc' should be provided also. Most
terminals have neither.
`rc'
String of commands to make the terminal restore the last saved
cursor position. If this capability is present, `sc' should be
provided also. Most terminals have neither.
`ff'
String of commands to advance to the next page, for a hardcopy
terminal.
`ta'
String of commands to move the cursor right to the next hardware
tab stop column. Missing if the terminal does not have any kind of
hardware tabs. Do not send this command if the kernel's terminal
modes say that the kernel is expanding tabs into spaces.
`bt'
String of commands to move the cursor left to the previous hardware
tab stop column. Missing if the terminal has no such ability; many
terminals do not. Do not send this command if the kernel's
terminal modes say that the kernel is expanding tabs into spaces.
The following obsolete capabilities should be included in terminal
descriptions when appropriate, but should not be looked at by new
programs.
`nc'
Flag whose presence means the terminal does not support the ASCII
carriage return character as `cr'. This flag is needed because
old programs assume, when the `cr' capability is missing, that
ASCII carriage return can be used for the purpose. We use `nc' to
tell the old programs that carriage return may not be used.
New programs should not assume any default for `cr', so they need
not look at `nc'. However, descriptions should contain `nc'
whenever they do not contain `cr'.
`xt'
Flag whose presence means that the ASCII tab character may not be
used for cursor motion. This flag exists because old programs
assume, when the `ta' capability is missing, that ASCII tab can be
used for the purpose. We use `xt' to tell the old programs not to
use tab.
New programs should not assume any default for `ta', so they need
not look at `xt' in connection with cursor motion. Note that `xt'
also has implications for standout mode (*note Standout::.). It
is obsolete in regard to cursor motion but not in regard to
standout.
In fact, `xt' means that the terminal is a Teleray 1061.
`bc'
Very obsolete alternative name for the `le' capability.
`bs'
Flag whose presence means that the ASCII character backspace may be
used to move the cursor left. Obsolete; look at `le' instead.
`nl'
Obsolete capability which is a string that can either be used to
move the cursor down or to scroll. The same string must scroll
when used on the bottom line and move the cursor when used on any
other line. New programs should use `do' or `sf', and ignore `nl'.
If there is no `nl' capability, some old programs assume they can
use the newline character for this purpose. These programs follow
a bad practice, but because they exist, it is still desirable to
define the `nl' capability in a terminal description if the best
way to move down is *not* a newline.

File: termcap.info, Node: Wrapping, Next: Scrolling, Prev: Cursor Motion, Up: Capabilities
Wrapping
========
"Wrapping" means moving the cursor from the right margin to the left
margin of the following line. Some terminals wrap automatically when a
graphic character is output in the last column, while others do not.
Most application programs that use termcap need to know whether the
terminal wraps. There are two special flag capabilities to describe
what the terminal does when a graphic character is output in the last
column.
`am'
Flag whose presence means that writing a character in the last
column causes the cursor to wrap to the beginning of the next line.
If `am' is not present, writing in the last column leaves the
cursor at the place where the character was written.
Writing in the last column of the last line should be avoided on
terminals with `am', as it may or may not cause scrolling to occur
(*note Scrolling::.). Scrolling is surely not what you would
intend.
If your program needs to check the `am' flag, then it also needs
to check the `xn' flag which indicates that wrapping happens in a
strange way. Many common terminals have the `xn' flag.
`xn'
Flag whose presence means that the cursor wraps in a strange way.
At least two distinct kinds of strange behavior are known; the
termcap data base does not contain anything to distinguish the two.
On Concept-100 terminals, output in the last column wraps the
cursor almost like an ordinary `am' terminal. But if the next
thing output is a newline, it is ignored.
DEC VT-100 terminals (when the wrap switch is on) do a different
strange thing: the cursor wraps only if the next thing output is
another graphic character. In fact, the wrap occurs when the
following graphic character is received by the terminal, before the
character is placed on the screen.
On both of these terminals, after writing in the last column a
following graphic character will be displayed in the first column
of the following line. But the effect of relative cursor motion
characters such as newline or backspace at such a time depends on
the terminal. The effect of erase or scrolling commands also
depends on the terminal. You can't assume anything about what
they will do on a terminal that has `xn'. So, to be safe, you
should never do these things at such a time on such a terminal.
To be sure of reliable results on a terminal which has the `xn'
flag, output a `cm' absolute positioning command after writing in
the last column. Another safe thing to do is to output
carriage-return newline, which will leave the cursor at the
beginning of the following line.

File: termcap.info, Node: Scrolling, Next: Windows, Prev: Wrapping, Up: Capabilities
Scrolling
=========
"Scrolling" means moving the contents of the screen up or down one or
more lines. Moving the contents up is "forward scrolling"; moving them
down is "reverse scrolling".
Scrolling happens after each line of output during ordinary output
on most display terminals. But in an application program that uses
termcap for random-access output, scrolling happens only when
explicitly requested with the commands in this section.
Some terminals have a "scroll region" feature. This lets you limit
the effect of scrolling to a specified range of lines. Lines outside
the range are unaffected when scrolling happens. The scroll region
feature is available if either `cs' or `cS' is present.
`sf'
String of commands to scroll the screen one line up, assuming it is
output with the cursor at the beginning of the bottom line.
`sr'
String of commands to scroll the screen one line down, assuming it
is output with the cursor at the beginning of the top line.
`do'
A few programs will try to use `do' to do the work of `sf'. This
is not really correct--it is an attempt to compensate for the
absence of a `sf' command in some old terminal descriptions.
Since these terminal descriptions do define `sr', perhaps at one
time the definition of `do' was different and it could be used for
scrolling as well. But it isn't desirable to combine these two
functions in one capability, since scrolling often requires more
padding than simply moving the cursor down. Defining `sf' and
`do' separately allows you to specify the padding properly. Also,
all sources agree that `do' should not be relied on to do
scrolling.
So the best approach is to add `sf' capabilities to the
descriptions of these terminals, copying the definition of `do' if
that does scroll.
`SF'
String of commands to scroll the screen N lines up, assuming it is
output with the cursor at the beginning of the bottom line.
`SR'
String of commands to scroll the screen N lines down, assuming it
is output with the cursor at the beginning of the top line.
`cs'
String of commands to set the scroll region. This command takes
two parameters, START and END, which are the line numbers
(origin-zero) of the first line to include in the scroll region
and of the last line to include in it. When a scroll region is
set, scrolling is limited to the specified range of lines; lines
outside the range are not affected by scroll commands.
Do not try to move the cursor outside the scroll region. The
region remains set until explicitly removed. To remove the scroll
region, use another `cs' command specifying the full height of the
screen.
The cursor position is undefined after the `cs' command is set, so
position the cursor with `cm' immediately afterward.
`cS'
String of commands to set the scroll region using parameters in
different form. The effect is the same as if `cs' were used.
Four parameters are required:
1. Total number of lines on the screen.
2. Number of lines above desired scroll region.
3. Number of lines below (outside of) desired scroll region.
4. Total number of lines on the screen, the same as the first
parameter.
This capability is a GNU extension that was invented to allow the
Ann Arbor Ambassador's scroll-region command to be described; it
could also be done by putting non-Unix `%'-sequences into a `cs'
string, but that would have confused Unix programs that used the
`cs' capability with the Unix termcap. Currently only GNU Emacs
uses the `cS' capability.
`ns'
Flag which means that the terminal does not normally scroll for
ordinary sequential output. For modern terminals, this means that
outputting a newline in ordinary sequential output with the cursor
on the bottom line wraps to the top line. For some obsolete
terminals, other things may happen.
The terminal may be able to scroll even if it does not normally do
so. If the `sf' capability is provided, it can be used for
scrolling regardless of `ns'.
`da'
Flag whose presence means that lines scrolled up off the top of the
screen may come back if scrolling down is done subsequently.
The `da' and `db' flags do not, strictly speaking, affect how to
scroll. But programs that scroll usually need to clear the lines
scrolled onto the screen, if these flags are present.
`db'
Flag whose presence means that lines scrolled down off the bottom
of the screen may come back if scrolling up is done subsequently.
`lm'
Numeric value, the number of lines of display memory that the
terminal has. A value of zero means that the terminal has more
display memory than can fit on the screen, but no fixed number of
lines. (The number of lines may depend on the amount of text in
each line.)
Any terminal description that defines `SF' should also define `sf';
likewise for `SR' and `sr'. However, many terminals can only scroll by
one line at a time, so it is common to find `sf' and not `SF', or `sr'
without `SR'.
Therefore, all programs that use the scrolling facilities should be
prepared to work with `sf' in the case that `SF' is absent, and
likewise with `sr'. On the other hand, an application program that
uses only `sf' and not `SF' is acceptable, though slow on some
terminals.
When outputting a scroll command with `tputs', the NLINES argument
should be the total number of lines in the portion of the screen being
scrolled. Very often these commands require padding proportional to
this number of lines. *Note Padding::.

File: termcap.info, Node: Windows, Next: Clearing, Prev: Scrolling, Up: Capabilities
Windows
=======
A "window", in termcap, is a rectangular portion of the screen to
which all display operations are restricted. Wrapping, clearing,
scrolling, insertion and deletion all operate as if the specified
window were all the screen there was.
`wi'
String of commands to set the terminal output screen window. This
string requires four parameters, all origin-zero:
1. The first line to include in the window.
2. The last line to include in the window.
3. The first column to include in the window.
4. The last column to include in the window.
Most terminals do not support windows.

File: termcap.info, Node: Clearing, Next: Insdel Line, Prev: Windows, Up: Capabilities
Clearing Parts of the Screen
============================
There are several terminal capabilities for clearing parts of the
screen to blank. All display terminals support the `cl' string, and
most display terminals support all of these capabilities.
`cl'
String of commands to clear the entire screen and position the
cursor at the upper left corner.
`cd'
String of commands to clear the line the cursor is on, and all the
lines below it, down to the bottom of the screen. This command
string should be used only with the cursor in column zero; their
effect is undefined if the cursor is elsewhere.
`ce'
String of commands to clear from the cursor to the end of the
current line.
`ec'
String of commands to clear N characters, starting with the
character that the cursor is on. This command string is expected
to leave the cursor position unchanged. The parameter N should
never be large enough to reach past the right margin; the effect
of such a large parameter would be undefined.
Clear to end of line (`ce') is extremely important in programs that
maintain an updating display. Nearly all display terminals support this
operation, so it is acceptable for a an application program to refuse to
work if `ce' is not present. However, if you do not want this
limitation, you can accomplish clearing to end of line by outputting
spaces until you reach the right margin. In order to do this, you must
know the current horizontal position. Also, this technique assumes
that writing a space will erase. But this happens to be true on all
the display terminals that fail to support `ce'.

File: termcap.info, Node: Insdel Line, Next: Insdel Char, Prev: Clearing, Up: Capabilities
Insert/Delete Line
==================
"Inserting a line" means creating a blank line in the middle of the
screen, and pushing the existing lines of text apart. In fact, the
lines above the insertion point do not change, while the lines below
move down, and one is normally lost at the bottom of the screen.
"Deleting a line" means causing the line to disappear from the
screen, closing up the gap by moving the lines below it upward. A new
line appears at the bottom of the screen. Usually this line is blank,
but on terminals with the `db' flag it may be a line previously moved
off the screen bottom by scrolling or line insertion.
Insertion and deletion of lines is useful in programs that maintain
an updating display some parts of which may get longer or shorter.
They are also useful in editors for scrolling parts of the screen, and
for redisplaying after lines of text are killed or inserted.
Many terminals provide commands to insert or delete a single line at
the cursor position. Some provide the ability to insert or delete
several lines with one command, using the number of lines to insert or
delete as a parameter. Always move the cursor to column zero before
using any of these commands.
`al'
String of commands to insert a blank line before the line the
cursor is on. The existing line, and all lines below it, are
moved down. The last line in the screen (or in the scroll region,
if one is set) disappears and in most circumstances is discarded.
It may not be discarded if the `db' is present (*note
Scrolling::.).
The cursor must be at the left margin before this command is used.
This command does not move the cursor.
`dl'
String of commands to delete the line the cursor is on. The
following lines move up, and a blank line appears at the bottom of
the screen (or bottom of the scroll region). If the terminal has
the `db' flag, a nonblank line previously pushed off the screen
bottom may reappear at the bottom.
The cursor must be at the left margin before this command is used.
This command does not move the cursor.
`AL'
String of commands to insert N blank lines before the line that
the cursor is on. It is like `al' repeated N times, except that
it is as fast as one `al'.
`DL'
String of commands to delete N lines starting with the line that
the cursor is on. It is like `dl' repeated N times, except that
it is as fast as one `dl'.
Any terminal description that defines `AL' should also define `al';
likewise for `DL' and `dl'. However, many terminals can only insert or
delete one line at a time, so it is common to find `al' and not `AL',
or `dl' without `DL'.
Therefore, all programs that use the insert and delete facilities
should be prepared to work with `al' in the case that `AL' is absent,
and likewise with `dl'. On the other hand, it is acceptable to write
an application that uses only `al' and `dl' and does not look for `AL'
or `DL' at all.
If a terminal does not support line insertion and deletion directly,
but does support a scroll region, the effect of insertion and deletion
can be obtained with scrolling. However, it is up to the individual
user program to check for this possibility and use the scrolling
commands to get the desired result. It is fairly important to implement
this alternate strategy, since it is the only way to get the effect of
line insertion and deletion on the popular VT100 terminal.
Insertion and deletion of lines is affected by the scroll region on
terminals that have a settable scroll region. This is useful when it is
desirable to move any few consecutive lines up or down by a few lines.
*Note Scrolling::.
The line pushed off the bottom of the screen is not lost if the
terminal has the `db' flag capability; instead, it is pushed into
display memory that does not appear on the screen. This is the same
thing that happens when scrolling pushes a line off the bottom of the
screen. Either reverse scrolling or deletion of a line can bring the
apparently lost line back onto the bottom of the screen. If the
terminal has the scroll region feature as well as `db', the pushed-out
line really is lost if a scroll region is in effect.
When outputting an insert or delete command with `tputs', the NLINES
argument should be the total number of lines from the cursor to the
bottom of the screen (or scroll region). Very often these commands
require padding proportional to this number of lines. *Note Padding::.
For `AL' and `DL' the NLINES argument should *not* depend on the
number of lines inserted or deleted; only the total number of lines
affected. This is because it is just as fast to insert two or N lines
with `AL' as to insert one line with `al'.

1469
lib/termcap/grot/termcap.info-3 Normal file
View file

File diff suppressed because it is too large Load diff

218
lib/termcap/grot/termcap.info-4 Normal file
View file

@ -0,0 +1,218 @@
This is Info file /home/gd/gnu/termcap/termcap.info, produced by
Makeinfo-1.52 from the input file /home/gd/gnu/termcap/termcap.texi.
This file documents the termcap library of the GNU system.
Copyright (C) 1988 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of
this manual under the conditions for verbatim copying, provided that
the entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
versions, except that this permission notice may be stated in a
translation approved by the Foundation.

File: termcap.info, Node: Cap Index, Next: Index, Prev: Var Index, Up: Top
Capability Index
****************
* Menu:
* ae: Standout.
* AL: Insdel Line.
* al: Insdel Line.
* am: Wrapping.
* as: Standout.
* bc: Cursor Motion.
* bl: Bell.
* bs: Cursor Motion.
* bt: Cursor Motion.
* bw: Cursor Motion.
* CC: Basic.
* cd: Clearing.
* ce: Clearing.
* ch: Cursor Motion.
* cl: Clearing.
* CM: Cursor Motion.
* cm: Cursor Motion.
* co: Screen Size.
* cr: Cursor Motion.
* cS: Scrolling.
* cs: Scrolling.
* ct: Initialization.
* cv: Cursor Motion.
* da: Scrolling.
* dB: Pad Specs.
* db: Scrolling.
* dC: Pad Specs.
* DC: Insdel Char.
* dc: Insdel Char.
* dF: Pad Specs.
* dl: Insdel Line.
* DL: Insdel Line.
* dm: Insdel Char.
* dN: Pad Specs.
* DO: Cursor Motion.
* do: Cursor Motion.
* ds: Status Line.
* dT: Pad Specs.
* ec: Clearing.
* ed: Insdel Char.
* ei: Insdel Char.
* eo: Basic.
* es: Status Line.
* ff: Cursor Motion.
* fs: Status Line.
* gn: Basic.
* hc: Basic.
* hd: Half-Line.
* ho: Cursor Motion.
* hs: Status Line.
* hu: Half-Line.
* hz: Basic.
* i1: Initialization.
* i3: Initialization.
* IC: Insdel Char.
* ic: Insdel Char.
* if: Initialization.
* im: Insdel Char.
* in: Insdel Char.
* ip: Insdel Char.
* is: Initialization.
* it: Initialization.
* K1...K5: Keypad.
* k1...k9: Keypad.
* kA...kT: Keypad.
* ka...ku: Keypad.
* km: Meta Key.
* l0...l9: Keypad.
* le: Cursor Motion.
* LE: Cursor Motion.
* li: Screen Size.
* ll: Cursor Motion.
* lm: Scrolling.
* mb: Standout.
* md: Standout.
* me: Standout.
* mh: Standout.
* mi: Insdel Char.
* mk: Standout.
* mm: Meta Key.
* mo: Meta Key.
* mp: Standout.
* mr: Standout.
* ms: Standout.
* ms: Underlining.
* nc: Cursor Motion.
* nd: Cursor Motion.
* nl: Cursor Motion.
* ns: Scrolling.
* nw: Cursor Motion.
* os: Basic.
* pb: Pad Specs.
* pc: Pad Specs.
* pf: Printer.
* pO: Printer.
* po: Printer.
* ps: Printer.
* rc: Cursor Motion.
* RI: Cursor Motion.
* rp: Basic.
* rs: Initialization.
* sa: Standout.
* sc: Cursor Motion.
* se: Standout.
* sf: Scrolling.
* SF: Scrolling.
* sg: Standout.
* so: Standout.
* sr: Scrolling.
* SR: Scrolling.
* st: Initialization.
* ta: Cursor Motion.
* te: Initialization.
* ti: Initialization.
* ts: Status Line.
* uc: Underlining.
* ue: Underlining.
* ug: Underlining.
* ul: Underlining.
* up: Cursor Motion.
* UP: Cursor Motion.
* us: Underlining.
* vb: Bell.
* ve: Cursor Visibility.
* vi: Cursor Visibility.
* vs: Cursor Visibility.
* wi: Windows.
* ws: Status Line.
* xb: Basic.
* xn: Wrapping.
* xs: Standout.
* xt: Standout.
* xt: Cursor Motion.

File: termcap.info, Node: Index, Prev: Cap Index, Up: Top
Concept Index
*************
* Menu:
* %: Encode Parameters.
* appearance modes: Standout.
* bell: Bell.
* clearing the screen: Clearing.
* command character: Basic.
* cursor motion: Cursor Motion.
* delete character: Insdel Char.
* delete line: Insdel Line.
* delete mode: Insdel Char.
* description format: Format.
* erasing: Clearing.
* generic terminal type: Basic.
* home position: Cursor Motion.
* inheritance: Inheriting.
* initialization: Initialization.
* insert character: Insdel Char.
* insert line: Insdel Line.
* insert mode: Insdel Char.
* line speed: Output Padding.
* magic cookie: Standout.
* meta key: Meta Key.
* names of terminal types: Naming.
* overstrike: Basic.
* padding: Pad Specs.
* padding: Padding.
* parameters: Parameters.
* printer: Printer.
* repeat output: Basic.
* reset: Initialization.
* screen size: Screen Size.
* screen size: Screen Size.
* screen size: Naming.
* scrolling: Scrolling.
* standout: Standout.
* status line: Status Line.
* Superbee: Basic.
* tab stops: Initialization.
* termcap: Introduction.
* terminal flags (kernel): Initialize.
* underlining: Underlining.
* visibility: Cursor Visibility.
* visible bell: Bell.
* window: Windows.
* wrapping: Naming.
* wrapping: Wrapping.

3603
lib/termcap/grot/termcap.texi Normal file
View file

File diff suppressed because it is too large Load diff

3941
lib/termcap/grot/texinfo.tex Normal file
View file

File diff suppressed because it is too large Load diff