1 .\"Generated by db2man.xsl. Don't modify this, modify the source.
10 .de Sp \" Vertical space (when we can't use .PP)
16 .ie \\n(.$>=3 .ne \\$3
22 tig \- text-mode interface for git
27 tig [options] [\-\-] [git log options]
28 tig [options] log [git log options]
29 tig [options] diff [git diff options]
30 tig [options] show [git show options]
31 tig [options] < [git command output]
37 Browse changes in a git repository\&. Additionally, tig(1) can also act as a pager for output of various git commands\&.
40 When browsing repositories, tig(1) uses the underlying git commands to present the user with various views, such as summarized commit log and showing the commit with the log message, diffstat, and the diff\&.
43 Using tig(1) as a pager, it will display input from stdin and try to colorize it\&.
49 Start up in log view using the internal log command\&.
53 Start up in diff view using the internal diff command\&.
56 \-n[INTERVAL], \-\-line\-number[=INTERVAL]
57 Prefix line numbers in log and diff view\&. Optionally, with interval different than each line\&.
60 \-t[NSPACES], \-\-tab\-size[=NSPACES]
61 Set the number of spaces tabs should be expanded to\&.
65 Show version and exit\&.
69 End of tig(1) options\&. Useful when specifying command options for the main view\&. Example:
72 $ tig \-\- \-\-since=1\&.month
77 Open log view using the given git log options\&.
80 diff [git diff options]
81 Open diff view using the given git diff options\&.
84 show [git show options]
85 Open diff view using the given git show options\&.
89 tig(1) will stop the option parsing when the first command line parameter not starting with "\-" is encountered\&. All options including this one will be passed to git log when loading the main view\&. This makes it possible to say:
92 $ tig tag\-1\&.0\&.\&.HEAD
98 If stdin is a pipe, any log or diff options will be ignored and the pager view will be opened loading data from stdin\&. The pager mode can be used for colorizing output from various git commands\&.
101 Example on how to colorize the output of git\-show(1):
107 .SS "Git command options"
110 All git command options specified on the command line will be passed to the given command and all will be shell quoted before they are passed to the shell\&.
116 If you specify options for the main view, you should not use the \-\-pretty option as this option will be set automatically to the format expected by the main view\&.
121 Example on how to open the log view and show both author and committer information:
124 $ tig log \-\-pretty=fuller
128 See the "Specifying revisions" section below for an introduction to revision options supported by the git commands\&. For details on specific git command options, refer to the man page of the command in question\&.
130 .SH "ENVIRONMENT VARIABLES"
133 Several options related to the interface with git can be configured via environment options\&.
135 .SS "Repository references"
138 Commits that are referenced by tags and branch heads will be marked by the reference name surrounded by \fI[\fR and \fI]\fR:
141 2006\-03\-26 19:42 Petr Baudis | [cogito\-0\&.17\&.1] Cogito 0\&.17\&.1
145 If you want to filter out certain directories under \&.git/refs/, say tmp you can do it by setting the following variable:
148 $ TIG_LS_REMOTE="git ls\-remote \&. | sed /\\/tmp\\//d" tig
152 Or set the variable permanently in your environment\&.
156 Set command for retrieving all repository references\&. The command should output data in the same format as git\-ls\-remote(1)\&.
161 It is possible to alter which commands are used for the different views\&. If for example you prefer commits in the main view to be sorted by date and only show 500 commits, use:
164 $ TIG_MAIN_CMD="git log \-\-date\-order \-n500 \-\-pretty=raw %s" tig
168 Or set the variable permanently in your environment\&.
171 Notice, how %s is used to specify the commit reference\&. There can be a maximum of 5 %s ref specifications\&.
175 The command used for the diff view\&. By default, git show is used as a backend\&.
179 The command used for the log view\&. If you prefer to have both author and committer shown in the log view be sure to pass \-\-pretty=fuller to git log\&.
183 The command used for the main view\&. Note, you must always specify the option: \-\-pretty=raw since the main view parser expects to read that format\&.
188 tig(1) presents various \fIviews\fR of a repository\&. Each view is based on output from an external command, most often \fIgit log\fR, \fIgit diff\fR, or \fIgit show\fR\&.
192 Is the default view, and it shows a one line summary of each commit in the chosen list of revisions\&. The summary includes commit date, author, and the first line of the log message\&. Additionally, any repository references, such as tags, will be shown\&.
196 Presents a more rich view of the revision log showing the whole log message and the diffstat\&.
200 Shows either the diff of the current working tree, that is, what has changed since the last commit, or the commit diff complete with log message, diffstat and diff\&.
204 Is used for displaying both input from stdin and output from git commands entered in the internal prompt\&.
208 Displays the information from the tig(1) man page\&. For the help view to work you need to have the tig(1) man page installed\&.
213 Below the default key bindings are shown\&.
219 Switch to main view\&.
223 Switch to diff view\&.
227 Switch to log view\&.
231 Switch to pager view\&.
239 If on a commit line show the commit diff\&. Additionally, if in main or log view this will split the view\&. To open the commit diff in full size view either use \fId\fR or press Return twice\&.
243 Switch to next view\&.
245 .SS "Cursor navigation"
249 Move cursor one line up\&.
253 Move cursor one line down\&.
257 Move cursor one line up and enter\&. When used in the main view this will always show the diff of the current commit in the split diff view\&.
261 Move cursor one line down and enter\&.
265 Move cursor one page up\&.
269 Move cursor one page down\&.
273 Jump to first line\&.
283 Scroll view one line up\&.
287 Scroll view one line down\&.
291 Scroll view one page up\&.
295 Scroll view one page down\&.
309 Stop all background loading\&. This can be useful if you use tig(1) in a repository with a long history without limiting the revision log\&.
317 Toggle line numbers on/off\&.
321 Open prompt\&. This allows you to specify what git command to run\&. Example:
327 .SH "REVISION SPECIFICATION"
330 This section describes various ways to specify what revisions to display or otherwise limit the view to\&. tig(1) does not itself parse the described revision options so refer to the relevant git man pages for futher information\&. Relevant man pages besides git\-log(1) are git\-diff(1) and git\-rev\-list(1)\&.
333 You can tune the interaction with git by making use of the options explained in this section\&. For example, by configuring the environment variables described in the "View commands" section\&.
335 .SS "Limit by path name"
338 If you are interested only in those revisions that made changes to a specific file (or even several files) list the files like this:
345 To avoid ambiguity with repository references such as tag name, be sure to separate file names from other git options using "\-\-"\&. So if you have a file named \fImaster\fR it will clash with the reference named \fImaster\fR, and thus you will have to use:
348 $ tig log \-\- master
355 For the main view, avoiding ambiguity will in some cases require you to specify two "\-\-" options\&. The first will make tig(1) stop option processing and the latter will be passed to git log\&.
359 .SS "Limit by date or number"
362 To speed up interaction with git, you can limit the amount of commits to show both for the log and main view\&. Either limit by date using e\&.g\&. \-\-since=1\&.month or limit by the number of commits using \-n400\&.
365 If you are only interested in changed that happened between two dates you can use:
368 $ tig \-\- \-\-after=May\&.5th \-\-before=2006\-05\-16\&.15:44
375 The dot ("\&.") is used as a separator instead of a space to avoid having to quote the option value\&. If you prefer use \-\-after="May 5th" instead of \-\-after="May 5th"\&.
379 .SS "Limiting by commit ranges"
382 Alternatively, commits can be limited to a specific range, such as "all commits between \fItag\-1\&.0\fR and \fItag\-2\&.0\fR"\&. For example:
385 $ tig log tag\-1\&.0\&.\&.tag\-2\&.0
389 This way of commit limiting makes it trivial to only browse the commits which haven't been pushed to a remote branch\&. Assuming \fIorigin\fR is your upstream remote branch, using:
392 $ tig log origin\&.\&.HEAD
396 will list what will be pushed to the remote branch\&. Optionally, the ending \fIHEAD\fR can be left out since it is implied\&.
398 .SS "Limiting by reachability"
401 Git interprets the range specifier "tag\-1\&.0\&.\&.tag\-2\&.0" as "all commits reachable from \fItag\-2\&.0\fR but not from \fItag\-1\&.0\fR"\&. Where reachability refers to what commits are ancestors (or part of the history) of the branch or tagged revision in question\&.
404 If you prefer to specify which commit to preview in this way use the following:
407 $ tig log tag\-2\&.0 ^tag\-1\&.0
411 You can think of \fI^\fR as a negation operator\&. Using this alternate syntax, it is possible to further prune commits by specifying multiple branch cut offs\&.
413 .SS "Combining revisions specification"
416 Revisions options can to some degree be combined, which makes it possible to say "show at most 20 commits from within the last month that changed files under the Documentation/ directory\&."
419 $ tig \-\- \-\-since=1\&.month \-n20 \-\- Documentation/
422 .SS "Examining all repository references"
425 In some cases, it can be useful to query changes across all references in a repository\&. An example is to ask "did any line of development in this repository change a particular file within the last week"\&. This can be accomplished using:
428 $ tig \-\- \-\-all \-\-since=1\&.week \-\- Makefile
434 Known bugs and problems:
438 If the screen width is very small the main view can draw outside the current view causing bad wrapping\&. Same goes for title and status windows\&.
444 Features that should be explored\&.
457 Copyright (c) Jonas Fonseca <fonseca@diku\&.dk>, 2006
460 This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version\&.
465 git(7): \fIhttp://www.kernel.org/pub/software/scm/git/docs/\fR,
466 cogito(7): \fIhttp://www.kernel.org/pub/software/scm/cogito/docs/\fR
467 gitk(1): git repository browser written using tcl/tk,
468 qgit(1): git repository browser written using c++/Qt,
469 gitview(1): git repository browser written using python/gtk\&.