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

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

Browse source
This commit is contained in:
Jari Aalto 1996-12-23 17:02:34 +00:00
commit ccc6cda312
502 changed files with 91988 additions and 69123 deletions
Download patch file Download diff file Expand all files Collapse all files

89
lib/termcap/grot/ChangeLog
View file

@ -1,3 +1,92 @@
Wed Aug 16 20:45:44 1995 David J. MacKenzie <djm@geech.gnu.ai.mit.edu>
* version.c: Version 1.3.
* termcap.c (tgetent): Use the user-supplied buffer even if we
don't find a matching terminal, so the program can set the buffer
if they want (`less' does this). From Bob Pegram
<pegram@emba.uvm.edu>.
Wed Jul 26 11:44:51 1995 David J. MacKenzie <djm@geech.gnu.ai.mit.edu>
* termcap.c: TERMCAP_NAME -> TERMCAP_FILE.
* configure.in: Add --enable-install-termcap and --with-termcap
options.
* Makefile.in: Add hooks for new configure options.
* Makefile.in (DISTFILES): Add termcap.src.
(DEFS): Remove -DNO_ARG_ARRAY.
(install-data, uninstall-data): New targets.
* tparam.c (tparam): Remove arg array version and the #ifdef.
* termcap.c: Move #define of bcopy to after #include <string.h>.
* termcap.h: Prototype the arg to the tputs outfun arg.
* Makefile.in: realclean -> maintainer-clean. Use @prefix@ and
@exec_prefix@.
* Makefile.in (DISTFILES): Add install-sh.
Fri Apr 7 14:57:45 1995 Richard Stallman <rms@mole.gnu.ai.mit.edu>
* termcap.c (tgetent): Don't try to return the allocated address.
Always return 1 if successful.
Tue Feb 14 02:34:43 1995 Richard Stallman <rms@pogo.gnu.ai.mit.edu>
* termcap.c (speeds): Make it ints. Add some higher speeds.
(tputs) [emacs]: If speed is high, convert to smaller units.
(tputs): Really use SPEED to calculate PADCOUNT.
Sat Dec 17 07:20:24 1994 Richard Stallman <rms@mole.gnu.ai.mit.edu>
* termcap.c (tgetst1): Let ^? stand for DEL character.
Thu Jun 30 04:35:50 1994 Roland McGrath (roland@churchy.gnu.ai.mit.edu)
* configure.in: Use AC_HAVE_HEADERS instead of AC_UNISTD_H.
Add AC_PROG_RANLIB.
* Makefile.in (AR, RANLIB): New variables.
(install, libtermcap.a): Use them instead of hard-wired commands.
Sat Jun 4 12:21:41 1994 Roland McGrath (roland@geech.gnu.ai.mit.edu)
* termcap.c [HAVE_CONFIG_H]: Include <sys/file.h>, and include
<fcntl.h> #ifdef USG5, so we get O_* defns.
Wed May 25 19:05:30 1994 Roland McGrath (roland@churchy.gnu.ai.mit.edu)
* termcap.c (O_RDONLY): Define to 0 if not already defined.
(tgetent): Use O_RDONLY instead of explicit 0 in call to open.
Wed Jan 5 22:20:15 1993 Morten Welinder (terra@diku.dk)
* termcap.c (tgetent) [INTERNAL_TERMINAL]: Fake internal terminal
without reading any files.
(valid_file_name, tgetent) [MSDOS]: Drive letter support.
(tgetent) [MSDOS]: Use text mode for database.
Fri Dec 17 00:22:43 1993 Mike Long (mike.long@analog.com)
* termcap.c (tgetent): Replaced literal filenames for termcap
database with preprocessor symbol TERMCAP_NAME.
(TERMCAP_NAME): Define if not defined.
Fri Sep 10 00:35:07 1993 Roland McGrath (roland@churchy.gnu.ai.mit.edu)
* Makefile.in (.c.o): Put -I. before -I$(srcdir).
* termcap.c: Include <config.h> instead of "config.h".
* tparam.c: Likewise.
Thu Jul 29 20:53:30 1993 David J. MacKenzie (djm@wookumz.gnu.ai.mit.edu)
* Makefile.in (config.status): Run config.status --recheck, not
configure, to get the right args passed.
Thu Apr 15 12:45:10 1993 David J. MacKenzie (djm@kropotkin.gnu.ai.mit.edu)
* Version 1.2.

249
lib/termcap/grot/INSTALL
View file

@ -1,117 +1,176 @@
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.
Basic Installation
==================
To compile this package:
These are generic installation instructions.
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. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
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.
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
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'.
The file `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
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.
The simplest way to compile this package is:
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
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. 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.
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.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
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'.
2. Type `make' to compile the package.
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.
3. Optionally, type `make check' to run any self-tests that come with
the package.
`configure' ignores any other arguments that you give it.
4. Type `make install' to install the programs and any data files and
documentation.
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
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
The `make' variables that you might want to override with environment
variables when running `configure' are:
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
(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.
Compiling For Multiple Architectures
====================================
(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 ...'
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, 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
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
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.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.
2. Type `make' to compile the package. If you want, you can override
the `make' variables CFLAGS and LDFLAGS like this:
Installation Names
==================
make CFLAGS=-O2 LDFLAGS=-s
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
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.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
4. Type `make install' to install programs, data files, and
documentation.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
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'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
CPU-COMPANY-SYSTEM
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
==================
`configure' recognizes the following options to control how it
operates.
`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
`--help'
Print a summary of the options to `configure', and exit.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made.
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.
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'.

72
lib/termcap/grot/Makefile.in
View file

@ -1,5 +1,5 @@
# Makefile for GNU termcap library.
# Copyright (C) 1992, 1993 Free Software Foundation, Inc.
# Copyright (C) 1992, 1993, 1994 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
@ -21,26 +21,20 @@ srcdir = @srcdir@
VPATH = @srcdir@
CC = @CC@
AR = ar
RANLIB = @RANLIB@
# 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
DEFS = @DEFS@ -DTERMCAP_FILE=\"$(termcapfile)\"
CFLAGS = -g
prefix = /usr/local
exec_prefix = $(prefix)
prefix = @prefix@
exec_prefix = @exec_prefix@
# Directory in which to install libtermcap.a.
libdir = $(exec_prefix)/lib
@ -57,6 +51,10 @@ oldincludedir = /usr/include
# Directory in which to install the documentation info files.
infodir = $(prefix)/info
# File to which `install-data' should install the data file
# if --enable-install-termcap was given.
termcapfile = @termcapfile@
#### End of system configuration section. ####
SHELL = /bin/sh
@ -65,35 +63,55 @@ 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
termcap.src termcap.texi termcap.info* \
texinfo.tex Makefile.in configure configure.in mkinstalldirs install-sh
all: libtermcap.a termcap.info
all: libtermcap.a info
.c.o:
$(CC) -c $(CPPFLAGS) $(DEFS) -I$(srcdir) $(CFLAGS) $<
$(CC) -c $(CPPFLAGS) $(DEFS) -I. -I$(srcdir) $(CFLAGS) $<
install: all
install: all installdirs @installdata@
$(INSTALL_DATA) libtermcap.a $(libdir)/libtermcap.a
-ranlib $(libdir)/libtermcap.a
test -d $(includedir) || mkdir $(includedir)
-$(RANLIB) $(libdir)/libtermcap.a
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:
uninstall: @uninstalldata@
rm -f $(libdir)/libtermcap.a $(includedir)/termcap.h
test -z "$(oldincludedir)" || rm -f $(oldincludedir)/termcap.h
rm -f $(infodir)/termcap.info*
# These are separate targets to avoid trashing the user's existing
# termcap file unexpectedly.
install-data:
$(INSTALL_DATA) ${srcdir}/termcap.src ${termcapfile}
uninstall-data:
rm -f ${termcapfile}
installdirs:
$(SHELL) ${srcdir}/mkinstalldirs $(bindir) $(libdir) \
$(includedir) $(infodir)
Makefile: Makefile.in config.status
$(SHELL) config.status
config.status: configure
$(SHELL) config.status --recheck
configure: configure.in
cd $(srcdir) && autoconf
libtermcap.a: $(OBJS)
ar rc $@ $(OBJS)
-ranlib $@
$(AR) rc $@ $(OBJS)
-$(RANLIB) $@
info: termcap.info
termcap.info: termcap.texi
$(MAKEINFO) $(srcdir)/termcap.texi --output=$(srcdir)/termcap.info
$(MAKEINFO) $(srcdir)/termcap.texi --output=$@
TAGS: $(SRCS)
etags $(SRCS)
@ -104,9 +122,11 @@ clean:
mostlyclean: clean
distclean: clean
rm -f Makefile config.status
rm -f Makefile config.status config.cache config.log
realclean: distclean
maintainer-clean: distclean
@echo "This command is intended for maintainers to use;"
@echo "rebuilding the deleted files requires makeinfo."
rm -f TAGS *.info*
dist: $(DISTFILES)
@ -114,5 +134,5 @@ dist: $(DISTFILES)
rm -rf `cat .fname`
mkdir `cat .fname`
ln $(DISTFILES) `cat .fname`
tar chzf `cat .fname`.tar.z `cat .fname`
tar chzf `cat .fname`.tar.gz `cat .fname`
rm -rf `cat .fname` .fname

8
lib/termcap/grot/NEWS
View file

@ -1,3 +1,11 @@
Major changes in release 1.3:
Termcap data file is now included in distribution and may optionally
be installed, or used in a non-default location.
Support for a fake internal terminal (no external files).
Higher tty speeds supported.
Portability tweaks.
Major changes in release 1.2:
For `%.', only set the high bit on NUL.

30
lib/termcap/grot/README
View file

@ -1,13 +1,33 @@
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.
independent of the terminal type. The GNU termcap library does not
place an arbitrary limit on the size of termcap entries, unlike most
other termcap libraries.
The GNU termcap library does not place an arbitrary limit on the size
of termcap entries, unlike most other termcap libraries.
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. However, use of termcap is discouraged. Termcap is
being phased out in favor of the terminfo-based ncurses library, which
contains an emulation of the termcap library routines in addition to
an excellent curses implementation. ncurses is available from the
usual GNU archive sites.
See the file INSTALL for compilation and installation instructions.
Additionally:
This package contains termcap.src, the latest official termcap data
file. By default, it is not installed. The current version contains
some entries that are more than 1023 bytes long, which is the largest
value that is safe to use with the many historical applications that
only allocate a 1024 byte termcap buffer (telnet, for example). If
you make sure that all of your programs allocate buffers of at least
2500 bytes, or let the termcap library do it by passing a NULL
pointer, then it is safe to install the new termcap file, as described
below.
You can give configure two special options:
--enable-install-termcap install the termcap data file
--with-termcap=FILE use data file FILE instead of /etc/termcap
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

1152
lib/termcap/grot/configure vendored
View file

File diff suppressed because it is too large Load diff

21
lib/termcap/grot/configure.in
View file

@ -1,10 +1,23 @@
dnl Process this file with autoconf to produce a configure script.
AC_INIT(termcap.h)
AC_SUBST(PROGS)dnl
AC_ARG_ENABLE(install-termcap,
[ --enable-install-termcap install the termcap data file],
[if test $enableval = yes; then
installdata=install-data uninstalldata=uninstall-data
fi])
AC_SUBST(installdata)dnl
AC_SUBST(uninstalldata)dnl
AC_ARG_WITH(termcap,
[ --with-termcap=FILE use data file FILE instead of /etc/termcap],
termcapfile=$withval, termcapfile=/etc/termcap)
AC_SUBST(termcapfile)dnl
AC_PROG_CC
AC_PROG_CPP
AC_PROG_RANLIB
AC_PROG_INSTALL
AC_HAVE_HEADERS(string.h)
AC_UNISTD_H
AC_HAVE_HEADERS(string.h unistd.h)
AC_STDC_HEADERS
AC_OUTPUT(Makefile)

108
lib/termcap/grot/termcap.info
View file

@ -1,5 +1,5 @@
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 is Info file ./termcap.info, produced by Makeinfo-1.55 from the
input file ./termcap.texi.
This file documents the termcap library of the GNU system.
@ -21,60 +21,60 @@ translation approved by the Foundation.

Indirect:
termcap.info-1: 912
termcap.info-2: 47539
termcap.info-3: 90314
termcap.info-4: 138449
termcap.info-1: 874
termcap.info-2: 47411
termcap.info-3: 90390
termcap.info-4: 138827

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
Node: Top874
Node: Introduction4105
Node: Library5832
Node: Preparation6851
Node: Find8034
Node: Interrogate11492
Node: Initialize16800
Node: Padding18440
Node: Why Pad19146
Node: Not Enough20768
Node: Describe Padding23336
Node: Output Padding24826
Node: Parameters28441
Node: Encode Parameters30101
Node: Using Parameters36185
Node: tparam36780
Node: tgoto38806
Node: Data Base41361
Node: Format42257
Node: Capability Format44346
Node: Naming47411
Node: Inheriting51980
Node: Changing54224
Node: Capabilities55388
Node: Basic58127
Node: Screen Size62180
Node: Cursor Motion63920
Node: Wrapping74062
Node: Scrolling77091
Node: Windows82980
Node: Clearing83714
Node: Insdel Line85478
Node: Insdel Char90390
Node: Standout100375
Node: Underlining109433
Node: Cursor Visibility111852
Node: Bell112600
Node: Keypad113149
Node: Meta Key117864
Node: Initialization118818
Node: Pad Specs121369
Node: Status Line123422
Node: Half-Line125306
Node: Printer126108
Node: Summary127787
Node: Var Index138114
Node: Cap Index138827
Node: Index145991

End Tag Table

15
lib/termcap/grot/termcap.info-1
View file

@ -1,5 +1,5 @@
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 is Info file ./termcap.info, produced by Makeinfo-1.55 from the
input file ./termcap.texi.
This file documents the termcap library of the GNU system.
@ -218,10 +218,9 @@ variable `TERM' using `getenv ("TERM")'.
If you are using the GNU version of termcap, you can alternatively
ask `tgetent' to allocate enough space. Pass a null pointer for
BUFFER, and `tgetent' itself allocates the storage using `malloc'. In
this case the returned value on success is the address of the storage,
cast to `int'. But normally there is no need for you to look at the
address. Do not free the storage yourself.
BUFFER, and `tgetent' itself allocates the storage using `malloc'.
There is no way to get the address that was allocated, and you
shouldn't try to free the storage.
With the Unix version of termcap, you must allocate space for the
description yourself and pass the address of the space as the argument
@ -881,7 +880,7 @@ preferable for cursor motion.
File: termcap.info, Node: tparam, Next: tgoto, Up: Using Parameters
`tparam'
--------
........
The function `tparam' can encode display commands with any number of
parameters and allows you to specify the buffer space. It is the
@ -930,7 +929,7 @@ capability.
File: termcap.info, Node: tgoto, Prev: tparam, Up: Using Parameters
`tgoto'
-------
.......
The special case of cursor motion is handled by `tgoto'. There are
two reasons why you might choose to use `tgoto':

9
lib/termcap/grot/termcap.info-2
View file

@ -1,5 +1,5 @@
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 is Info file ./termcap.info, produced by Makeinfo-1.55 from the
input file ./termcap.texi.
This file documents the termcap library of the GNU system.
@ -663,6 +663,11 @@ column.
carriage-return newline, which will leave the cursor at the
beginning of the following line.
`LP'
Flag whose presence means that it is safe to write in the last
column of the last line without worrying about undesired
scrolling. `LP' indicates the DEC flavor of `xn' strangeness.

File: termcap.info, Node: Scrolling, Next: Windows, Prev: Wrapping, Up: Capabilities

21
lib/termcap/grot/termcap.info-3
View file

@ -1,5 +1,5 @@
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 is Info file ./termcap.info, produced by Makeinfo-1.55 from the
input file ./termcap.texi.
This file documents the termcap library of the GNU system.
@ -566,12 +566,12 @@ a `ks' capability and send it, to make the keypad actually transmit.
Such programs should also send the `ke' string when exiting.
`ks'
String of commands to make the function keys transmit. If this
String of commands to make the keypad keys transmit. If this
capability is not provided, but the others in this section are,
programs may assume that the function keys always transmit.
programs may assume that the keypad keys always transmit.
`ke'
String of commands to make the function keys work locally. This
String of commands to make the keypad keys work locally. This
capability is provided only if `ks' is.
`kl'
@ -784,6 +784,11 @@ Initialization
String of commands to set tab stop at current cursor column on all
lines.
`NF'
Flag whose presence means that the terminal does not support
XON/XOFF flow control. Programs should not send XON (`C-q') or
XOFF (`C-s') characters to the terminal.

File: termcap.info, Node: Pad Specs, Next: Status Line, Prev: Initialization, Up: Capabilities
@ -1266,6 +1271,9 @@ definitions, see the index of capability names (*note Cap Index::.).
`lm'
Number: lines of display memory.
`LP'
Flag: writing to last column of last line will not scroll.
`mb'
String to enter blinking mode.
@ -1305,6 +1313,9 @@ definitions, see the index of capability names (*note Cap Index::.).
`nd'
String to move the cursor right one column.
`NF'
Flag: do not use XON/XOFF flow control.
`nl'
Obsolete alternative name for the `do' and `sf' capabilities.

22
lib/termcap/grot/termcap.info-4
View file

@ -1,5 +1,5 @@
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 is Info file ./termcap.info, produced by Makeinfo-1.55 from the
input file ./termcap.texi.
This file documents the termcap library of the GNU system.
@ -28,8 +28,8 @@ Capability Index
* Menu:
* ae: Standout.
* AL: Insdel Line.
* al: Insdel Line.
* AL: Insdel Line.
* am: Wrapping.
* as: Standout.
* bc: Cursor Motion.
@ -42,8 +42,8 @@ Capability Index
* ce: Clearing.
* ch: Cursor Motion.
* cl: Clearing.
* CM: Cursor Motion.
* cm: Cursor Motion.
* CM: Cursor Motion.
* co: Screen Size.
* cr: Cursor Motion.
* cS: Scrolling.
@ -61,8 +61,8 @@ Capability Index
* DL: Insdel Line.
* dm: Insdel Char.
* dN: Pad Specs.
* DO: Cursor Motion.
* do: Cursor Motion.
* DO: Cursor Motion.
* ds: Status Line.
* dT: Pad Specs.
* ec: Clearing.
@ -100,6 +100,7 @@ Capability Index
* li: Screen Size.
* ll: Cursor Motion.
* lm: Scrolling.
* LP: Wrapping.
* mb: Standout.
* md: Standout.
* me: Standout.
@ -114,6 +115,7 @@ Capability Index
* ms: Underlining.
* nc: Cursor Motion.
* nd: Cursor Motion.
* NF: Initialization.
* nl: Cursor Motion.
* ns: Scrolling.
* nw: Cursor Motion.
@ -131,12 +133,12 @@ Capability Index
* sa: Standout.
* sc: Cursor Motion.
* se: Standout.
* sf: Scrolling.
* SF: Scrolling.
* sf: Scrolling.
* sg: Standout.
* so: Standout.
* sr: Scrolling.
* SR: Scrolling.
* sr: Scrolling.
* st: Initialization.
* ta: Cursor Motion.
* te: Initialization.
@ -158,8 +160,8 @@ Capability Index
* xb: Basic.
* xn: Wrapping.
* xs: Standout.
* xt: Standout.
* xt: Cursor Motion.
* xt: Standout.

File: termcap.info, Node: Index, Prev: Cap Index, Up: Top
@ -199,8 +201,8 @@ Concept Index
* repeat output: Basic.
* reset: Initialization.
* screen size: Screen Size.
* screen size: Screen Size.
* screen size: Naming.
* screen size: Screen Size.
* scrolling: Scrolling.
* standout: Standout.
* status line: Status Line.
@ -212,7 +214,7 @@ Concept Index
* visibility: Cursor Visibility.
* visible bell: Bell.
* window: Windows.
* wrapping: Naming.
* wrapping: Wrapping.
* wrapping: Naming.

29
lib/termcap/grot/termcap.texi
View file

@ -1,5 +1,5 @@
\input texinfo @c -*-texinfo-*-
@setfilename termcap
@setfilename termcap.info
@settitle The Termcap Library
@smallbook
@ -286,9 +286,8 @@ variable @code{TERM} using @code{getenv ("TERM")}.
If you are using the GNU version of termcap, you can alternatively ask
@code{tgetent} to allocate enough space. Pass a null pointer for
@var{buffer}, and @code{tgetent} itself allocates the storage using
@code{malloc}. In this case the returned value on success is the address
of the storage, cast to @code{int}. But normally there is no need for you
to look at the address. Do not free the storage yourself.@refill
@code{malloc}. There is no way to get the address that was allocated,
and you shouldn't try to free the storage.@refill
With the Unix version of termcap, you must allocate space for the
description yourself and pass the address of the space as the argument
@ -1890,6 +1889,12 @@ flag, output a @samp{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.
@item LP
@kindex LP
Flag whose presence means that it is safe to write in the last column of
the last line without worrying about undesired scrolling. @samp{LP}
indicates the DEC flavor of @samp{xn} strangeness.
@end table
@node Scrolling, Windows, Wrapping, Capabilities
@ -2830,12 +2835,12 @@ Such programs should also send the @samp{ke} string when exiting.
@table @asis
@item @samp{ks}
@kindex ka@dots{}ku
String of commands to make the function keys transmit. If this
String of commands to make the keypad keys transmit. If this
capability is not provided, but the others in this section are,
programs may assume that the function keys always transmit.
programs may assume that the keypad keys always transmit.
@item @samp{ke}
String of commands to make the function keys work locally. This
String of commands to make the keypad keys work locally. This
capability is provided only if @samp{ks} is.
@item @samp{kl}
@ -3065,6 +3070,12 @@ String of commands to clear all tab stops.
@kindex st
String of commands to set tab stop at current cursor column on all
lines.
@item NF
@kindex NF
Flag whose presence means that the terminal does not support XON/XOFF
flow control. Programs should not send XON (@kbd{C-q}) or XOFF
(@kbd{C-s}) characters to the terminal.
@end table
@node Pad Specs, Status Line, Initialization, Capabilities
@ -3460,6 +3471,8 @@ Number: height of the screen.
String to position cursor at lower left corner.
@item lm
Number: lines of display memory.
@item LP
Flag: writing to last column of last line will not scroll.
@item mb
String to enter blinking mode.
@item md
@ -3486,6 +3499,8 @@ Flag: cursor motion in standout mode is safe.
Obsolete flag: do not use ASCII carriage-return on this terminal.
@item nd
String to move the cursor right one column.
@item NF
Flag: do not use XON/XOFF flow control.
@item nl
Obsolete alternative name for the @samp{do} and @samp{sf} capabilities.
@item ns

1175
lib/termcap/grot/texinfo.tex
View file

File diff suppressed because it is too large Load diff