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