NameDateSize

..27-Jun-202090

aclocal.m420-Feb-2020258.3 KiB

ANNOUNCE20-Feb-202040.6 KiB

announce.html.in20-Feb-202066.1 KiB

AUTHORS20-Feb-20202.6 KiB

config.guess18-Feb-202047.3 KiB

config.sub18-Feb-202030.9 KiB

configure20-Feb-2020730.5 KiB

configure.in20-Feb-202075.9 KiB

convert_configure.pl20-Feb-20204.8 KiB

COPYING20-Feb-20201.4 KiB

dist.mk20-Feb-20207.2 KiB

doc/18-Feb-20205

form/20-Feb-202053

FREEBSD-upgrade06-Nov-20121.6 KiB

FREEBSD-Xlist06-Nov-201292

include/20-Feb-202036

INSTALL20-Feb-202090.4 KiB

install-sh06-Nov-20127 KiB

Makefile.in20-Feb-20204.3 KiB

Makefile.os220-Feb-20208.6 KiB

man/20-Feb-2020146

MANIFEST20-Feb-202036.1 KiB

menu/20-Feb-202041

misc/20-Feb-202028

mk-0th.awk20-Feb-20205.7 KiB

mk-1st.awk20-Feb-202018.1 KiB

mk-2nd.awk20-Feb-20205.2 KiB

mk-hdr.awk20-Feb-20203.9 KiB

ncurses/20-Feb-202031

NEWS20-Feb-2020631.9 KiB

panel/20-Feb-202026

progs/20-Feb-202026

README20-Feb-202010.1 KiB

README.emx20-Feb-20204 KiB

README.MinGW20-Feb-20206.5 KiB

TO-DO20-Feb-20209.5 KiB

VERSION20-Feb-202020

README

