README
1
2<< 12 May 1983 >>
3To install this directory on your system:
4
5First determine a list of "common terminals" for your system. This list
6will probably be small, and can be empty if you like, but you should
7probably put your own terminal in it.
8
9Second, edit the editor script "reorder" to use this list instead of the
10list built in to it. The changes will be evident from looking at the
11script. Notice that the script contains the terminals in order from least
12common to most common, since the move commands will move them to the front
13in that order, the effect will be to put the most common at the front of
14termcap since that's moved last. The s.* terminals are specials, and
15although they don't have to go to the front, they are probably quite
16common and really should go near the front.
17
18Third, if you are not a super user and cannot create the directory
19/usr/lib/tabset, make a corresponding directory somewhere you can and add
20a line to reorder to globally change all /usr/lib/tabset's to your own
21path name. This change is better than just changing the termcap file
22because it makes it easier to diff it from newer distributed versions.
23Try to keep the source as is whenever possible, and put mungings into
24reorder.
25
26Now you can run "make install" which will create an /etc/termcap. Again,
27if you aren't a super user change the cp command to put it where you can.
28In this case you will have to redefine E_TERMCAP in "local/uparm.h", which
29will probably be in subdirectories with the other UCB software.
30
31
32Finally, if you make additions or fixes to termcap, please mail a note
33explaining what you did with the fixed termcap entry (not the whole file,
34please!) to me at one of the addresses below, so it can be incorporated
35back into the original source. I will normally include anything unless
36there is a good reason not to, but I reserve the right to redo it differently.
37
38 uunet!ucbvax!termcap (uucp)
39 termcap@berkeley.cs.edu (Internet)
40
41<< 14 October 1987 >>
42It is probably easiest to make local termcap changes in separate
43files, eg /usr/local/etc/termcap, and encourage people to put
44
45 setenv TERMPATH ~/.termcap:/usr/local/etc/termcap:/etc/termcap
46
47in their shell startup files. This way local system-wide changes can be
48isolated in /usr/local/etc/termcap and user changes in ~/.termcap, all
49without consuming lots of disk or requiring re-integration of local
50changes when system termcap files change.
51
52 John Kunze
53 termcap@berkeley.cs.edu
54
55