Move tig.spec.in to the contrib area
[tig] / manual.txt
... / ...
CommitLineData
1The tig Manual
2==============
3Jonas Fonseca <fonseca@diku.dk>
4
5This is the manual for tig, the ncurses-based text-mode interface for git.
6Tig allows you to browse changes in a git repository and can additionally act
7as a pager for output of various git commands. When used as a pager, it will
8display input from stdin and colorize it.
9
10When browsing repositories, tig uses the underlying git commands to present
11the user with various views, such as summarized commit log and showing the
12commit with the log message, diffstat, and the diff.
13
14ifndef::backend-docbook[]
15*Table of Contents*
16
17include::manual.toc[]
18endif::backend-docbook[]
19
20[[calling-conventions]]
21Calling Conventions
22-------------------
23
24[[pager-mode]]
25Pager Mode
26~~~~~~~~~~
27
28If stdin is a pipe, any log or diff options will be ignored and the pager view
29will be opened loading data from stdin. The pager mode can be used for
30colorizing output from various git commands.
31
32Example on how to colorize the output of git-show(1):
33
34-----------------------------------------------------------------------------
35$ git show | tig
36-----------------------------------------------------------------------------
37
38[[cmd-options]]
39Git Command Options
40~~~~~~~~~~~~~~~~~~~
41
42All git command options specified on the command line will be passed to the
43given command and all will be shell quoted before they are passed to the
44shell.
45
46NOTE: If you specify options for the main view, you should not use the
47`--pretty` option as this option will be set automatically to the format
48expected by the main view.
49
50Example on how to open the log view and show both author and committer
51information:
52
53-----------------------------------------------------------------------------
54$ tig log --pretty=fuller
55-----------------------------------------------------------------------------
56
57See the <<refspec, "Specifying revisions">> section below for an introduction
58to revision options supported by the git commands. For details on specific git
59command options, refer to the man page of the command in question.
60
61[[env-variables]]
62Environment Variables
63---------------------
64
65Several options related to the interface with git can be configured via
66environment options.
67
68[[repo-refs]]
69Repository References
70~~~~~~~~~~~~~~~~~~~~~
71
72Commits that are referenced by tags and branch heads will be marked by the
73reference name surrounded by '[' and ']':
74
75-----------------------------------------------------------------------------
762006-03-26 19:42 Petr Baudis | [cogito-0.17.1] Cogito 0.17.1
77-----------------------------------------------------------------------------
78
79If you want to filter out certain directories under `.git/refs/`, say `tmp`
80you can do it by setting the following variable:
81
82-----------------------------------------------------------------------------
83$ TIG_LS_REMOTE="git ls-remote . | sed /\/tmp\//d" tig
84-----------------------------------------------------------------------------
85
86Or set the variable permanently in your environment.
87
88TIG_LS_REMOTE::
89 Set command for retrieving all repository references. The command
90 should output data in the same format as git-ls-remote(1).
91
92[[history-commands]]
93History Commands
94~~~~~~~~~~~~~~~~
95
96It is possible to alter which commands are used for the different views. If
97for example you prefer commits in the main view to be sorted by date and only
98show 500 commits, use:
99
100-----------------------------------------------------------------------------
101$ TIG_MAIN_CMD="git log --date-order -n500 --pretty=raw %s" tig
102-----------------------------------------------------------------------------
103
104Or set the variable permanently in your environment.
105
106Notice, how `%s` is used to specify the commit reference. There can be a
107maximum of 5 `%s` ref specifications.
108
109TIG_DIFF_CMD::
110 The command used for the diff view. By default, git show is used
111 as a backend.
112
113TIG_LOG_CMD::
114 The command used for the log view. If you prefer to have both
115 author and committer shown in the log view be sure to pass
116 `--pretty=fuller` to git log.
117
118TIG_MAIN_CMD::
119 The command used for the main view. Note, you must always specify
120 the option: `--pretty=raw` since the main view parser expects to
121 read that format.
122
123[[tree-commands]]
124Tree Commands
125~~~~~~~~~~~~~
126
127TIG_TREE_CMD::
128 The command used for the tree view. Takes two arguments, the first
129 is the revision ID and the second is the path of the directory tree,
130 empty for the root directory. Defaults to "git ls-tree %s %s".
131
132TIG_BLOB_CMD::
133 The command used for the blob view. Takes one argument which is
134 the blob ID. Defaults to "git cat-file blob %s".
135
136[[viewer]]
137The Viewer
138----------
139
140The display consists of a status window on the last line of the screen and one
141or more views. The default is to only show one view at the time but it is
142possible to split both the main and log view to also show the commit diff.
143
144If you are in the log view and press 'Enter' when the current line is a commit
145line, such as:
146
147-----------------------------------------------------------------------------
148commit 4d55caff4cc89335192f3e566004b4ceef572521
149-----------------------------------------------------------------------------
150
151You will split the view so that the log view is displayed in the top window
152and the diff view in the bottom window. You can switch between the two views
153by pressing 'Tab'. To maximize the log view again, simply press 'l'.
154
155[[commit-id]]
156Current Head and Commit ID
157~~~~~~~~~~~~~~~~~~~~~~~~~~
158
159The viewer keeps track of both what head and commit ID you are currently
160viewing. The commit ID will follow the cursor line and change every time
161you highlight a different commit. Whenever you reopen the diff view it will be
162reloaded, if the commit ID changed.
163
164The head ID is used when opening the main and log view to indicate from what
165revision to show history.
166
167[[views]]
168Views
169~~~~~
170
171Various 'views' of a repository is presented. Each view is based on output
172from an external command, most often 'git log', 'git diff', or 'git show'.
173
174The main view::
175 Is the default view, and it shows a one line summary of each commit
176 in the chosen list of revisions. The summary includes commit date,
177 author, and the first line of the log message. Additionally, any
178 repository references, such as tags, will be shown.
179
180The log view::
181 Presents a more rich view of the revision log showing the whole log
182 message and the diffstat.
183
184The diff view::
185 Shows either the diff of the current working tree, that is, what
186 has changed since the last commit, or the commit diff complete
187 with log message, diffstat and diff.
188
189The tree view::
190 Lists directory trees associated with the current revision allowing
191 subdirectories to be descended or ascended and file blobs to be
192 viewed.
193
194The blob view::
195 Displays the file content or "blob" of data associated with a file
196 name.
197
198The status view::
199 Displays status of files in the working tree and allows changes to be
200 staged/unstaged as well as adding of untracked files.
201
202The pager view::
203 Is used for displaying both input from stdin and output from git
204 commands entered in the internal prompt.
205
206The help view::
207 Displays key binding quick reference.
208
209[[title-window]]
210Title Windows
211~~~~~~~~~~~~~
212
213Each view has a title window which shows the name of the view, current commit
214ID if available, and where the view is positioned:
215
216-----------------------------------------------------------------------------
217[main] c622eefaa485995320bc743431bae0d497b1d875 - commit 1 of 61 (1%)
218-----------------------------------------------------------------------------
219
220By default, the title of the current view is highlighted using bold font. For
221long loading views (taking over 3 seconds) the time since loading started will
222be appended:
223
224-----------------------------------------------------------------------------
225[main] 77d9e40fbcea3238015aea403e06f61542df9a31 - commit 1 of 779 (0%) 5s
226-----------------------------------------------------------------------------
227
228[[keys]]
229Default Keybindings
230-------------------
231Below the default key bindings are shown.
232
233[[view-switching]]
234View Switching
235~~~~~~~~~~~~~~
236
237`-------`--------------------------------------------------------------------
238Key Action
239-----------------------------------------------------------------------------
240m Switch to main view.
241d Switch to diff view.
242l Switch to log view.
243p Switch to pager view.
244t Switch to (directory) tree view.
245f Switch to (file) blob view.
246h Switch to help view
247S Switch to status view
248-----------------------------------------------------------------------------
249
250[[view-manipulation]]
251View Manipulation
252~~~~~~~~~~~~~~~~~
253
254`-------`--------------------------------------------------------------------
255Key Action
256-----------------------------------------------------------------------------
257q Close view, if multiple views are open it will jump back to the \
258 previous view in the view stack. If it is the last open view it \
259 will quit. Use 'Q' to quit all views at once.
260Enter This key is "context sensitive" depending on what view you are \
261 currently in. When in log view on a commit line or in the main \
262 view, split the view and show the commit diff. In the diff view \
263 pressing Enter will simply scroll the view one line down.
264Tab Switch to next view.
265Up This key is "context sensitive" and will move the cursor one \
266 line up. However, if you opened a diff view from the main view \
267 (split- or full-screen) it will change the cursor to point to \
268 the previous commit in the main view and update the diff view \
269 to display it.
270Down Similar to 'Up' but will move down.
271-----------------------------------------------------------------------------
272
273[[cursor-nav]]
274Cursor Navigation
275~~~~~~~~~~~~~~~~~
276
277`-------`--------------------------------------------------------------------
278Key Action
279-----------------------------------------------------------------------------
280j Move cursor one line up.
281k Move cursor one line down.
282PgUp,\
283-,a Move cursor one page up.
284PgDown Space Move cursor one page down.
285Home Jump to first line.
286End Jump to last line.
287-----------------------------------------------------------------------------
288
289[[view-scrolling]]
290Scrolling
291~~~~~~~~~
292
293`-------`--------------------------------------------------------------------
294Key Action
295-----------------------------------------------------------------------------
296Insert Scroll view one line up.
297Delete Scroll view one line down.
298w Scroll view one page up.
299s Scroll view one page down.
300-----------------------------------------------------------------------------
301
302[[searching]]
303Searching
304~~~~~~~~~
305
306`-------`--------------------------------------------------------------------
307Key Action
308-----------------------------------------------------------------------------
309/ Search the view. Opens a prompt for entering search regex to use.
310? Search backwards in the view. Also prompts for regex.
311n Find next match for the current search regex.
312N Find previous match for the current search regex.
313-----------------------------------------------------------------------------
314
315[[misc-keys]]
316Misc
317~~~~
318
319`-------`--------------------------------------------------------------------
320Key Action
321-----------------------------------------------------------------------------
322Q Quit.
323r Redraw screen.
324z Stop all background loading. This can be useful if you use \
325 tig in a repository with a long history without limiting \
326 the revision log.
327v Show version.
328'.' Toggle line numbers on/off.
329g Toggle revision graph visualization on/off.
330':' Open prompt. This allows you to specify what git command \
331 to run. Example `:log -p`
332-----------------------------------------------------------------------------
333
334[[refspec]]
335Revision Specification
336----------------------
337
338This section describes various ways to specify what revisions to display or
339otherwise limit the view to. Tig does not itself parse the described
340revision options so refer to the relevant git man pages for further
341information. Relevant man pages besides git-log(1) are git-diff(1) and
342git-rev-list(1).
343
344You can tune the interaction with git by making use of the options explained
345in this section. For example, by configuring the environment variables
346described in the <<history-commands, "History commands">> section.
347
348[[path-limiting]]
349Limit by Path Name
350~~~~~~~~~~~~~~~~~~
351
352If you are interested only in those revisions that made changes to a specific
353file (or even several files) list the files like this:
354
355-----------------------------------------------------------------------------
356$ tig log Makefile README
357-----------------------------------------------------------------------------
358
359To avoid ambiguity with repository references such as tag name, be sure to
360separate file names from other git options using "\--". So if you have a file
361named 'master' it will clash with the reference named 'master', and thus you
362will have to use:
363
364-----------------------------------------------------------------------------
365$ tig log -- master
366-----------------------------------------------------------------------------
367
368NOTE: For the main view, avoiding ambiguity will in some cases require you to
369specify two "\--" options. The first will make tig stop option processing
370and the latter will be passed to git log.
371
372[[date-number-limiting]]
373Limit by Date or Number
374~~~~~~~~~~~~~~~~~~~~~~~
375
376To speed up interaction with git, you can limit the amount of commits to show
377both for the log and main view. Either limit by date using e.g.
378`--since=1.month` or limit by the number of commits using `-n400`.
379
380If you are only interested in changed that happened between two dates you can
381use:
382
383-----------------------------------------------------------------------------
384$ tig -- --after="May 5th" --before="2006-05-16 15:44"
385-----------------------------------------------------------------------------
386
387NOTE: If you want to avoid having to quote dates containing spaces you can use
388"." instead, e.g. `--after=May.5th`.
389
390[[commit-range-limiting]]
391Limiting by Commit Ranges
392~~~~~~~~~~~~~~~~~~~~~~~~~
393
394Alternatively, commits can be limited to a specific range, such as "all
395commits between 'tag-1.0' and 'tag-2.0'". For example:
396
397-----------------------------------------------------------------------------
398$ tig log tag-1.0..tag-2.0
399-----------------------------------------------------------------------------
400
401This way of commit limiting makes it trivial to only browse the commits which
402haven't been pushed to a remote branch. Assuming 'origin' is your upstream
403remote branch, using:
404
405-----------------------------------------------------------------------------
406$ tig log origin..HEAD
407-----------------------------------------------------------------------------
408
409will list what will be pushed to the remote branch. Optionally, the ending
410'HEAD' can be left out since it is implied.
411
412[[reachability-limiting]]
413Limiting by Reachability
414~~~~~~~~~~~~~~~~~~~~~~~~
415
416Git interprets the range specifier "tag-1.0..tag-2.0" as "all commits
417reachable from 'tag-2.0' but not from 'tag-1.0'". Where reachability refers
418to what commits are ancestors (or part of the history) of the branch or tagged
419revision in question.
420
421If you prefer to specify which commit to preview in this way use the
422following:
423
424-----------------------------------------------------------------------------
425$ tig log tag-2.0 ^tag-1.0
426-----------------------------------------------------------------------------
427
428You can think of '^' as a negation operator. Using this alternate syntax, it
429is possible to further prune commits by specifying multiple branch cut offs.
430
431[[refspec-combi]]
432Combining Revisions Specification
433~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
434
435Revisions options can to some degree be combined, which makes it possible to
436say "show at most 20 commits from within the last month that changed files
437under the Documentation/ directory."
438
439-----------------------------------------------------------------------------
440$ tig -- --since=1.month -n20 -- Documentation/
441-----------------------------------------------------------------------------
442
443[[refspec-all]]
444Examining All Repository References
445~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
446
447In some cases, it can be useful to query changes across all references in a
448repository. An example is to ask "did any line of development in this
449repository change a particular file within the last week". This can be
450accomplished using:
451
452-----------------------------------------------------------------------------
453$ tig -- --all --since=1.week -- Makefile
454-----------------------------------------------------------------------------
455
456include::BUGS[]
457
458[[copy-right]]
459Copyright
460---------
461
462Copyright (c) 2006 Jonas Fonseca <fonseca@diku.dk>
463
464This program is free software; you can redistribute it and/or modify
465it under the terms of the GNU General Public License as published by
466the Free Software Foundation; either version 2 of the License, or
467(at your option) any later version.
468
469[[references]]
470References and Related Tools
471----------------------------
472
473Manpages:
474
475 - gitlink:tig[1]
476 - gitlink:tigrc[5]
477
478Online resources:
479
480include::SITES[]
481
482Git porcelains:
483
484 - link:http://www.kernel.org/pub/software/scm/git/docs/[git],
485 - link:http://www.kernel.org/pub/software/scm/cogito/docs/[Cogito]
486
487Other git repository browsers:
488
489 - gitk(1)
490 - qgit(1)
491 - gitview(1)