Merge with master
[tig] / tig.1
CommitLineData
2b9c2ad0
JF
1.\"Generated by db2man.xsl. Don't modify this, modify the source.
2.de Sh \" Subsection
3.br
4.if t .Sp
5.ne 5
6.PP
7\fB\\$1\fR
8.PP
9..
10.de Sp \" Vertical space (when we can't use .PP)
11.if t .sp .5v
12.if n .sp
13..
14.de Ip \" List item
15.br
16.ie \\n(.$>=3 .ne \\$3
17.el .ne 3
18.IP "\\$1" \\$2
19..
20.TH "TIG" 1 "" "" ""
21.SH NAME
22tig \- text-mode interface for git
23.SH "SYNOPSIS"
24
25.nf
26tig [options]
27tig [options] [\-\-] [git log options]
28tig [options] log [git log options]
29tig [options] diff [git diff options]
30tig [options] show [git show options]
31tig [options] < [git command output]
32.fi
33
34.SH "DESCRIPTION"
35
36
37Browse changes in a git repository\&. Additionally, tig(1) can also act as a pager for output of various git commands\&.
38
39
40When 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\&.
41
42
43Using tig(1) as a pager, it will display input from stdin and try to colorize it\&.
44
45.SH "OPTIONS"
46
47.TP
48\-l
49Start up in log view using the internal log command\&.
50
51.TP
52\-d
53Start up in diff view using the internal diff command\&.
54
55.TP
56\-n[INTERVAL], \-\-line\-number[=INTERVAL]
57Prefix line numbers in log and diff view\&. Optionally, with interval different than each line\&.
58
59.TP
60\-t[NSPACES], \-\-tab\-size[=NSPACES]
61Set the number of spaces tabs should be expanded to\&.
62
63.TP
64\-v, \-\-version
65Show version and exit\&.
66
67.TP
ffe3a8da
JF
68\-h, \-\-help
69Show help message and exit\&.
70
71.TP
2b9c2ad0
JF
72\-\-
73End of tig(1) options\&. Useful when specifying command options for the main view\&. Example:
74
75.nf
76$ tig \-\- \-\-since=1\&.month
77.fi
78
79.TP
80log [git log options]
81Open log view using the given git log options\&.
82
83.TP
84diff [git diff options]
85Open diff view using the given git diff options\&.
86
87.TP
88show [git show options]
89Open diff view using the given git show options\&.
90
91.TP
92[git log options]
93tig(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:
94
95.nf
96$ tig tag\-1\&.0\&.\&.HEAD
97.fi
98
99.SS "Pager mode"
100
101
102If 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\&.
103
104
105Example on how to colorize the output of git\-show(1):
106
107.nf
108$ git show | tig
109.fi
110
111.SS "Git command options"
112
113
114All 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\&.
115
116.RS
117.Sh "Note"
118
119
120If 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
122.RE
123
124
125Example on how to open the log view and show both author and committer information:
126
127.nf
128$ tig log \-\-pretty=fuller
129.fi
130
131
132See 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\&.
133
134.SH "ENVIRONMENT VARIABLES"
135
136
137Several options related to the interface with git can be configured via environment options\&.
138
139.SS "Repository references"
140
141
142Commits that are referenced by tags and branch heads will be marked by the reference name surrounded by \fI[\fR and \fI]\fR:
143
144.nf
1452006\-03\-26 19:42 Petr Baudis | [cogito\-0\&.17\&.1] Cogito 0\&.17\&.1
146.fi
147
148
149If you want to filter out certain directories under \&.git/refs/, say tmp you can do it by setting the following variable:
150
151.nf
152$ TIG_LS_REMOTE="git ls\-remote \&. | sed /\\/tmp\\//d" tig
153.fi
154
155
156Or set the variable permanently in your environment\&.
157
158.TP
159TIG_LS_REMOTE
160Set command for retrieving all repository references\&. The command should output data in the same format as git\-ls\-remote(1)\&.
161
162.SS "View commands"
163
164
165It 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:
166
167.nf
168$ TIG_MAIN_CMD="git log \-\-date\-order \-n500 \-\-pretty=raw %s" tig
169.fi
170
171
172Or set the variable permanently in your environment\&.
173
174
175Notice, how %s is used to specify the commit reference\&. There can be a maximum of 5 %s ref specifications\&.
176
177.TP
178TIG_DIFF_CMD
179The command used for the diff view\&. By default, git show is used as a backend\&.
180
181.TP
182TIG_LOG_CMD
183The 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\&.
184
185.TP
186TIG_MAIN_CMD
187The 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
189.SH "THE VIEWER"
190
191
ffe3a8da
JF
192The display consists of a status window on the last line of the screen and one or more views\&. The default is to only show one view at the time but it is possible to split both the main and log view to also show the commit diff\&.
193
194
195If you are in the log view and press \fIEnter\fR when the current line is a commit line, such as:
196
197.nf
198commit 4d55caff4cc89335192f3e566004b4ceef572521
199.fi
200
201
202You will split the view so that the log view is displayed in the top window and the diff view in the bottom window\&. You can switch between the two views by pressing \fITab\fR\&. To maximize the log view again, simply press \fIl\fR\&.
203
204.SS "Current head and commit ID"
205
206
207The viewer keeps track of both what head and commit ID you are currently viewing\&. The commit ID will follow the cursor line and change everytime time you highlight a different commit\&. Whenever you reopen the diff view it will be reloaded, if the commit ID changed\&.
208
209
210The head ID is used when opening the main and log view to indicate from what revision to show history\&.
211
212.SS "Views"
213
214
2b9c2ad0
JF
215tig(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\&.
216
217.TP
218The main view
e7a724d9 219Is 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\&.
2b9c2ad0
JF
220
221.TP
222The log view
223Presents a more rich view of the revision log showing the whole log message and the diffstat\&.
224
225.TP
226The diff view
227Shows 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\&.
228
229.TP
230The pager view
231Is used for displaying both input from stdin and output from git commands entered in the internal prompt\&.
232
233.TP
234The help view
235Displays the information from the tig(1) man page\&. For the help view to work you need to have the tig(1) man page installed\&.
236
ffe3a8da
JF
237.SS "Title windows"
238
239
240Each view has a title window which shows the name of the view, current commit ID if available, and where the view is positioned:
241
242.nf
243[main] c622eefaa485995320bc743431bae0d497b1d875 \- commit 1 of 61 (1%)
244.fi
245
246
247By default, the title of the current view is highlighted using bold font\&.
248
2b9c2ad0
JF
249.SH "KEYS"
250
251
252Below the default key bindings are shown\&.
253
254.SS "View switching"
255
256.TP
257m
258Switch to main view\&.
259
260.TP
261d
262Switch to diff view\&.
263
264.TP
265l
266Switch to log view\&.
267
268.TP
269p
270Switch to pager view\&.
271
272.TP
273h
274Show man page\&.
275
ffe3a8da
JF
276.SS "View manipulation"
277
2b9c2ad0 278.TP
ffe3a8da
JF
279q
280Close view, if multiple views are open it will jump back to the previous view in the view stack\&. If it is the last open view it will quit\&. Use \fIQ\fR to quit all views at once\&.
281
282.TP
283Enter
284This key is "context sensitive" depending on what view you are currently in\&. When in log view on a commit line or in the main view, split the view and show the commit diff\&. In the diff view pressing Enter will simply scroll the view one line down\&.
2b9c2ad0
JF
285
286.TP
287Tab
288Switch to next view\&.
289
2b9c2ad0
JF
290.TP
291Up
ffe3a8da 292This key is "context sensitive" and will move the cursor one line up\&. However, uf you opened a diff view from the main view (split\- or full\-screen) it will change the cursor to point to the previous commit in the main view and update the diff view to display it\&.
2b9c2ad0
JF
293
294.TP
295Down
ffe3a8da 296Similar to \fIUp\fR but will move down\&.
2b9c2ad0 297
ffe3a8da 298.SS "Cursor navigation"
2b9c2ad0
JF
299
300.TP
301j
ffe3a8da 302Move cursor one line up\&.
2b9c2ad0
JF
303
304.TP
ffe3a8da
JF
305k
306Move cursor one line down\&.
307
308.TP
309PgUp, b, \-
2b9c2ad0
JF
310Move cursor one page up\&.
311
312.TP
ffe3a8da 313PgDown, Space
2b9c2ad0
JF
314Move cursor one page down\&.
315
316.TP
317Home
318Jump to first line\&.
319
320.TP
321End
322Jump to last line\&.
323
324.SS "Scrolling"
325
326.TP
327Insert
328Scroll view one line up\&.
329
330.TP
331Delete
332Scroll view one line down\&.
333
334.TP
335w
336Scroll view one page up\&.
337
338.TP
339s
340Scroll view one page down\&.
341
342.SS "Misc"
343
344.TP
ffe3a8da
JF
345Q
346Quit\&.
2b9c2ad0
JF
347
348.TP
349r
350Redraw screen\&.
351
352.TP
353z
354Stop all background loading\&. This can be useful if you use tig(1) in a repository with a long history without limiting the revision log\&.
355
356.TP
357v
358Show version\&.
359
360.TP
361n
362Toggle line numbers on/off\&.
363
364.TP
365\fI:\fR
366Open prompt\&. This allows you to specify what git command to run\&. Example:
367
368.nf
369:log \-p
370.fi
371
395d626e 372.SH "REVISION SPECIFICATION"
2b9c2ad0
JF
373
374
395d626e 375This 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)\&.
2b9c2ad0 376
395d626e
JF
377
378You 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\&.
379
380.SS "Limit by path name"
2b9c2ad0
JF
381
382
383If you are interested only in those revisions that made changes to a specific file (or even several files) list the files like this:
384
385.nf
ffe3a8da 386$ tig log Makefile README
2b9c2ad0
JF
387.fi
388
389
390To 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:
391
392.nf
56235576 393$ tig log \-\- master
2b9c2ad0
JF
394.fi
395
396.RS
397.Sh "Note"
398
399
400For 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\&.
401
402.RE
403
404.SS "Limit by date or number"
405
406
407To 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\&.
408
395d626e
JF
409
410If you are only interested in changed that happened between two dates you can use:
411
412.nf
ffe3a8da 413$ tig \-\- \-\-after="May 5th" \-\-before="2006\-05\-16 15:44"
395d626e
JF
414.fi
415
2b9c2ad0
JF
416.RS
417.Sh "Note"
418
419
ffe3a8da 420If you want to avoid having to quote dates containing spaces you can use "\&." instead, e\&.g\&. \-\-after=May\&.5th\&.
2b9c2ad0
JF
421
422.RE
423
395d626e 424.SS "Limiting by commit ranges"
2b9c2ad0
JF
425
426
427Alternatively, commits can be limited to a specific range, such as "all commits between \fItag\-1\&.0\fR and \fItag\-2\&.0\fR"\&. For example:
428
429.nf
430$ tig log tag\-1\&.0\&.\&.tag\-2\&.0
431.fi
432
433
434This 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:
435
436.nf
437$ tig log origin\&.\&.HEAD
438.fi
439
440
441will list what will be pushed to the remote branch\&. Optionally, the ending \fIHEAD\fR can be left out since it is implied\&.
442
443.SS "Limiting by reachability"
444
445
395d626e
JF
446Git 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\&.
447
448
449If you prefer to specify which commit to preview in this way use the following:
2b9c2ad0
JF
450
451.nf
452$ tig log tag\-2\&.0 ^tag\-1\&.0
453.fi
454
455
456You 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\&.
457
395d626e
JF
458.SS "Combining revisions specification"
459
460
461Revisions 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\&."
462
463.nf
464$ tig \-\- \-\-since=1\&.month \-n20 \-\- Documentation/
465.fi
466
467.SS "Examining all repository references"
468
469
470In 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:
471
472.nf
473$ tig \-\- \-\-all \-\-since=1\&.week \-\- Makefile
474.fi
475
2b9c2ad0
JF
476.SH "BUGS"
477
478
479Known bugs and problems:
480
481.TP 3
482\(bu
ffe3a8da
JF
483In it's current state tig is pretty much UTF\-8 only\&.
484.TP
485\(bu
2b9c2ad0
JF
486If 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\&.
487.LP
488
489.SH "TODO"
490
491
492Features that should be explored\&.
493
494.TP 3
495\(bu
496Searching\&.
497.TP
498\(bu
499Locale support\&.
500.LP
501
502.SH "COPYRIGHT"
503
504
505Copyright (c) Jonas Fonseca <fonseca@diku\&.dk>, 2006
506
507
508This 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\&.
509
510.SH "SEE ALSO"
511
512.nf
513git(7): \fIhttp://www.kernel.org/pub/software/scm/git/docs/\fR,
514cogito(7): \fIhttp://www.kernel.org/pub/software/scm/cogito/docs/\fR
515gitk(1): git repository browser written using tcl/tk,
e7a724d9 516qgit(1): git repository browser written using c++/Qt,
2b9c2ad0
JF
517gitview(1): git repository browser written using python/gtk\&.
518.fi
519