1-------------------------------------------------------------------------------
2-- Copyright 2020 Thomas E. Dickey                                           --
3-- Copyright 1998-2012,2018 Free Software Foundation, Inc.                   --
4--                                                                           --
5-- Permission is hereby granted, free of charge, to any person obtaining a   --
6-- copy of this software and associated documentation files (the             --
7-- "Software"), to deal in the Software without restriction, including       --
8-- without limitation the rights to use, copy, modify, merge, publish,       --
9-- distribute, distribute with modifications, sublicense, and/or sell copies --
10-- of the Software, and to permit persons to whom the Software is furnished  --
11-- to do so, subject to the following conditions:                            --
12--                                                                           --
13-- The above copyright notice and this permission notice shall be included   --
14-- in all copies or substantial portions of the Software.                    --
15--                                                                           --
16-- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS   --
17-- OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF                --
18-- MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN --
19-- NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,       --
20-- DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR     --
21-- OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE --
22-- USE OR OTHER DEALINGS IN THE SOFTWARE.                                    --
23--                                                                           --
24-- Except as contained in this notice, the name(s) of the above copyright    --
25-- holders shall not be used in advertising or otherwise to promote the      --
26-- sale, use or other dealings in this Software without prior written        --
27-- authorization.                                                            --
28-------------------------------------------------------------------------------
29-- $Id: README,v 1.28 2020/02/02 23:34:34 tom Exp $
30-------------------------------------------------------------------------------
31		README file for the ncurses package
32
33See the file ANNOUNCE for a summary of ncurses features and ports.
34See the file INSTALL for instructions on how to build and install ncurses.
35See the file NEWS for a release history and bug-fix notes.
36See the file TO-DO for things that still need doing, including known bugs.
37
38Browse the file misc/ncurses-intro.html for narrative descriptions of how
39to use ncurses and the panel, menu, and form libraries.
40 
41Browse the file doc/html/hackguide.html for a tour of the package internals.
42
43ROADMAP AND PACKAGE OVERVIEW:
44
45You should be reading this file in a directory called:  ncurses-d.d, where d.d
46is the current version number (see the dist.mk file in this directory for
47that).  There should be a number of subdirectories, including `c++', `form',
48`man', `menu', `misc', `ncurses', `panel', `progs', `test', 'tack' and `Ada95'. 
49(The 'tack' program may be distributed separately).
50
51A full build/install of this package typically installs several libraries, a
52handful of utilities, and a database hierarchy.  Here is an inventory of the
53pieces:
54
55The libraries are:
56
57	libncurses.a       (normal)
58	libncurses.so      (shared)
59	libncurses_g.a     (debug and trace code enabled)
60	libncurses_p.a     (profiling enabled)
61
62	libpanel.a         (normal)
63	libpanel.so        (shared)
64	libpanel_g.a       (debug and trace code enabled)
65
66	libmenu.a          (normal)
67	libmenu.so         (shared)
68	libmenu_g.a        (debug enabled)
69
70	libform.a          (normal)
71	libform.so         (shared)
72	libform_g.a        (debug enabled)
73
74If you configure using the --enable-widec option, a "w" is appended to the
75library names (e.g., libncursesw.a), and the resulting libraries support
76wide-characters, e.g., via a UTF-8 locale.  The corresponding header files
77are compatible with the non-wide-character configuration; wide-character
78features are provided by ifdef's in the header files.  The wide-character
79library interfaces are not binary-compatible with the non-wide-character
80version.
81
82If you configure using the --enable-reentrant option, a "t" is appended to the
83library names (e.g., libncursest.a) and the resulting libraries have a
84different binary interface which makes the ncurses interface more "opaque".
85
86The ncurses libraries implement the curses API.  The panel, menu and forms
87libraries implement clones of the SVr4 panel, menu and forms APIs.  The source
88code for these lives in the `ncurses', `panel', `menu', and `form' directories
89respectively.
90
91In the `c++' directory, you'll find code that defines an interface to the
92curses, forms, menus and panels library packaged as C++ classes, and a demo program in C++
93to test it.  These class definition modules are not installed by the 'make
94install.libs' rule as libncurses++.
95
96In the `Ada95' directory, you'll find code and documentation for an
97Ada95 binding of the curses API, to be used with the GNAT compiler.
98This binding is built by a normal top-level `make' if configure detects
99an usable version of GNAT (3.11 or above). It is not installed automatically.
100See the Ada95 directory for more build and installation instructions and
101for documentation of the binding.
102
103To do its job, the ncurses code needs your terminal type to be set in the
104environment variable TERM (normally set by your OS; under UNIX, getty(1)
105typically does this, but you can override it in your .profile); and, it needs a
106database of terminal descriptions in which to look up your terminal type's
107capabilities.
108
109In older (V7/BSD) versions of curses, the database was a flat text file,
110/etc/termcap; in newer (USG/USL) versions, the database is a hierarchy of
111fast-loading binary description blocks under /usr/lib/terminfo.  These binary
112blocks are compiled from an improved editable text representation called
113`terminfo' format (documented in man/terminfo.5).  The ncurses library can use
114either /etc/termcap or the compiled binary terminfo blocks, but prefers the
115second form.
116
117In the `misc' directory, there is a text file terminfo.src, in editable
118terminfo format, which can be used to generate the terminfo binaries (that's
119what make install.data does).  If the package was built with the
120--enable-termcap option enabled, and the ncurses library cannot find a terminfo
121description for your terminal, it will fall back to the termcap file supplied
122with your system (which the ncurses package installation leaves strictly
123alone).
124
125The utilities are as follows:
126
127	tic             -- terminfo source to binary compiler
128	infocmp         -- terminfo binary to source decompiler/comparator
129	clear           -- emits clear-screen for current terminal
130	tabs            -- set tabs on a terminal
131	tput            -- shell-script access to terminal capabilities.
132	toe             -- table of entries utility
133	tset            -- terminal-initialization utility
134
135The first two (tic and infocmp) are used for manipulating terminfo
136descriptions; the next two (clear and tput) are for use in shell scripts.  The
137last (tset) is provided for 4.4BSD compatibility.  The source code for all of
138these lives in the `progs' directory.
139
140Detailed documentation for all libraries and utilities can be found in the
141`man' and `doc' directories.  An HTML introduction to ncurses, panels, and
142menus programming lives in the `doc/html' directory.  Manpages in HTML format
143are under `doc/html/man'.
144
145The `test' directory contains programs that can be used to verify or
146demonstrate the functions of the ncurses libraries.  See test/README for
147descriptions of these programs.  Notably, the `ncurses' utility is designed to
148help you systematically exercise the library functions.
149
150AUTHORS:
151
152Pavel Curtis: 
153	wrote the original ncurses
154
155Zeyd M. Ben-Halim:
156	port of original to Linux and many enhancements.
157
158Thomas Dickey (maintainer for 1.9.9g through 4.1, resuming with FSF's 5.0):
159	configuration scripts, porting, mods to adhere to XSI Curses in the
160	areas of background color, terminal modes.  Also memory leak testing,
161	the wresize, default colors and key definition extensions and numerous
162	bug fixes -- more than half of those enumerated in NEWS beginning with
163	the internal release 1.8.9, see
164
165		https://invisible-island.net/personal/changelogs.html
166
167Florian La Roche (official maintainer for FSF's ncurses 4.2)
168	Beginning with release 4.2, ncurses is distributed under an MIT-style
169	license.
170
171Eric S. Raymond:
172	the man pages, infocmp(1), tput(1), clear(1), captoinfo(1), tset(1),
173	toe(1), most of tic(1), trace levels, the HTML intro, wgetnstr() and
174	many other entry points, the cursor-movement optimization, the
175	scroll-pack optimizer for vertical motions, the mouse interface and
176	xterm mouse support, and the ncurses test program.
177
178Juergen Pfeifer
179	The menu and form libraries, C++ bindings for ncurses, menus, forms and
180	panels, as well as the Ada95 binding.  Ongoing support for panel.
181
182CONTRIBUTORS:
183
184Alexander V. Lukyanov
185	for numerous fixes and improvements to the optimization logic.
186
187David MacKenzie
188	for first-class bug-chasing and methodical testing.
189
190Ross Ridge
191	for the code that hacks termcap parameterized strings into terminfo.
192
193Warren Tucker and Gerhard Fuernkranz,
194	for writing and sending the panel library.
195
196Hellmuth Michaelis,
197	for many patches and testing the optimization code.
198
199Eric Newton, Ulrich Drepper, and Anatoly Ivasyuk:
200	the C++ code.
201
202Jonathan Ross,
203	for lessons in using sed.
204
205Keith Bostic (maintainer of 4.4BSD curses)
206	for help, criticism, comments, bug-finding, and being willing to
207	deep-six BSD curses for this one when it grew up.
208
209Richard Stallman,
210	for his commitment to making ncurses free software.
211
212Countless other people have contributed by reporting bugs, sending fixes,
213suggesting improvements, and generally whining about ncurses :-)
214
215BUGS:
216	See the INSTALL file for bug and developer-list addresses.
217	The Hacker's Guide in the doc directory includes some guidelines
218	on how to report bugs in ways that will get them fixed most quickly.
219

README.emx

1-------------------------------------------------------------------------------
2-- Copyright 2020 Thomas E. Dickey                                           --
3-- Copyright 1998-2006,2018 Free Software Foundation, Inc.                   --
4--                                                                           --
5-- Permission is hereby granted, free of charge, to any person obtaining a   --
6-- copy of this software and associated documentation files (the             --
7-- "Software"), to deal in the Software without restriction, including       --
8-- without limitation the rights to use, copy, modify, merge, publish,       --
9-- distribute, distribute with modifications, sublicense, and/or sell copies --
10-- of the Software, and to permit persons to whom the Software is furnished  --
11-- to do so, subject to the following conditions:                            --
12--                                                                           --
13-- The above copyright notice and this permission notice shall be included   --
14-- in all copies or substantial portions of the Software.                    --
15--                                                                           --
16-- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS   --
17-- OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF                --
18-- MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN --
19-- NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,       --
20-- DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR     --
21-- OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE --
22-- USE OR OTHER DEALINGS IN THE SOFTWARE.                                    --
23--                                                                           --
24-- Except as contained in this notice, the name(s) of the above copyright    --
25-- holders shall not be used in advertising or otherwise to promote the      --
26-- sale, use or other dealings in this Software without prior written        --
27-- authorization.                                                            --
28-------------------------------------------------------------------------------
29-- $Id: README.emx,v 1.11 2020/02/02 23:34:34 tom Exp $
30-- Author: Thomas Dickey
31-------------------------------------------------------------------------------
32
33You can build ncurses on OS/2 in the EMX environment.  But you must build and
34acquire tools.  Not all of the tools distributed with EMX work properly, and
35some additional ones are required.
36
37First, the configure script distributed with ncurses will not run as-is in EMX. 
38You can generate a new one if you have autoconf built for EMX.  You will need
39the EMX development tools, of course.  Get these programs to start:
40
41	GNU m4 program (version 1.4)
42	GNU autoconf (version 2.13).
43	GNU patch (version 2.5)
44
45Apply the autoconf patches from
46
47	https://invisible-island.net/autoconf
48	ftp://ftp.invisible-island.net/autoconf
49
50These are ordered by date:
51
52	autoconf-2.13-20030927.patch.gz
53	autoconf-2.13-20030927-emx.patch.gz
54
55I built my development environment for ncurses using EMX 0.9c at the end of
561997.  Much of the EMX patch for autoconf was done originally by J.J.G.Ripoll,
57using a similar environment (he prefers using the 'ash' shell).  Newer versions
58may fix these problems:
59
60	+ The pdksh program distributed at Hobbes and Leo (with a 1996 date) is
61	  defective.  It does not process "here documents" correctly (which
62	  renders it useless for running the autoconf script).  I built my own
63	  copy of pdksh 5.2.13, which does have the bug corrected (documented
64	  in the change log for pdksh).
65
66	+ I also built from sources (because the distributed binaries did not
67	  work) the cmp, diff programs.
68	  
69	  Other required utilities such as ar, cat, chmod, cp, gawk, grep, mv,
70	  ls, rm, mkdir, sed, sort and tr worked.
71
72Once you have autoconf patched and installed, run 'autoconf' from the top-level
73directory of ncurses to generate the EMX-specific configure script.
74

README.MinGW

1-------------------------------------------------------------------------------
2-- Copyright 2020 Thomas E. Dickey                                           --
3-- Copyright 2008-2011,2012 Free Software Foundation, Inc.                   --
4--                                                                           --
5-- Permission is hereby granted, free of charge, to any person obtaining a   --
6-- copy of this software and associated documentation files (the             --
7-- "Software"), to deal in the Software without restriction, including       --
8-- without limitation the rights to use, copy, modify, merge, publish,       --
9-- distribute, distribute with modifications, sublicense, and/or sell copies --
10-- of the Software, and to permit persons to whom the Software is furnished  --
11-- to do so, subject to the following conditions:                            --
12--                                                                           --
13-- The above copyright notice and this permission notice shall be included   --
14-- in all copies or substantial portions of the Software.                    --
15--                                                                           --
16-- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS   --
17-- OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF                --
18-- MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN --
19-- NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,       --
20-- DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR     --
21-- OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE --
22-- USE OR OTHER DEALINGS IN THE SOFTWARE.                                    --
23--                                                                           --
24-- Except as contained in this notice, the name(s) of the above copyright    --
25-- holders shall not be used in advertising or otherwise to promote the      --
26-- sale, use or other dealings in this Software without prior written        --
27-- authorization.                                                            --
28-------------------------------------------------------------------------------
29-- $Id: README.MinGW,v 1.10 2020/02/02 23:34:34 tom Exp $
30-- Author: Juergen Pfeifer
31-------------------------------------------------------------------------------
32
33This is work in progress, but it's in an state where one can see it
34works at least on the Windows Console.
35
36You should install the MSYS package, so that you've a shell environment that
37allows you to run the scripts, especially configure etc.  You can get that
38from http://www.mingw.org
39
40To build ncurses for native Windows, you need the MinGW toolchain.  The
41original MinGW toolchain from the above site is only for 32-Bit Windows.  As
42Windows Server - and also regular workstations - are moving to 64-Bit, it
43seems to be reasonable to have a toolchain that supports both architectures.
44I recommend to use the TDM gcc toolchain which you can find at
45http://tdm-gcc.tdragon.net/download.  Go to the download section and select
46the bundle installer for tdm64 (MinGW-w64).  This installs a multilib version
47of the gcc toolchain that can compile for native 32- and 64-Bit Windows
48versions.  It also comes with a working pthread implementation.
49
50The latest config and build scripts we use for MinGW have only been tested
51for the gcc-4.6.1 compiler toolchain (or better).
52
53Using MinGW is a pragmatic decision, it's the easiest way to port this
54heavily UNIX based sourcebase to native Windows. The goal is of course
55to provide the includes, libraries and DLLs to be used with the more
56common traditional development environments on Windows, mainly with
57Microsoft Visual Studio.
58
59The TERM environment variable must be set specially to active the Windows
60console-driver.  The driver checks if TERM is set to "#win32con" (explicit
61use) or if TERM is unset or empty (implicit).
62
63Please also make sure that MSYS links to the correct directory containing
64your MinGW toolchain. For TDM this is usually C:\MinGW64. In your Windows
65CMD.EXE command shell go to the MSYS root directory (most probably
66C:\MSYS or C:\MSYS\1.0) and verify, that there is a junction point mingw
67that points to the MinGW toolchain directory. If not, delete the mingw
68directory and use the mklink command (or the linkd.exe utility on older
69Windows) to create the junction point.
70
71This code requires WindowsNT 5.1 or better, which means on the client
72Windows XP or better, on the server Windows Server 2003 or better.
73
74I recommend using libtool to build ncurses on MinGW, because libtool
75knows exactly how to build dll's on Windows for use with MinGW.
76
77To build a modern but still small footprint ncurses that provides
78hooks for interop, I recommend using these options:
79
80	  --with-libtool
81	  --disable-home-terminfo
82	  --enable-database
83	  --disable-termcap
84	  --enable-sp-funcs
85	  --enable-term-driver
86	  --enable-interop
87
88This is the configuration commandline as I'm using it at the moment (assuming
89environment variable MINGW_ROOT to hold the root directory name of your MinGW
90build):
91
92./configure \
93	--prefix=$MINGW_ROOT \
94	--with-cxx \
95	--without-ada \
96	--enable-warnings \
97	--enable-assertions \
98	--disable-home-terminfo \
99	--enable-database \
100	--enable-sp-funcs \
101	--enable-term-driver \
102	--enable-interop \
103	--disable-termcap \
104	--with-progs \
105	--with-libtool \
106	--enable-pc-files \
107	--mandir=$MINGW_ROOT/share/man
108
109Please note that it is also necessary to set this environment variable:
110
111export PATH_SEPARATOR=";"
112
113in order to parse the terminfo paths correctly. Terminfo paths should
114always be separated by a seeeemicolon,even when running under MSYS.
115
116To support regular expressions properly, ncurses under MinGW should be
117linked against the gnurx regex library, which must be built separately
118under MinGW.  See
119
120    ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libgnurx-src-2.5.zip
121
122All the options above are - like the whole Windows support -
123experimental.
124
125A lot is still TODO, e.g.:
126
127  - Wide Character support (display is workable, but input untested)
128    The Win32Con driver should actually only use Unicode in the
129    future.
130  - Thread support (locking). If using TDM toolchain this is done by
131    configuring pthreads.
132  - A GUI console driver
133  - Support for Terminals attached via a serial port (via terminfo)
134  - Support for networked Terminal connections (via terminfo)
135  - Workarounds for MinGW's filesystem access are necessary to make infocmp
136    work (though tic works).
137
138To support terminfo, we would need to have an ioctl() simulation for the
139serial and networked terminals.
140