|
|
1.1 root 1: Curses/Terminfo distribution
2:
3: THIS CODE IS PROPRIETARY TO BELL LABS. DO NOT GIVE IT TO ANYONE ELSE.
4:
5: You have a distribution of curses and terminfo. This is the second
6: internal distribution of curses. To find the version, look in
7: screen/curses.c for a version number.
8:
9: To report bugs, if at all possible, demonstrate the bug in the form
10: of a "show script", that is, a 2 page (often 48 line) file which
11: will cause the show program to mess up. If a simple modification
12: to show will illustrate the bug, this is second choice. Otherwise,
13: please write a small program that illustrates the bug. Huge programs
14: that "don't work" are unlikely to get much sympathy.
15:
16: To install curses, be guided by the makefiles. You can use the
17: makefile in this directory. Do a "make all install". Do not do "make clean"
18: until the install completes. This will not install any manual pages
19: or demos - they are up to you to install by hand if you want them.
20:
21: If you are on a 16 bit machine, it will be necessary
22: to add the -i option to ../screen/makefile's compilation of tic.
23: (This has already been done for the PDP-11).
24: Otherwise, tic will dump core when trying to compile some terminals.
25: If you are on a small 11 without separate I/D, you'll have
26: to compile only those entries that don't use lots of use= indirection:
27: what's happening is that 3 or 4 levels of use= recursion runs out of
28: memory on the stack.
29:
30: Now you can run programs using curses. A sample program included in
31: the screen directory is show.c, say "make show" and it will compile.
32: "show" is a paging program - you hit space to go on to the next page.
33: You can use show to make sure everything works. (Be sure you have TERM
34: set in your environment. TERMCAP is no longer necessary.) A fancier
35: demo can be found in the demo directory.
36:
37: If you add or change terminfo descriptions in the terminfo directory,
38: you can run compile on the single source file, instead of on terminfo.src.
39: Since the compiler is so slow, it's worthwhile to only run it on
40: one source file.
41:
42: If you add capabilities
43: you should edit screen/caps. Be sure to add the capabilties
44: at the END of the section (bools, nums, or strings) as this will
45: preserve compatibility with older binaries. Then run "make term.h",
46: "make clean", and recompile the library.
47:
48: For debugging, the makefile will create several other versions of curses.
49: In addition to the .c (source) and .o (object) files, there are .p's
50: for profiling, .d's for debugging, and .t's for tracing. These will
51: create dlibcurses.a, plibcurses.a, and tlibcurses.a. The d version
52: defines DEBUG and uses the -g flag for sdb. DEBUG causes the file "trace"
53: to be created in the current directory when you run a program with curses.
54: This can be installed as -lcurses if you wish. The t version defines
55: DEBUG for tracing, but doesn't use -g, so it's faster to compile, but
56: won't help much if core dumps.
57:
58: A recent addition is screen/termcap.c (made from screen/termcap.form
59: and screen/caps) which emulates the older termcap library. This is
60: intended only as a conversion aid, but it is complete enough to enable
61: vi 3.7 (the last termcap version) to run using terminfo.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.