There is one configuration file per terminal type in git/gitps/gitview. The configuration file(s) resides in the user's home directory or (the default versions) in the directory $(prefix)/lib (usually /usr/local/lib). The generic name is .gitrc.TERM. GIT allows each terminal type to have its own configuration file (TERM is the value of the TERM environment variable (e.g vt102). For the Linux console the configuration file is .gitrc.console).
If you have compiled the GIT package with HAVE_LIBTERMCAP and your system has a huge termcap database (/etc/termcap), you can copy the termcap definition(s) of your terminal(s) in a file ($HOME/.termcap e.g.). After that, set your TERMCAP environment variable to point to it. You should add something like this to your .profile :
TERMCAP=/home/mike/.termcap
git/gitps/gitview can run without such a file, but on systems with huge termcap databases, copying the definitions of the most used terminals in a local .termcap will result in git/gitps/gitview starting faster.
If you have compiled the GIT package with HAVE_LIBTERMINFO, or on your system the termcap database is emulated using the terminfo library (like in the HP-UX system), don't bother about speed.
The configuration file .gitrc.TERM is the file searched by git/gitps/gitview each time they are started, in order to configure themselves. .gitrc.TERM it is first searched in the home directory then, if not found, in the directory $(prefix)/lib (usually /usr/local/lib). The configuration file is structured on sections, each section containing variables in the following format:
variable_name = first_field;second_field; ...
After the 'variable_name' at least one space or tab is required. All characters after a '#' are ignored and if you comment a section name, the whole section is ignored.
The default configuration file .gitrc.TERM supports most of the usual commands. To find out more about them please read it. git allows you to change both the utility used to perform a particular operation (using compress instead of gzip :-) ) and the key associated with it. There is also possible to remove/add new commands.
The configuration file contains the following sections: