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