GIT is a set of interactive tools. It contains an extensible
file system browser, an ascii/hex file viewer, a process viewer/killer
and some other related utilities and shell scripts. It can be used to
increase the speed and efficiency of most of the daily tasks such as
copying and moving files and directories, invoking editors, compressing
and uncompressing files, creating and expanding archives, compiling
programs, sending mail, etc. It looks nice, has colors (if the standard
ANSI color sequences are supported) and is user-friendly.
GIT runs on a wide variety of UNIX systems because it uses
the GNU Autoconf package to get system specific information.
Please refer to the PLATFORMS file included in the standard distribution
for a detailed list of systems on which GIT has been tested.
One of the main advantages of GIT is its flexibility. It is not
limited to a given set of commands. The configuration file can be
easily enhanced, allowing the user to add new commands or file
operations, depending on its needs or preferences.
GIT also provides a shell like command prompt, just to make sure
that the entire power of the UNIX shell commands is still there.
GIT is "free software"; this means that everyone is free to use
it and free to redistribute it on certain conditions. GIT is not
in the public domain; it is copyrighted and there are restrictions on
its distribution, but these restrictions are designed to permit
everything that a good cooperating citizen would want to do. What is
not allowed is to try to prevent others from further sharing any version
of GIT that they might get from you. The precise conditions are
found in the GNU General Public License that comes with GIT and
also appears following this section.
The easiest way to get a copy of GIT is from someone else who has
it. You need not ask for our permission to do so, or tell any one else;
just copy it. If you have access to the Internet, you can get the
latest distribution version of GIT from host `ftp.gnu.org'
using anonymous login. See the file `/pub/gnu/GETTING.GNU.SOFTWARE' on
that host to find out about your options for copying and which files to
use.
You may also receive GNU Interactive Tools when you buy a
computer. Computer manufacturers are free to distribute copies on the
same terms that apply to everyone else. These terms require them to
give you the full sources, including whatever changes they may have
made, and to permit you to redistribute the GNU Interactive Tools
received from them under the usual terms of the General Public License.
In other words, the program must be free for you when you get it, not
just free for the manufacturer.
The GIT package contains three interactive programs and a few
additional utilities. Here there is a description of each of them.
gitfm is a file system browser with some shell like features
designed to make your work much easier and much efficient. It displays
one or two panels, each one containing a file system directory. You can
browse the directory tree with the usual cursor keys, pressing
ENTER when you want to enter or leave a directory and TAB
when you want to change the panels.
Under the two panels there is a shell like input line which you can use to type normal shell commands. The input line can handle an unlimited number of characters and keeps a history of typed commands (using the GNU history library).
Under the input line there is a status bar. You can see there the status of the currently executed command, the warnings and errors and you will be prompted if a decision has to be taken.
gitfm now follows a new, easy to remember, scheme to bind commands
on keys. This is only a convention, if you define new key bindings you
may, or may not follow it.
All the file commands start with ^C. This prefix can be followed by some modifiers, in order to affect the default behavior of the given command. These modifiers are b and r.
b - this modifier specifies that the command will run in background:
^CM = CHMOD; chmod %s{New mode of %i: ,%m} %i;;;;y
defines a command that changes the current selected files mode in foreground, while
^CbM = B-CHMOD; chmod %s{New mode of %i: ,%m} %i&;;;;y
defines a background command that does the same thing.
r - this modifier specifies that the command will be run recursively:
^CrM = R-CHMOD; chmod -R %s{New mode of %i: ,} %i;;;;y
defines a command that recursively changes the mode of the selected entries.
The b and r modifiers can be combined, the resulting command running recursively and in background:
^CbrM = B-R-CHMOD; chmod -R %s{New mode of %i: ,} %i&;;;;y
You should also note that for some commands (like gzip) there is
no need for a non-recursive version. Running gzip recursively on
files is harmless. If there is a directory between these files,
gzip will recursively compress that directory, so you can use the
same key binding for recursively and non-recursively compressing. In
fact, it is a matter of selecting files or directories.
Unfortunately, we can't run chmod recursively trying to change
the mode of all the files in a directory to 0644 because that directory
might contain subdirectories and removing the execution permission from
them is a bad idea. So, in this case, we need separate commands.
This is a brief description of the command line arguments.
-h print this help message
-v print the version number
-c use ANSI colors
-b don't use ANSI colors
-l don't use the last screen character
-p output final path at exit
The -p option can be used to make gitfm force bash (assuming that
you're using it as your shell) chdir to the last directory gitfm was in
before quitting. In order to do this, you need to invoke gitfm using this
function (put it into your .profile):
function g
{
gitfm -p $ 3> /tmp/gitfm.p.$$
if test -s /tmp/gitfm.p.$$; then
if test -d "`cat /tmp/gitfm.p.$$`"; then
cd "`cat /tmp/gitfm.p.$$`"
else
cd
fi
fi
rm -f /tmp/gitfm.p.$$
}
This will not work if you suspend gitfm. Nothing bad will happen, just the chdir will not be performed.
gitfm has three major modes of displaying the panels. In the first
(default) mode, two panels are displayed, each one using half of the
screen. In the second mode, only one panel uses the entire screen. In
the third mode, only the status bar and the input line are displayed,
both panels being hidden.
Briefly, a panel can use the entire screen or just half of it. Even when a panel is hidden, it still exists.
Users can switch between these three major modes as needed:
^X 0
Enlarges the other panel to use the entire screen. It also changes the
minor mode to `Enable all'. The current panel will become
invisible (`enlarge-other-panel').
Enlarges the current panel to use the entire screen. It also changes
the minor mode to `Enable all'. The other panel will become
invisible (`enlarge-panel').
Switches back to the two panel mode (`two-panel-mode').
Switches to the tty mode (no panels on the screen) (`tty-mode').
Basically a panel displays the files and directories in a directory. You can optionally specify some additional information about each entry (file, directory, ...) to be displayed (a minor mode).
When using the full screen mode, all the minor modes here can be used. In half screen mode, the `panel-enable-all' mode is not available.
These are the panel minor modes: ESC e o
Display the entry owner and group (`panel-enable-owner-group').
Display the entry date and time (`panel-enable-date-time').
Display the entry size (`panel-enable-size').
Display the entry mode (`panel-enable-mode').
Display the entry full name (`panel-enable-full-name').
Display the entire information about file (`panel-enable-all'). This mode is only available if the panel has been enlarged to use the entire screen with `enlarge-panel' or `enlarge-other-panel' (`panel-enable-all').
There is also another way to change the panel minor modes:
^], ^[]
Switches to the next panel minor mode (`panel-enable-next-mode').
Entries in a panel can be sorted in different ways. These are the available options:
ESC s n
Display the panel entries sorted by their names
(`panel-sort-by-name').
Display the panel entries sorted by their extensions
(`panel-sort-by-extension').
Display the panel entries sorted by their sizes
(`panel-sort-by-size').
Display the panel entries sorted by their `last modified' stamps (`panel-sort-by-date').
Display the panel entries sorted by their modes
(`panel-sort-by-mode').
Display the panel entries sorted by their owner ids
(`panel-sort-by-owner-id').
Display the panel entries sorted by their group ids
(`panel-sort-by-group-id').
Display the panel entries sorted by their owner names
(`panel-sort-by-owner-name').
Display the panel entries sorted by their group names
(`panel-sort-by-group-name').
There is also another way to change the sort method:
ESC s u
Switch to the next panel sort method (`panel-sort-next-method').
Moving the cursor in the panel is very easy. If your keyboard has arrows, use them. If the arrow keys don't work (it might be due to a badly configured TERM environment variable), you can use the Emacs commands bindings as well.
UP, ^P
Move the cursor vertically up one entry (`previous-line').
Move the cursor vertically down one entry (`next-line').
Move the cursor on the first entry in the panel
(`beginning-of-panel').
Move the cursor on the last entry in the panel (`end-of-panel').
Move the cursor vertically down one page (`scroll-down').
Move the cursor vertically down one page (`scroll-up').
Scroll the panel entries to the left (`horizontal-scroll-left').
Scroll the panel entries to the right (`horizontal-scroll-right').
In order to optimize the screen output, you can modify the scroll step
(`set-scroll-step'). This is the number of lines to try scrolling
a panel when the cursor moves out. The `StartupScrollStep'
specifies the initial scroll step, but using `set-scroll-step' you
can dynamically change it.
Move the cursor in the other panel (`other-panel').
Switch the two panels. This command works even when gitfm is not
in the `two panels' mode (`switch-panels').
INS, ^T, ^X \, ^\
Toggle the `selected' flag of the current entry (`select-entry').
Select (marks) all the files matching at least one pattern from a space
separated list of shell patterns. Spaces and \s are allowed in the
patterns but they have to be escaped with a \. The user will be
prompted for a pattern to match against
(`select-files-matching-pattern').
Unselect (unmarks) all the files matching at least one pattern from a
space separated list of shell patterns. Spaces and \s are allowed in
the patterns but they have to be escaped with a \. The user will be
prompted for a pattern to match against
(`unselect-files-matching-pattern').
Select (marks) all the files having the same extension as the current
file. If the current file name doesn't have an extension or starts with
a dot, no files are selected (`select-extension').
Unselect (unmarks) all the files having the same extension as the
current file. If the current file name doesn't have an extension or
starts with a dot, no files are unselected (`unselect-extension').
See Selecting Files, for additional ways of selecting and unselecting files.
Users sometime need to search a file in a panel, especially when the
panel contains a big number of entries. For that reason gitfm
provides an incremental search feature. Using forward and backward
incremental search, files can be very easy located. Wrapped incremental
search is also provided.
^S, ^Xs
Incremental search forward a file name in the current panel
(`isearch-forward'). Pressing ^S or ^Xs again will
force gitfm to go to the next entry that matches the current
isearched string. When the end of the panel is reached, the isearch is
restarted from its beginning.
Incremental search backward a file name in the current panel
(`isearch-backward'). Pressing ^R or ^Xr again will
force gitfm to go to the next entry that matches the current
isearched string. When the beginning of the panel is reached, the
isearch is restarted from its end.
The input line is one of the main methods used by gitfm to interact
with the user. All the answers the user should give in order to perform
some operation and all the shell like commands are built using it. So
here is a description of all the basic editing operations that the
`input line' provides. They are very much inspired from
Emacs, so Emacs users should have no problem using them.
Typing characters is the most usual way of inserting text into the input
line. Key sequences starting with printable ascii characters are not
allowed in gitfm so typing a for example results in inserting
a at the current point position. Of course, there are some other
ways of inserting text into the command line and here there is a
description of most of them.
ESC RET
Copy the current entry name into the input line at the current point
position (`entry-to-input-line').
Copy the other panel path into the input line at the current point
position (`other-path-to-input-line').
Copy the names of all the selected entries into the input line at the
current point position (`selected-entries-to-input-line').
^B, LEFT
Move the point backward one character (`backward-char').
Move the point forward one character (`forward-char').
Move the point one word backward (`backward-word').
Move the point one word forward (`forward-word').
Move the cursor at the beginning of the input line (`beginning-of-line').
Move the cursor at the end of the input line (`end-of-line').
DEL, ^D
Delete the character under the cursor (`delete-char').
Delete the character before the cursor (`backward-delete-char').
Delete backward one word (`backward-kill-word').
Delete forward one word (`kill-word').
Delete the entire line (`kill-line').
Delete all the characters between the beginning of the input line and
the point (`kill-to-beginning-of-line').
Delete all the characters between the point and the end of the input
line (`kill-to-end-of-line').
Delete all the spaces around the point, leaving only one space
(`just-one-space').
Delete all the spaces around the point
(`delete-horizontal-space').
Save the region between the point and the mark into the kill "ring" and
then kills it (`kill-region'). Note that there is no real
kill-ring here. The so-called kill-ring has only one entry.
Save the region between the point and the mark without killing it
(`kill-ring-save').
ESC l
Convert the following word to lower case, moving over.
(`downcase-word').
Convert the following word to upper case, moving over.
(`upcase-word').
Capitalize the following word, moving over.
(`capitalize-word').
A separate history is kept for both built-in and user-defined commands. If you call a command that you have used before, you can re-edit a previously entered string in order to minimize the amount of characters needed to be typed for the new one. There is no limit on the number of strings that can be kept in the history.
ESC p
Walk backward through the history of previously entered strings
(`previous-history-element').
Walk forward through the history of previously entered strings
(`next-history-element').
^SPC
Set the mark at the current point position (`set-mark').
Exchange the current point position with the mark one
(`exchange-point-and-mark').
^Y
Reinsert a previously killed text at the current point position
(`yank').
If the very first character in the input line is a `+', what comes after it is considered a (space separated) list of shell patterns, and all the files that match at least one pattern from that list will be marked as selected. An empty list of shell patterns (i.e. the `+' by itself) will cause all the files to be selected.
If the very first character in the input line is a `-', the space separated list of shell patterns that follows is used to unselect files. An empty list of shell patterns (i.e. the `-' by itself) will cause all the selected files to be unselected.
Finally, if the first and only character in the input line is a `*', then all the selected files will become unselected, and all the unselected files will become selected.
F5, ESC 5, ^C C
Copy the currently selected entries to the user supplied path
(`copy').
Copy the currently selected entries to the user supplied path. The
operation is performed in background (`B-COPY').
F6, ESC 6, ^C T
Move the currently selected entries to the user supplied path
(`move').
Move the currently selected entries to the user supplied path. The
operation is performed in background (`B-MOVE').
The easiest way to create a new file is to start an editor passing the file name as an argument. Most editors will try to create the file if the file doesn't exist. See Editing Files, for more information.
F8, ESC 8, ^C D
Delete the currently selected entries (`delete').
Delete the currently selected entries. The operation is performed in
background (`B-DELETE').
^C H
Create a hard link from the current files to a user supplied file
name (`LINK').
Create a hard link from the current files to a user supplied file name
(`B-LINK'). The action is performed in background.
Create a symbolic link from the current files to a user supplied file
name (`SYMLINK').
Create a symbolic link from the current files to a user supplied file
name (`B-SYMLINK'). The action is performed in background.
^C R
Rename the current file or directory with the user supplied name
(`RENAME').
Rename the current file or directory with the user supplied name. The
operation is performed in background (`B-RENAME').
Change the name of all the selected entries to lowercase.
(`name-downcase').
Change the name of all the selected entries to uppercase.
(`name-upcase').
^C /
Split the current file into several smaller files of a given size and
named based on a given prefix (`SPLIT').
Split the current file into several smaller files of a given size and
named based on a given prefix. The operation is performed in background
(`B-SPLIT').
^C ~
Pack the files into the smallest number of bins. This is an
approximation - the problem is NP-complete and no known algorithm can
guarantee a solution better than `(11/9) * OPTIMAL + 4'.
To make things even worse, for large files, there is no portable way
to predict how many blocks the file system implementation will require
for indirect blocks, directories, etc. So keep in mind that this is
only an approximation.
Bin packing can be useful when you want to put a bunch of files on
floppies or zip disks and you want to optimize things a little bit
(`bin-packing').
`gitfm' assumes that you want to pack all the files in the current
directory - if there is any selected file in that directory it will be
unselected first. Then `gitfm' will ask for a bin size, and select
the files that should go in the first bin. You are supposed to place
those files in the first bin (e.g. a tar archive), remove them from the
current directory, then run `bin-packing' again, to obtain the list
of the files that should go into the second bin, etc.
^C M
Change the mode of the currently selected entries (`CHMOD').
Change the mode of the currently selected entries. The operation is
performed in background (`B-CHMOD').
Recursively change the modes of the selected entries if one of them is a
directory (`R-CHMOD').
Recursively change the modes of the selected entries if one of them is a
directory. The operation is performed in background (`B-R-CHMOD').
Change the owner of the currently selected entries (`CHOWN').
Change the owner of the currently selected entries. The operation is
performed in background (`B-CHOWN').
Recursively change the owners of the selected entries if one of them is
a directory (`R-CHOWN').
Recursively change the owners of the selected entries if one of them is
a directory. The operation is performed in background
(`B-R-CHOWN').
Change the group of the currently selected entries (`CHGRP').
Change the group of the currently selected entries. The operation is
performed in background (`B-CHGRP').
Recursively change the groups of the selected entries if one of them is
a directory (`R-CHGRP').
Recursively change the groups of the selected entries if one of them is
a directory. The operation is performed in background
(`B-R-CHGRP').
F4, ESC 4
Call the default editor with the current file name as an argument
(`EDIT').
Call the default editor with the selected entry names as arguments
(`MULTIPLE-EDIT').
Create a new file by calling the default editor with the user supplied
file name as an argument (`FILE-CREATE').
Call the default editor in order to edit the ChangeLog file (`CHANGE-LOG').
The default editor can be specified using the EDITOR or GIT_EDITOR environment variables. See Environment Variables, for more information.
F3, ESC 3
Call the default viewer (gitview) with the current file name as
argument (`VIEW').
Call the default pager (more) with the currently selected entry
names as arguments (`MULTIPLE-VIEW').
^C z
Compress the currently selected entries with gzip
(`COMPRESS').
Compress the currently selected entries with gzip. The operation
is performed in background (`B-COMPRESS').
Uncompress the currently selected entries with gunzip
(`UNCOMPRESS').
Uncompress the currently selected entries with gunzip. The
operation is performed in background (`B-UNCOMPRESS').
Uncompress the currently selected entries with gunzip
(`F-UNCOMPRESS'). Force uncompression of links.
Uncompress the currently selected entries with gunzip. Force
uncompression of links. The operation is performed in background
(`BF-UNCOMPRESS').
Compress the currently selected entries with bzip2
(`BZIP2-COMPRESS').
Compress the currently selected entries with bzip2. The
operation is performed in background (`B-BZIP2-COMPRESS').
Uncompress the currently selected entries with bunzip2
(`BZIP2-UNCOMPRESS').
Uncompress the currently selected entries with bunzip2. The
operation is performed in background (`B-BZIP2-UNCOMPRESS').
^C e
Encode the currently selected file (`UUENCODE').
Encode the currently selected file. The operation is performed in
background (`B-UUENCODE').
Decode the currently selected file (`UUDECODE').
Decode the currently selected file. The operation is performed in
background (`B-UUDECODE').
Encode the currently selected file using mpack (`MIME-PACK').
Encode the currently selected file using mpack. The operation is
performed in background (`B-MIME-PACK').
Decode the currently selected file using munpack (`MIME-UNPACK').
Decode the currently selected file using munpack. The operation is
performed in background (`B-MIME-UNPACK').
^C p
Encrypt (using pgp) the current file (`ENCRYPT').
Decrypt (using pgp) the current file (`DECRYPT').
^C =
Compare (using diff) the current ASCII file with the other
panel's current file (`DIFF'). If both entries are directories, a
recursive diff is performed.
Compare (using diff) the current ASCII file with its latest
backup. The latest backup is the file having the same name and a '~' at
the end (`LAST-BACKUP-DIFF').
Compare the current file with the other panel current file. A binary
comparison is performed (`compare').
^X I
Run the ispell command with the current file name as an
argument.
^C j
Print the selected files vialprto the user specified printer or to the default one if nolproptions are given (`PRINT-JOB').
^C J
Print the list of active printing jobs vialpq. The default printer is queried if nolpqoptions are given (`PRINT-JOB-LIST').
^C W
Call gitwipe to wipe the selected files. Asks for confirmation
before actually wiping them in order to avoid errors (`WIPE').
See gitwipe, for more information.
ESC %
Searche files on the file system, starting from the current directory
(`FIND').
Use 'locate' to search files on the file system, starting from the
current directory (`LOCATE').
Locate the binary, source, and manual page files for a command
(`WHEREIS').
Locate a command; display its pathname or alias (`WHICH').
^C a
Create a tar archive containing all the currently selected
entries (`TAR').
Create a tar archive containing all the currently selected
entries. The operation is performed in background (`B-TAR').
Create a compressed tar archive containing the current entry,
provided it is a directory (`TAR-COMPRESS').
Create a compressed tar archive containing the current entry,
provided it is directory. The operation is performed in background
(`B-TAR-COMPRESS').
Create a bzip2 compressed tar archive containing the current
entry, provided it is a directory (`TAR-BZIP2').
Create a bzip2 compressed tar archive containing the current
entry, provided it is a directory. The operation is performed in
background (`B-TAR-BZIP2').
Expand the selected archives into the current directory. The utility
used is selected based on the extension of the file
(`GENERIC-UNPACK').
Expand the selected archives into the current directory. The utility
used is based on the extension of the file. The operation is performed
in background (`B-GENERIC-UNPACK').
^C V
Expand the selected archives into an user supplied current directory.
The utility used is selected based on the extension of the file
(`GENERIC-UNPACK-INTO').
Expand the selected archives into an user supplied directory. The
utility used is based on the extension of the file. The operation is
performed in background (`B-GENERIC-UNPACK-INTO').
Red Hat Linux Distributions use a very powerful package manager called
rpm. It is used whenever you need to install/remove/upgrade/etc
a software package. The packages used by rpm use the extension
`.rpm'. gitfm provides default key bindings for some of the
basic operations rpm can perform on packages: install, uninstall,
upgrade and query.
^C I
Install the rpm package pointed by the cursor
(`RPM-INSTALL').
Install the rpm package pointed by the cursor
(`B-RPM-INSTALL'). The operation is performed in background.
Uninstall the rpm package pointed by the cursor
(`RPM-UNINSTALL').
Uninstall the rpm package pointed by the cursor
(`B-RPM-UNINSTALL'). The operation is performed in background.
Upgrade the rpm package pointed by the cursor
(`RPM-UPGRADE').
Upgrade the rpm package pointed by the cursor
(`B-RPM-UPGRADE'). The operation is performed in background.
Query therpmpackage manager (`RPM-QUERY'). The default options used are `-qil'. See therpmmanual page for more details on usingrpm.
^C t
Print the type of a file using the file utility
(`FILE-TYPE').
^C m d, ^C m ^D
Change the current MSDOS directory to a given directory
(`MTOOLS-CHDIR').
Put the currently selected files on a MSDOS floppy
(`MTOOLS-PUT').
Put the currently selected files on a MSDOS floppy
(`B-MTOOLS-PUT'). The operation is performed in background.
Get some files from a MSDOS floppy and put them in a given
directory (`MTOOLS-GET').
Get some files from a MSDOS floppy and put them in a given
directory (`B-MTOOLS-GET'). The operation is performed in
background.
Delete files from a MSDOS floppy (`MTOOLS-DELETE').
Delete files from a MSDOS floppy (`B-MTOOLS-DELETE'). The
operation is performed in background.
List files and directories on a MSDOS floppy (`MTOOLS-DIR').
Format a MSDOS floppy (`MTOOLS-FORMAT').
Format a MSDOS floppy (`B-MTOOLS-FORMAT'). The operation is
performed in background.
Create a directory on a MSDOS floppy (`MTOOLS-MKDIR').
Create a directory on a MSDOS floppy (`B-MTOOLS-MKDIR').
The operation is performed in background.
Remove a directory from a MSDOS floppy (`MTOOLS-RMDIR').
All the files and subdirectories in that directory are removed as well.
Remove a directory from a MSDOS floppy (`B-MTOOLS-RMDIR').
All the files and subdirectories in that directory are removed as well.
The operation is performed in background.
Rename a file or directory on a MSDOS floppy
(`MTOOLS-RENAME').
Rename a file or directory on a MSDOS floppy
(`B-MTOOLS-RENAME'). The operation is performed in background.
Display the contents of a file located on a MSDOS floppy
(`MTOOLS-TYPE').
Many files on UNIX systems have one or more extensions specifying
their types. For example, a file that ends in `.c' is a file
containing a C program, while a file ending in `.tar.gz' is
a tar archive compressed with the gzip utility. Having a
default action for each file type, binded on the same key, seems to be a
good idea because you can use that key to obtain type specific
information about a file or to process it in some type specific way much
easier. The GIT package contains a script called
gitaction that is used to detect the current file type and
perform a type specific action. See gitaction, for more information.
F2, ESC 2, ^X a
Perform an action on the current file, depending on its type
(`FILE-ACTION').
F7, ESC 7, ^X M
Create a new subdirectory in the current directory with the user
supplied name (`make-directory').
F5 (for directories), ESC 5 (for directories), ^C C (for directories)
Copy the currently selected entries to the user supplied path
(`copy').
Copy the currently selected entries to the user supplied path. The
operation is performed in background (`B-COPY').
F8 (for subdirectories), ESC 8 (for directories), ^C D (for subdirectories)
Delete the currently selected entries (`delete').
Delete the currently selected entries. The operation is performed in
background (`B-DELETE').
F6 (for directories), ESC 6 (for directories), ^C T (for directories)
Move the currently selected entries to the user supplied path
(`move').
Move the currently selected entries to the user supplied path. The
operation is performed in background (`B-MOVE').
^C R (for directories)
Rename the current file or directory with the user supplied name
(`RENAME').
Rename the current file or directory with the user supplied name. The
operation is performed in background (`B-RENAME').
^C c q
Quickly compare the files in the left panel with the files in the right
one. Only the file names, sizes and time stamps are considered in the
comparison.
Compare the files in the left panel with the files in the right one.
The contents of each file in the current panel will be compared against
the contents of its couterpart (if any) from the other panel.
Recursively compare (using diff -r -q) the current directory with
the other panel's current directory (`FAST-DIFF'). Print on
standard output the names of the files that differ.
Compare (using diff) the current directory with the other panel
current directory. For successful operation, both panels should contain
the same directory (`DIR-DIFF').
Compare (using diff) the current directory with the other panel
current directory. For successful operation, both panels should contain
the same directory. The operation is performed in background
(`DIR-DIFF').
^C U
Display the output of the du -s command on the status line
(`DIRECTORY-USAGE').
^X d, ^X ^D
Change the current working directory. The user is asked for a new
directory name and the new directory is added to the directory history
(`change-directory').
See Dirs History, for more information. ESC a c
Change the current directory of the current panel to the directory of
the other panel (`adapt-current-directory').
Change the current directory of the other panel to the directory of the
current panel (`adapt-other-directory').
Users usually work on a limited set of subdirectories. Providing a fast
method of switching between a number of intensively used directories is
a good idea and gitfm has a set of builtin commands for doing it.
Usually new directories are added to the directory history when the
`change-directory' built-in command is used. gitfm also adds
the current directory to the history list when started, when the
directory history is reseted and when a command having a non empty
`new-dir' field successfully completes its execution.
See new-dir, for more information.
^X ^N
Go to the next directory in the history (`next-directory').
Go to the previous directory in the history
(`previous-directory').
Reset the entire directory history. As explained above, the current
directory becomes the only directory in the history
(`reset-directory-history').
gitfm provides default key bindings for switching to a number of
important directories as "/", "..", "$HOME", etc.
ESC /
Go to the `/' directory (`ROOT-DIR').
Go to the `..' directory (`up-one-dir').
Go to the `~' ($HOME) directory (`HOME-DIR').
Go to the `/usr/include' directory (`INCLUDE-DIR').
Go to the `/mnt/fd0' directory (`FIRST-FLOPPY-DIR').
Go to the `/mnt/fd1' directory (`SECOND-FLOPPY-DIR').
F9, ESC 9, ^X m
Run the make command in the current directory. Use -k as the
default option (`MAKE').
Run the make command in background in the current directory
(`B-MAKE').
See gitaction, for more information.
^C 2 a
Send the current current ascii file by mail to an user supplied email
address (`ASCII-MAIL').
The same as `ASCII-MAIL', the only difference being that the command runs in background (`B-ASCII-MAIL').
Send the current current binary file by mail to an user supplied list of
email addresses. The file is uuencoded first (`BINARY-MAIL').
The same as `BINARY-MAIL', the only difference being that the command runs in background (`B-BINARY-MAIL').
Send the current current binary file by mail to an user supplied list of
email addresses. The file is encoded with mpack first
(`MIME-MAIL').
The same as `MIME-MAIL', the only difference being that the command runs in background (`B-MIME-MAIL').
Run the emacs -f rmail command. This will start the Emacs's
`rmail' function so that you can read your mail (`READ-MAIL').
^X z
Call a sub-shell as specified by the $GIT_SHELL environment
variable (`SUB-SHELL').
See Environment Variables, for more information.
^X g
Search using grep all the selected files for a given pattern
(`GREP').
Search recursively using gitrgrep all the user specified files
and directories for a given pattern (`RECURSIVE-GREP').
See gitrgrep, for more information.
Having a lock feature might be a good idea and, since not all the
UNIX systems provide one, gitfm tries to get around the
problem ...
^X p
Prompt the user for a password and locks the console until the same
password is reinserted (`lock').
Sometimes your screen needs to be refreshed. Just think about what happens when somebody wants to talk with you and the talk daemon writes something like this
Message from Talk_Daemon@galei.cs.vu.nl at 12:15 ...
talk: connection requested by andrei@galei.cs.vu.nl.
talk: respond with: talk andrei@galei.cs.vu.nl
on your screen. And sometimes you might also want to re-read the
current directories. gitfm provides a built-in command for
refreshing the screen contents.
^L
Re-read the directories contents and refresh the screen (`refresh').
^X ^L
Call reset in order to reset the terminal to its default
settings (`TTY-RESET').
People dealing with lots of files usually need to save/restore/copy
files from/to other file systems. In order to be more efficient,
gitfm provides a set of key bindings for mounting and unmounting
file systems. See gitmount, for more information.
The default key bindings set has been designed to work under
Linux, but it can be easily changed for other UNIX systems
with different device names. Reading the configuration file
.gitrc.common should be enough. See Hot Keys, for more
information.
As a convention, the `/mnt' directory is used to store an empty
subdirectory for each mountable file system. Each file system is
actually mounted in its counterpart `/mnt' subdirectory. Try to
follow this convention since the gitmount script is heavily based
on it. See Customization, for more information.
ESC m a
Call mount(1) in order to mount the first floppy
(`/dev/fd0') in the `/mnt/fd0' directory (`MOUNT-A').
Call mount(1) in order to mount the second floppy
(`/dev/fd1') in the `/mnt/fd1' directory (`MOUNT-B').
Call mount(1) in order to mount the cdrom
(`/dev/cdrom') in the `/mnt/cdrom' directory (`MOUNT-CDROM').
Call mount(1) in order to mount the first floppy
(`/dev/fd0') in the `/mnt/floppy' directory (`MOUNT-FLOPPY').
Call mount(1) in order to mount the zip drive
(`/dev/zip') in the `/mnt/zip' directory (`MOUNT-ZIP').
Call mount(1) in order to mount the jaz drive
(`/dev/jaz') in the `/mnt/jaz' directory (`MOUNT-JAZ').
Call mount(1) in order to mount the file systems corresponding to
the selected subdirectories. For example, if you are in the `/mnt'
directory and the `cdrom' and `zip' subdirectories are
selected, the cdrom and the zip disk will be mounted (`MOUNT-THESE').
Call umount(1) in order to remove (unmount) the first floppy
(`/dev/fd0') (`UMOUNT-A').
Call umount(1) in order to remove (unmount) the second floppy
(`/dev/fd1') (`UMOUNT-B').
Call umount(1) in order to remove (unmount) the cdrom
(`/dev/cdrom') (`UMOUNT-CDROM').
Call umount(1) in order to remove (unmount) the first floppy
(`/dev/fd0') (`UMOUNT-FLOPPY').
Call umount(1) in order to remove (unmount) the zip drive
(`/dev/zip') (`UMOUNT-ZIP').
Call umount(1) in order to remove (unmount) the jaz drive
(`/dev/jaz') (`UMOUNT-JAZ').
Call umount(1) in order to remove (unmount) the file systems
mounted into the selected subdirectories. For example, if the current
directory is `/mnt' and the `cdrom' and `zip'
subdirectories are selected, the cdrom and the zip disk will be
unmounted (`UMOUNT-THESE').
^X T
Call date(1) in order to display the current time/date
(`DATE').
Call finger(1) in order to display information about local and
remote users (`FINGER').
Call mount(1) in order to display a list of the currently
mounted file systems (`MOUNTED-FILE-SYSTEMS').
Call quota(1) in order to display a user file system disk quota
and quota (`QUOTA').
Call df(1) in order to get the status of the currently mounted
file systems (`DISK-FREE-SPACE').
Call users(1) in order to get the name of the currently logged in
users (`USERS').
Call$GIT_VMSTAT(1) in order to get the current virtual memory status. This is very system dependent,Linuxusesfree, other systems usevmstat, so the $GIT_VMSTAT variable is used to deal with this (`VIRTUAL-MEMORY-STATUS').
See Environment Variables, for more information. ESC S w
Call who(1) in order to find out who is on the system
(`WHO').
^X E
Call env(1) in order to display the current environment
(`ENV').
Call xhost(1) in order to add/remove hosts names to the list
allowed to make connection to the X server (`XHOST').
There are at least two kinds of ps(1) utilities. One that
accepts (more or less) combinations of the 'a', 'u', and 'x' flags and
another that accepts combinations of 'e', 'f' and 'l' flags. Since is
quite difficult to test which one works fine on a given UNIX
system, gitfm provides key bindings for both of them. Anyway, if
your ps(1) fails to accept the predefined combinations, please
take a look in its manual and then modify the .gitrc.TERM file as
needed.
Since the number of possible combinations of flags in the ps
command line is quite big and *very* system dependent, there is no real
reason to display them all here. We are only interested in giving you
a starting point in your search through the .gitrc.TERM file.
Note also that you can display a list of processes using ps(1) or
browse through a list of them (killing as needed) using gitps.
As a convention, we have used the same key sequence for a given set of
ps(1) flags for both ps(1) and gitps, the only
difference being that ps(1) keys end in an uppercase letter.
See gitps, for more information.
Under Linux it is possible to see a tree of processes using
pstree(1).
Here there are the default key bindings for the 'e', 'f' and 'l'
ps(1) flags combinations:
ESC P b, ESC P c, ESC P e
Callgitpsorps(1) in order to browse through or display a list of currently running processes (`GITPS', `PS').
... and the default key bindings for the 'a', 'u' and 'x' ps(1)
flags combinations:
ESC P a, ESC P l, ESC P u ESC P x, ESC P y
Callgitpsorps(1) in order to browse through or display a list of currently running processes (`GITPS', `PS').
Call pstree(1) in order to displat the tree of currently running
processes (`PSTREE').
Call kill(1) in order to kill a user specified process with a
given signal (`KILL').
^X S
Call sync(1) in order to synchronize all the file systems
(`SYNC').
^X q
Read a manual page. The user is prompted for its name (`MAN').
Read an info documentation. The user is prompted for the documentation
name (`INFO').
Read the html documentation using the viewer specified in
GIT_BROWSER, or with lynx if GIT_BROWSER is not set
(`HTML').
F10, ESC 0, ^X ^C, ^X c
Exit GNU Interactive Tools (`exit').
gitps is an interactive process viewer/killer. It calls
internally the ps(1) utility. This is a brief description of the
command line arguments.
-h print this help message
-v print the version number
-i print the installation directory
-c use ANSI colors
-b don't use ANSI colors
-l don't use the last screen character
-p pass the remaining arguments to ps(1)
Running gitps it is self explanatory. Use the arrows,
PageUp, PageDown, Home, End, ^N, ^P,
^V, ESC v, Space and Backspace to move in the
list, ^L to refresh it, Enter to change the default signal
and F10, q or ^X ^C to leave.
You can change these keys, just read the GITPS-Setup, GITPS-Color, GITPS-Monochrome and GITPS-Keys sections in the configuration files .gitrc.TERM.
gitview is an ASCII/HEX file viewer. Use the arrows,
PageUp, PageDown, Home, End, ^N, ^P,
^V, ESC v, Space and Backspace to move in the
file, ^L to refresh the screen and F10, q or ^X
^C to leave.
You can change these keys, just read the GITVIEW-Setup, GITVIEW-Color, GITVIEW-Monochrome and GITVIEW-Keys sections in the configuration files .gitrc.TERM.
Here is a brief description of the command line arguments:
-h print this help message
-v print the version number
-i print the installation directory
-c use ANSI colors
-b don't use ANSI colors
-l don't use the last screen character
gitkeys is a program that displays the key sequence sent by the
pressed key. This is the key sequence received by GIT tools, so
this program is useful when setting up the .gitrc.TERM
configuration files.
gitwipe is an utility for wiping files. It overwrites the file
contents with a random sequence of numbers and then calls sync().
Note that gitwipe does *not* remove the wiped file since (under
Linux at least) the sync() system call might return before
actually writing the new file contents to disk. Removing the file might
be dangerous because some file systems can detect that the blocks in the
removed wiped file are no longer used and never write them back to disk
in order to improve performance. It is up to you to remove the file(s)
at a later moment.
gitmount is a script that allows you to mount a list of block
devices (specified in the command line), without specifying the file
system type. With a command like `gitmount fd0 cdrom' the first floppy
will be mounted in /mnt/fd0 and the cdrom will be mounted in
/mnt/cdrom. Make sure your /etc/fstab settings are
correct.
You don't need to know the file system type anymore. If you want to use
gitmount with the block device /dev/xxx then the directory
/mnt/xxx is created if it doesn't exist. gitmount will
attempt to create the necessary directories, but root permissions might
be required.
gitaction is a script that executes a different action for each
file type specified. It is called by the gitfm program when
pressing F2, ESC 2 or ^Xa.
The first parameter is the current directory name and the second one is the file name to be matched against the default patterns. The matching is done using the shell 'case' statement.
If you press F2, ESC 2 or ^Xa on a *.c file,
gitfm will compile it, if you press F2, ESC 2 or
^Xa on a *.tar.gz file, gitfm will list the tar
archive contents, if you press the same keys on a *.gz file,
gitfm will display its uncompressed contents on the screen, etc
...
If you want to find out what the default action for each file type is
(or if you want to modify it), just read/modify the gitaction
script. If no pattern is found, the file is displayed using
more.
If you press F2, ESC 2 or ^Xa on a *.gif file
or *.jpg file and you have the zgv utility installed, you
will be able to see it. If you want to change the gif/jpeg viewer, all
you need to do is to change its name in the gitaction script.
Also, you can add a .gitaction shell script in your home
directory and/or in any other directory. Before trying to match a file
name, gitaction will attempt to execute ./.gitaction. If
that one fails to match the file name against its patterns, it backs up
to $HOME/.gitaction. When this one fails too the patterns in
gitaction are tried. For an example of how to write .gitaction
scripts take a look at the .gitaction shell script provided as
part of the distribution and installed in the
/usr/share/doc/git/examples/ directory.
gitunpack is a shell script that accepts a directory and a set of
archives as its command line parameters, and then attempts to unpack
those archives in the given directory, selecting the utility used to
unpack the archives based on the archive extensions.
gitrgrep is a very small script that calls grep
recursively. It accepts grep like options / parameters, the only
difference being that file specifications should be quoted:
gitrgrepmain '*.c' orgitrgreperrno '*.c *.h'
gitregrep and gitrfgrep are recursive versions of the
egrep and fgrep programs.
The configuration files use shell environment variables to call the shell, editor, mail reader, html viewer, compress and virtual memory status utility. That means that if you set GIT_SHELL, GIT_EDITOR, GIT_RMAIL, GIT_BROWSER, or GIT_VMSTAT to some value, that value will be used instead of the default one. The defaults are:
GIT_SHELL='/bin/sh'
GIT_EDITOR='sensible-editor'
GIT_RMAIL='emacs -f rmail'
GIT_PAGER='sensible-pager'
GIT_VMSTAT='free'
GIT_BROWSER='sensible-browser'
If SHELL is defined, GIT_SHELL will be set to that value. If EDITOR is defined, GIT_EDITOR will be set to that value. If you want to change the default settings, put something like this into your .profile:
export GIT_SHELL='/usr/local/bin/bash'
export GIT_EDITOR='emacs'
export GIT_RMAIL='elm'
export GIT_PAGER='less'
export GIT_VMSTAT='vmstat'
export GIT_BROWSER='netscape'
There is one configuration file per terminal type in GIT. The
configuration file(s) reside in the user's home directory or (the
default versions) in the directory /usr/share/git/).
Their 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).
Since most of the key bindings are common to all the terminal types, a
configuration file called .gitrc.common is parsed before parsing
the normal .gitrc.TERM configuration file, the later one defining
only those keys that are terminal specific. However, if a key binding
is redefined in the .gitrc.TERM file, that binding will be used.
If the GIT package have been compiled without passing the
`--enable-terminfo' option to the configure script and your
system has a huge `termcap' database (/etc/termcap), you can
copy the termcap definition(s) of your terminal(s) in a file called,
lets say .termcap and put it in your home directory. After that,
set your TERMCAP environment variable to point to it. You should
add something like this to your .profile:
TERMCAP=/home/mike/.termcap
The interactive programs in the GIT package 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 file
will lead to a faster start.
The .gitrc.TERM it is first time searched in the home directory then, if not found, in the directory /usr/share/git/). The configuration file is structured in 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.
Section names are enclosed in rectangular brackets (`[' and `]'). Note that this manual don't include them while refering to section names.
The GIT package contains three major programs: gitfm,
gitps and gitview. Each one has its own sections in the
configuration files. There is also a global setup section called
`Setup' that is used by all these programs.
Note that now git has been renamed to gitfm,
the corresponding sections have been renamed to GITFM,
however for backwards compatibility, the old name (GIT)
is still checked if the GITFM section is not found.
GIT contains three interactive programs. Their names are:
gitfm (this is the file system browser), gitps (this is the
process viewer/killer and gitview (this is the ASCII/HEX file
viewer). Each one of these programs has its own set of key bindings.
The convention used in describing key bindings are very simple. Here
there are some examples that will help you to understand them. The
corresponding Emacs conventions will help you even more.
^A means keeping the Ctrl key down and pressing the a key (C-a).
The ESC character is represented as ^[ so that you can use the meta character (M- ) where available (or the ESC key):
^[a corresponds to M-a (pressing the ESC key and then a).
The ^ character is represented as ^^.
The backspace character is represented as ^_.
The Ctrl-SPACE character (C-SPC) is represented as ^$.
The space (SPC) character is represented as ^@.
Note that the key bindings notation described here is only used in the configuration files. For the sake of readability this manual uses ESC for the ESC key, SPC for the SPACE key and RET for the RETURN (ENTER) key.
In this section the variables have only one field.
`AnsiColors'
This variable should be set to `ON' if the terminal supports
standard `ANSI' color sequences. Otherwise it should be
`OFF'. If `AnsiColors' is `ON', `GITxxx-Color'
sections will be used in the configuration files .gitrc.TERM.
Otherwise, GIT interactive programs will use the
`GITxxx-Monochrome' sections.
`UseLastScreenChar'
This variable is used for terminals that can't write on the last
character of the screen without scrolling the entire screen. If your
terminal has no problem writing there (Linux console, vt100,
vt102, xterm, ...) set it to `ON'. Otherwise (hpterm), it should
be `OFF'.
`StartupScrollStep'
This variable specifies the scroll step initial value for both panels.
In this section the variables have only one field.
`StartupFileDisplayMode'
This variable specifies the file specific information displayed at startup. It can be any of `OwnerGroup', `DateTime', `Size', `Mode' or `FullName'. Its value initially affects both panels but it can be changed separately afterward.
`StartupFileSortMethod'
This variable specifies the startup sort method. It can be any of `Name', `Extension', `Size', `Date', `Mode', `OwnerId', `GroupId', `OwnerName' or `GroupName'. Its value initially affects both panels but it can be changed separately afterward.
`ConfirmOnExit'
If this variable is `ON', the user is prompted for confirmation at exit.
`HistoryFile'
This variable specifies the history file name. The default value is ~/.githistory.
`InfoDisplay'
If this variable is `OFF', auxiliary file informations are not displayed. This can be useful if you are using a very slow terminal.
`LeadingDotMatch'
If this variable is `OFF' when matching files for select-files-matching-pattern / unselect-files-matching-pattern then the leading '.' in the file name is matched only explicitly.
`TypeSensitivity'
If this variable is `OFF', colors are not used when displaying files. Normally, the information in the `GITFM-FTI' section is used to display files with different colors, depending on their types. Note that `TypeSensitivity' is automatically set to `OFF' when `AnsiColors' is `OFF'. See GITFM-FTI, for mor information.
`NormalModeHelp' `CommandLineModeHelp'
These variables describe the status bar contents for each gitfm
mode when no errors occurred. gitfm can display on the status bar
a help string and/or some system information (system type, hostname,
machine type and the current date) using escape characters:
\s -> the system type
\h -> the host name
\m -> the machine type
\d -> the current date
See Modes, for more information.
In this sections the variables have only one field.
These section allows you to customize the colors of gitfm. Reading
the .gitrc.TERM configuration file is self explanatory.
In this sections the variables have only one field.
These section allows you to customize the appearance of gitfm on
monochrome displays. Reading the .gitrc.TERM configuration file
is self explanatory.
These section describes the actions gitfm takes when a specified
key is pressed. A variable can have up to 6 fields separated by ';'.
Each line in this section looks like:
`key-sequence' = `command-name';`formatted-command';`new-dir'; `save-screen';`pause';`hide'
Note that you can't continue the variable fields description on the next line.
`key-sequence' is the key sequence associated with the given command. You can use any key sequence that doesn't start with an ascii character (0x20 to 0x7e).
Symbolic key names (F0, F1, F2, ... F10,
UP, DOWN, RIGHT, LEFT, INS, DEL,
HOME, END, PGUP and PGDOWN) can be used instead
of the key sequence. If some keys don't have a `termcap'/
`terminfo' description (like the F11/F12 keys on the
Linux console) you can specify the key sequence in the usual way.
`command-name' is a command generic name. Even if it is not always used, the `command-name' must be present (if a command is associated with a `key-sequence'). If it is not, no action will be taken when pressing `key-sequence'.
There are two types of commands in gitfm: built-in commands and
user defined commands. If the `command-name' section contains a
built-in command specification, the other fields are ignored.
Note that by convention built-in command names contain only lower case letters while user defined command names contain only upper case letters.
- `formatted-command' is a shell command which can contain some scanf like format specifiers. They are used to get the current entry name, owner, group, mode, etc.
Note that using uppercase `format specifiers' you will be able to access the other panel path, file and directory names, etc.
These are the available `format specifiers':
The format of %s is: %s{question,default_answer}.
When gitfm encounters a %s in the `formatted-command' it asks
the user the question `question' whose default answer is
`default_answer' and replaces the `%s{ , }' with the user's
answer. Both `question' and `default_answer' can contain any
other `format specifiers' except %s.
Note that there should be no spaces between %s and '{'.
gitfm will replace %f with the current directory entry name only if
it is a file (not a directory).
gitfm will replace %d with the current directory entry name only if
it is a directory (not a file).
gitfm will replace %l with the current directory entry name only if
it is a symbolic link with no target.
gitfm will replace %t with the current directory entry name only if
it is a named pipe.
gitfm will replace %z with the current directory entry name only if
it is a socket.
gitfm will always replace %a with the current directory entry name.
gitfm will always replace %m with the current file mode.
gitfm will always replace %g with the current file group.
gitfm will always replace %o with the current file owner.
gitfm will always replace %p with the current panel path.
gitfm will always replace %b with the current panel directory name.
gitfm will always replace %i with all the current panel selected
entry names.
The format of %? is: %?{confirmation}.
gitfm uses this format specifier only to ask for confirmation
before expanding / executing the current command. The
`confirmation' string is displayed and, if the user doesn't
confirm, the command is aborted. Otherwise, %?{confirmation} expands
to a null string and the command is expanded / executed normally.
If the `formatted-command' successfully exits (exit code = 0) or it has no body and this field is present then `new-dir' will become the current panel directory.
The character '~' used at the beginning of the `new-dir' field is replaced by the user's home directory.
This field is a character (usually 'y' or 'n') that tells gitfm to
save ('y') or not to save ('n') the terminal's screen after executing
the `formatted-command'. Saving the screen is not necessary while
editing or viewing a file because the information left after the editor
or the viewer exits is not important. Saving the screen means that that
screen will be restored before the execution of the next command.
Currently this field is used only if you are working as a super user
under Linux on a virtual console. Its default value is 'y'.
Users may wish to read some commands's results before repainting the panels. If this field is present gitfm will wait for a key to be pressed before restoring the panels. Its default value is 'n'.
Some commands that don't displaying any useful information if
successfully complete their execution: mount, chmod,
chown, chgrp, sync ... and, if an error occurs, a
line or two are sent to stderr. If this option is 'y', the stdout and
stderr will be redirected to some files (git.1.pid and
git.2.pid, where pid is gitfm's pid) and only if the
command's exit code is not 0, the git.2.pid file will be
displayed, line by line, onto the status bar. This way the panels will
not be deleted and then repainted and the command appears to be
built-in. git.1.pid and git.2.pid are created in the
temporary directory specified in the TMPDIR environment variable
(or "/tmp" if TMPDIR is not defined). The default value of the
hide field is 'n'.
This sections contains entries of the form:
`pattern' = `foreground'; `background'; `brightness'
where `pattern' is a file name matching pattern, `foreground', `background' and `brightness' are the color specification to be used when a file whose name match the given `pattern' is displayed in a panel. Colors can be turned off using the `TypeSensitivity' variable in the `GITFM-Setup' seection.
In this section the variables have only one field.
`Help'
This variable describe gitps's status bar contents.
In this sections the variables have only one field.
These section allows you to customize the colors of gitps.
Reading the .gitrc.TERM configuration file is self explanatory.
In this sections the variables have only one field.
These section allows you to customize the appearance of gitps on
monochrome displays. Reading the .gitrc.TERM configuration file
is self explanatory.
In this section the variables have only one field.
`Help'
This variable describe gitps's status bar contents.
In this sections the variables have only one field.
These section allows you to customize the colors of gitview.
Reading the .gitrc.TERM configuration file is self explanatory.
In this sections the variables have only one field.
These section allows you to customize the appearance of gitview
on monochrome displays. Reading the .gitrc.TERM configuration
file is self explanatory.
Background commands (& terminated)can be specified in the configuration file but their result (stdout and stderr redirection), will be overwritten by the result of newer commands and, if an error occurs, it will not be seen.
When gitfm is compiled for Linux, the default built-in color
descriptions are for color monitors, so you can't (decently) run
gitfm on a b/w monitor without the .gitrc.TERM file
correctly configured. .gitrc.TERM should be configured with
`AnsiColors' = OFF. However, if your system knows about the linux-m
terminal type, using that may be a better solution.
Job support is implemented only in gitfm.
Due to the fact that the ';' character is used as a field separator in the configuration files, you can't write something like that in the .gitrc.TERM files:
^AAA = SHOW-USERS-AND-GROUPS; more /etc/passwd; more /etc/group
because 'more /etc/group' will be considered as a directory to switch to. You must write a small script instead:
#! /bin/sh
more /etc/passwd more /etc/group
Supposing the script name is show_ug, the .gitrc.TERM line
will look like this:
^AAA = SHOW-USERS-AND-GROUPS; show_ug
There is no support for appearance modes on magic-cookie terminals.
Any questions, comments, or bug reports, should be emailed to `Tudor Hulubei <tudor@cs.unh.edu>'. Please include the version number.
^[]: Modes^]: Modes^A: Moving Point^B, LEFT: Moving Point^C -: Archive Files^C .: Compressing Files^C /: Splitting Files^C 2 a: Mail^C 2 b: Mail^C 2 m: Mail^C =: Comparing Files^C a: Archive Files^C B: Comparing Files^C b -: Archive Files^C b .: Compressing Files^C b /: Splitting Files^C b 2 a: Mail^C b 2 b: Mail^C b 2 m: Mail^C b a: Archive Files^C b C: Copying Files^C b C (for directories): Copying Dirs^C b d: Comparing Dirs^C b D: Deleting Files^C b D (for directories): Deleting Dirs^C b E: Encoding Files^C b e: Encoding Files^C b f Z: Compressing Files^C b G: Inode^C b H: Linking Files^C b i: RPM Packages^C b I: RPM Packages^C b K: Encoding Files^C b k: Encoding Files^C b M: Inode^C b m D: MSDOS Files^C b m F: MSDOS Files^C b m G: MSDOS Files^C b m K: MSDOS Files^C b m M: MSDOS Files^C b m P: MSDOS Files^C b m R: MSDOS Files^C b N: RPM Packages^C b o: Compressing Files^C b O: Inode^C b R: Renaming Files^C b R (for directories): Renaming Dirs^C b r G: Inode^C b r M: Inode^C b r O: Inode^C b S: Linking Files^C b T: Moving Files^C b T (for directories): Moving Dirs^C b V: Archive Files^C b X: Archive Files^C b x: Archive Files^C b z: Compressing Files^C b Z: Compressing Files^C C (for directories): Copying Dirs^C c q: Comparing Dirs^C c t: Comparing Dirs^C d: Comparing Dirs^C D (for directories): Deleting Dirs^C E: Encoding Files^C e: Encoding Files^C ESC =: Comparing Files^C f d: Comparing Dirs^C f Z: Compressing Files^C G: Inode^C H: Linking Files^C I: RPM Packages^C i: RPM Packages^C j: Printing Files^C J: Printing Files^C K: Encoding Files^C k: Encoding Files^C M: Inode^C m D: MSDOS Files^C m d, ^C m ^D: MSDOS Files^C m F: MSDOS Files^C m G: MSDOS Files^C m K: MSDOS Files^C m L: MSDOS Files^C m M: MSDOS Files^C m P: MSDOS Files^C m R: MSDOS Files^C m T: MSDOS Files^C N: RPM Packages^C n d: Renaming Files^C n u: Renaming Files^C o: Compressing Files^C O: Inode^C p: Encrypting Files^C P: Encrypting Files^C q: RPM Packages^C R: Renaming Files^C R (for directories): Renaming Dirs^C r G: Inode^C r M: Inode^C r O: Inode^C s: Selecting^C S: Linking Files^C t: File Types^C T (for directories): Moving Dirs^C u: Selecting^C U: Dirs Usage^C V: Archive Files^C W: Wiping Files^C X: Archive Files^C x: Archive Files^C Z: Compressing Files^C z: Compressing Files^C ~: Packing Files^E: Moving Point^F, RIGHT: Moving Point^H, BKSPC: Erasing^K: Erasing^L: Refreshing^O, ESC o: Modes^R, ^Xr: Isearch^S, ^Xs: Isearch^SPC: Setting Mark^U: Erasing^W: Erasing^X 0: Modes^X 1: Modes^X 2: Modes^X 4 a: Editing Files^X ^F: Editing Files^X ^I: Inserting Text^X ^L: Resetting^X ^P: Dirs History^X ^R: Dirs History^X ^X: Setting Mark^X b m: Compiling^X d, ^X ^D: Changing Dirs^X e: Editing Files^X E: Environment^X g: Grep^X G: Grep^X h: Documentation^X H: Environment^X I: Spell Checking Files^X k: Processes^X N: Dirs History^X P: Moving^X p: Locking^X q: Documentation^X S: Sync^X T: Sysinfo^X v: Viewing Files^X w: Searching Files^X W: Searching Files^X z: Shell^Y: YankingDEL, ^D: ErasingDOWN, ^N: MovingEND, ESC >: MovingESC %: Searching FilesESC &: Searching FilesESC +: SelectingESC -: SelectingESC .: Hot KeysESC /: Hot KeysESC 5 (for directories): Copying DirsESC 6 (for directories): Moving DirsESC 8 (for directories): Deleting DirsESC \: ErasingESC a c: Changing DirsESC a o: Changing DirsESC b: Moving PointESC BKSPC: ErasingESC c: Case ChangesESC d: ErasingESC e a: ModesESC e d: ModesESC e f: ModesESC e m: ModesESC e o: ModesESC e s: ModesESC ESC 1: Hot KeysESC ESC 2: Hot KeysESC ESC RET: Inserting TextESC f: Moving PointESC g: MovingESC h: Hot KeysESC i: Hot KeysESC j: MovingESC k: ErasingESC l: Case ChangesESC m a: MountingESC m b: MountingESC m c: MountingESC m f: MountingESC m j: MountingESC m t: MountingESC m z: MountingESC n: HistoryESC p: HistoryESC P a, ESC P l, ESC P u: ProcessesESC P b, ESC P c, ESC P e: ProcessesESC P T: ProcessesESC P x, ESC P y: ProcessesESC r a: MountingESC r b: MountingESC r c: MountingESC r f: MountingESC r j: MountingESC r t: MountingESC r z: MountingESC RET: Inserting TextESC s d: SortingESC s e: SortingESC S f: SysinfoESC s g i: SortingESC s g n: SortingESC S m: SysinfoESC s m: SortingESC s n: SortingESC s o i: SortingESC s o n: SortingESC S q: SysinfoESC S s: SysinfoESC s s: SortingESC S u: SysinfoESC s u: SortingESC S v: SysinfoESC S w: SysinfoESC SPC: ErasingESC u: Case ChangesESC w: ErasingESC x r m: MailF1, ESC 1, ^X i: DocumentationF10, ESC 0, ^X ^C, ^X c: ExitF2, ESC 2, ^X a: ActionsF3, ESC 3: Viewing FilesF4, ESC 4: Editing FilesF5 (for directories): Copying DirsF5, ESC 5, ^C C: Copying FilesF6 (for directories): Moving DirsF6, ESC 6, ^C T: Moving FilesF7, ESC 7, ^X M: Creating DirsF8 (for directories): Deleting DirsF8, ESC 8, ^C D: Deleting FilesF9, ESC 9, ^X m: CompilingHOME, ESC <: MovingINS, ^T, ^X \, ^\: SelectingPGDOWN, ^V: MovingPGUP, ESC v: MovingTAB, ^I, ^X o: MovingUP, ^P: Movingadapt-current-directory: Changing DirsAdapt-other-directory: Changing DirsASCII-MAIL: MailB-ASCII-MAIL: MailB-BINARY-MAIL: MailB-BZIP2-COMPRESS: Compressing FilesB-BZIP2-UNCOMPRESS: Compressing FilesB-CHGRP: InodeB-CHMOD: InodeB-CHOWN: InodeB-COMPRESS: Compressing FilesB-COPY: Copying FilesB-COPY (for directories): Copying DirsB-DELETE: Deleting FilesB-DELETE (for directories): Deleting DirsB-DIRR-DIFF: Comparing DirsB-GENERIC-UNPACK: Archive FilesB-GENERIC-UNPACK-INTO: Archive FilesB-LINK: Linking FilesB-MAKE: CompilingB-MIME-MAIL: MailB-MIME-PACK: Encoding FilesB-MIME-UNPACK: Encoding FilesB-MOVE: Moving FilesB-MOVE (for directories): Moving DirsB-MTOOLS-DELETE: MSDOS FilesB-MTOOLS-FORMAT: MSDOS FilesB-MTOOLS-GET: MSDOS FilesB-MTOOLS-MKDIR: MSDOS FilesB-MTOOLS-PUT: MSDOS FilesB-MTOOLS-RENAME: MSDOS FilesB-MTOOLS-RMDIR: MSDOS FilesB-R-CHGRP: InodeB-R-CHMOD: InodeB-R-CHOWN: InodeB-RENAME: Renaming FilesB-RENAME (for directories): Renaming DirsB-RPM-INSTALL: RPM PackagesB-RPM-UNINSTALL: RPM PackagesB-RPM-UPGRADE: RPM PackagesB-SPLIT: Splitting FilesB-SYMLINK: Linking FilesB-TAR: Archive FilesB-TAR-BZIP2: Archive FilesB-TAR-COMPRESS: Archive FilesB-UNCOMPRESS: Compressing FilesB-UUDECODE: Encoding FilesB-UUENCODE: Encoding Filesbackward-char: Moving Pointbackward-delete-char: Erasingbackward-kill-word: Erasingbackward-word: Moving Pointbeginning-of-line: Moving Pointbeginning-of-panel: MovingBF-UNCOMPRESS: Compressing Filesbin-packing: Packing FilesBINARY-MAIL: MailBZIP2-COMPRESS: Compressing FilesBZIP2-UNCOMPRESS: Compressing Filescapitalize-word: Case Changeschange-directory: Changing DirsCHANGE-LOG: Editing FilesCHGRP: InodeCHMOD: InodeCHOWN: Inodecompare: Comparing FilesCOMPRESS: Compressing Filescopy: Copying Filescopy (for directories): Copying DirsDATE: SysinfoDECRYPT: Encrypting Filesdelete: Deleting Filesdelete (for directories): Deleting Dirsdelete-char: Erasingdelete-horizontal-space: ErasingDIFF: Comparing FilesDIRECTORY-USAGE: Dirs UsageDIRR-DIFF: Comparing DirsDISK-FREE-SPACE: Sysinfodowncase-word: Case ChangesEDIT: Editing FilesENCRYPT: Encrypting Filesend-of-line: Moving Pointend-of-panel: Movingenlarge-other-panel: Modesenlarge-panel: Modesentry-to-input-line: Inserting TextENV: Environmentexchange-point-and-mark: Setting Markexit: ExitF-UNCOMPRESS: Compressing FilesFAST-DIFF: Comparing DirsFILE-ACTION: ActionsFILE-CREATE: Editing FilesFILE-TYPE: File TypesFIND: Searching FilesFINGER: SysinfoFIRST-FLOPPY-DIR: Hot Keysforward-char: Moving Pointforward-word: Moving PointGENERIC-UNPACK: Archive FilesGENERIC-UNPACK-INTO: Archive FilesGITPS, PS: ProcessesGREP: GrepHOME-DIR: Hot Keyshorizontal-scroll-left: Movinghorizontal-scroll-right: MovingHTML: DocumentationINCLUDE-DIR: Hot KeysINFO: Documentationisearch-backward: Isearchisearch-forward: IsearchISPELL: Spell Checking Filesjust-one-space: ErasingKILL: Processeskill-line: Erasingkill-region: Erasingkill-ring-save: Erasingkill-to-beginning-of-line: Erasingkill-to-end-of-line: Erasingkill-word: ErasingLAST-BACKUP-DIFF: Comparing FilesLINK: Linking FilesLOCATE: Searching Fileslock: LockingMAKE: Compilingmake-directory: Creating DirsMAN: DocumentationMIME-MAIL: MailMOUNT-A: MountingMOUNT-B: MountingMOUNT-CDROM: MountingMOUNT-FLOPPY: MountingMOUNT-JAZ: MountingMOUNT-THESE: MountingMOUNT-ZIP: MountingMOUNTED-FILE-SYSTEMS: Sysinfomove: Moving Filesmove (for directories): Moving DirsMPACK: Encoding FilesMTOOLS-CHDIR: MSDOS FilesMTOOLS-DELETE: MSDOS FilesMTOOLS-DIR: MSDOS FilesMTOOLS-FORMAT: MSDOS FilesMTOOLS-GET: MSDOS FilesMTOOLS-MKDIR: MSDOS FilesMTOOLS-PUT: MSDOS FilesMTOOLS-RENAME: MSDOS FilesMTOOLS-RMDIR: MSDOS FilesMTOOLS-TYPE: MSDOS FilesMULTIPLE-EDIT: Editing FilesMULTIPLE-VIEW: Viewing FilesMUNPACK: Encoding Filesname-downcase: Renaming Filesname-upcase: Renaming Filesnext-directory: Dirs Historynext-history-element: Historynext-line: Movingother-panel: Movingother-path-to-input-line: Inserting Textpanel-enable-all: Modespanel-enable-date-time: Modespanel-enable-full-name: Modespanel-enable-mode: Modespanel-enable-next-mode: Modespanel-enable-owner-group: Modespanel-enable-size: Modespanel-sort-by-date: Sortingpanel-sort-by-extension: Sortingpanel-sort-by-group-id: Sortingpanel-sort-by-group-name: Sortingpanel-sort-by-mode: Sortingpanel-sort-by-name: Sortingpanel-sort-by-owner-id: Sortingpanel-sort-by-owner-name: Sortingpanel-sort-by-size: Sortingpanel-sort-next-method: Sortingprevious-directory: Dirs Historyprevious-history-element: Historyprevious-line: MovingPRINT-JOB: Printing FilesPRINT-JOB-LIST: Printing FilesPSTREE: Processesquick-compare-panels: Comparing DirsQUOTA: SysinfoR-CHGRP: InodeR-CHMOD: InodeR-CHOWN: InodeREAD-MAIL: MailRECURSIVE-GREP: Greprefresh: RefreshingRENAME: Renaming FilesRENAME (for directories): Renaming Dirsreset-directory-history: Dirs HistoryROOT-DIR: Hot KeysRPM-INSTALL: RPM PackagesRPM-QUERY: RPM PackagesRPM-UNINSTALL: RPM PackagesRPM-UPGRADE: RPM Packagesscroll-down: Movingscroll-up: MovingSECOND-FLOPPY-DIR: Hot Keysselect-entry: Selectingselect-extension: Selectingselect-files-matching-pattern: Selectingselected-entries-to-input-line: Inserting Textset-mark: Setting Markset-scroll-step: MovingSPLIT: Splitting FilesSUB-SHELL: Shellswitch-panels: MovingSYMLINK: Linking FilesSYNC: SyncTAR: Archive FilesTAR-BZIP2: Archive FilesTAR-COMPRESS: Archive Filesthoroughly-compare-panels: Comparing Dirstty-mode: ModesTTY-RESET: Resettingtwo-panel-mode: ModesUMOUNT-A: MountingUMOUNT-B: MountingUMOUNT-FLOPPY: MountingUMOUNT-JAZ: MountingUMOUNT-THESE: MountingUMOUNT-ZIP: MountingUNCOMPRESS: Compressing Filesunselect-extension: Selectingunselect-files-matching-pattern: Selectingup-one-dir: Hot Keysupcase-word: Case ChangesUSERS: SysinfoUUDECODE: Encoding FilesUUENCODE: Encoding FilesVIEW: Viewing FilesVIRTUAL-MEMORY-STATUS: SysinfoWHEREIS: Searching FilesWHICH: Searching FilesWHO: SysinfoWIPE: Wiping FilesXHOST: Environmentyank: YankingAnsiColors: SetupCommandLineModeHelp: GITFM-SetupConfirmOnExit: GITFM-SetupEDITOR: Environment VariablesGIT_BROWSER: Environment VariablesGIT_EDITOR: Environment VariablesGIT_RMAIL: Environment VariablesGIT_SHELL: Environment VariablesGIT_VMSTAT: Environment VariablesHistoryFile: GITFM-SetupInfoDisplay: GITFM-SetupLeadingDotMatch: GITFM-SetupNormalModeHelp: GITFM-SetupSHELL: Environment VariablesStartupFileDisplayMode: GITFM-SetupStartupFileSortMethod: GITFM-SetupStartupScrollStep: SetupTERM: Configuration FilesTypeSensitivity: GITFM-SetupUseLastScreenChar: Setup