SIZEOF_REV introduced: 41 bytes of pure madness!
[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[[viewer]]
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
134-----------------------------------------------------------------------------
135commit 4d55caff4cc89335192f3e566004b4ceef572521
136-----------------------------------------------------------------------------
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
142[[commit-id]]
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
154[[views]]
155Views
156~~~~~
157
158Various 'views' of a repository is presented. Each view is based on output
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 tree view::
177 Lists directory trees associated with the current revision allowing
178 subdirectories to be descended or ascended and file blobs to be
179 viewed.
180
181The blob view::
182 Displays the file content or "blob" of data associated with a file
183 name.
184
185The pager view::
186 Is used for displaying both input from stdin and output from git
187 commands entered in the internal prompt.
188
189The help view::
190 Displays key binding quick reference.
191
192[[title-window]]
193Title Windows
194~~~~~~~~~~~~~
195
196Each view has a title window which shows the name of the view, current commit
197ID if available, and where the view is positioned:
198
199-----------------------------------------------------------------------------
200[main] c622eefaa485995320bc743431bae0d497b1d875 - commit 1 of 61 (1%)
201-----------------------------------------------------------------------------
202
203By default, the title of the current view is highlighted using bold font. For
204long loading views (taking over 3 seconds) the time since loading started will
205be appended:
206
207-----------------------------------------------------------------------------
208[main] 77d9e40fbcea3238015aea403e06f61542df9a31 - commit 1 of 779 (0%) 5s
209-----------------------------------------------------------------------------
210
211[[keys]]
212Default Keybindings
213-------------------
214Below the default key bindings are shown.
215
216[[view-switching]]
217View Switching
218~~~~~~~~~~~~~~
219
220`-------`--------------------------------------------------------------------
221Key Action
222-----------------------------------------------------------------------------
223m Switch to main view.
224d Switch to diff view.
225l Switch to log view.
226p Switch to pager view.
227t Switch to (directory) tree view.
228f Switch to (file) blob view.
229h Show man page.
230-----------------------------------------------------------------------------
231
232[[view-manipulation]]
233View Manipulation
234~~~~~~~~~~~~~~~~~
235
236`-------`--------------------------------------------------------------------
237Key Action
238-----------------------------------------------------------------------------
239q Close view, if multiple views are open it will jump back to the \
240 previous view in the view stack. If it is the last open view it \
241 will quit. Use 'Q' to quit all views at once.
242Enter This key is "context sensitive" depending on what view you are \
243 currently in. When in log view on a commit line or in the main \
244 view, split the view and show the commit diff. In the diff view \
245 pressing Enter will simply scroll the view one line down.
246Tab Switch to next view.
247Up This key is "context sensitive" and will move the cursor one \
248 line up. However, uf you opened a diff view from the main view \
249 (split- or full-screen) it will change the cursor to point to \
250 the previous commit in the main view and update the diff view \
251 to display it.
252Down Similar to 'Up' but will move down.
253-----------------------------------------------------------------------------
254
255[[cursor-nav]]
256Cursor Navigation
257~~~~~~~~~~~~~~~~~
258
259`-------`--------------------------------------------------------------------
260Key Action
261-----------------------------------------------------------------------------
262j Move cursor one line up.
263k Move cursor one line down.
264PgUp,\
265-,a Move cursor one page up.
266PgDown Space Move cursor one page down.
267Home Jump to first line.
268End Jump to last line.
269-----------------------------------------------------------------------------
270
271[[view-scrolling]]
272Scrolling
273~~~~~~~~~
274
275`-------`--------------------------------------------------------------------
276Key Action
277-----------------------------------------------------------------------------
278Insert Scroll view one line up.
279Delete Scroll view one line down.
280w Scroll view one page up.
281s Scroll view one page down.
282-----------------------------------------------------------------------------
283
284[[searching]]
285Searching
286~~~~~~~~~
287
288`-------`--------------------------------------------------------------------
289Key Action
290-----------------------------------------------------------------------------
291/ Search the view. Opens a prompt for entering search regex to use.
292? Search backwards in the view. Also prompts for regex.
293n Find next match for the current search regex.
294N Find previous match for the current search regex.
295-----------------------------------------------------------------------------
296
297[[misc-keys]]
298Misc
299~~~~
300
301`-------`--------------------------------------------------------------------
302Key Action
303-----------------------------------------------------------------------------
304Q Quit.
305r Redraw screen.
306z Stop all background loading. This can be useful if you use \
307 tig in a repository with a long history without limiting \
308 the revision log.
309v Show version.
310'.' Toggle line numbers on/off.
311g Toggle revision graph visualization on/off.
312':' Open prompt. This allows you to specify what git command \
313 to run. Example `:log -p`
314-----------------------------------------------------------------------------
315
316[[refspec]]
317Revision Specification
318----------------------
319
320This section describes various ways to specify what revisions to display or
321otherwise limit the view to. Tig does not itself parse the described
322revision options so refer to the relevant git man pages for futher
323information. Relevant man pages besides git-log(1) are git-diff(1) and
324git-rev-list(1).
325
326You can tune the interaction with git by making use of the options explained
327in this section. For example, by configuring the environment variables
328described in the <<history-commands, "History commands">> section.
329
330[[path-limiting]]
331Limit by Path Name
332~~~~~~~~~~~~~~~~~~
333
334If you are interested only in those revisions that made changes to a specific
335file (or even several files) list the files like this:
336
337-----------------------------------------------------------------------------
338$ tig log Makefile README
339-----------------------------------------------------------------------------
340
341To avoid ambiguity with repository references such as tag name, be sure to
342separate file names from other git options using "\--". So if you have a file
343named 'master' it will clash with the reference named 'master', and thus you
344will have to use:
345
346-----------------------------------------------------------------------------
347$ tig log -- master
348-----------------------------------------------------------------------------
349
350NOTE: For the main view, avoiding ambiguity will in some cases require you to
351specify two "\--" options. The first will make tig stop option processing
352and the latter will be passed to git log.
353
354[[date-number-limiting]]
355Limit by Date or Number
356~~~~~~~~~~~~~~~~~~~~~~~
357
358To speed up interaction with git, you can limit the amount of commits to show
359both for the log and main view. Either limit by date using e.g.
360`--since=1.month` or limit by the number of commits using `-n400`.
361
362If you are only interested in changed that happened between two dates you can
363use:
364
365-----------------------------------------------------------------------------
366$ tig -- --after="May 5th" --before="2006-05-16 15:44"
367-----------------------------------------------------------------------------
368
369NOTE: If you want to avoid having to quote dates containing spaces you can use
370"." instead, e.g. `--after=May.5th`.
371
372[[commit-range-limiting]]
373Limiting by Commit Ranges
374~~~~~~~~~~~~~~~~~~~~~~~~~
375
376Alternatively, commits can be limited to a specific range, such as "all
377commits between 'tag-1.0' and 'tag-2.0'". For example:
378
379-----------------------------------------------------------------------------
380$ tig log tag-1.0..tag-2.0
381-----------------------------------------------------------------------------
382
383This way of commit limiting makes it trivial to only browse the commits which
384haven't been pushed to a remote branch. Assuming 'origin' is your upstream
385remote branch, using:
386
387-----------------------------------------------------------------------------
388$ tig log origin..HEAD
389-----------------------------------------------------------------------------
390
391will list what will be pushed to the remote branch. Optionally, the ending
392'HEAD' can be left out since it is implied.
393
394[[reachability-limiting]]
395Limiting by Reachability
396~~~~~~~~~~~~~~~~~~~~~~~~
397
398Git interprets the range specifier "tag-1.0..tag-2.0" as "all commits
399reachable from 'tag-2.0' but not from 'tag-1.0'". Where reachability refers
400to what commits are ancestors (or part of the history) of the branch or tagged
401revision in question.
402
403If you prefer to specify which commit to preview in this way use the
404following:
405
406-----------------------------------------------------------------------------
407$ tig log tag-2.0 ^tag-1.0
408-----------------------------------------------------------------------------
409
410You can think of '^' as a negation operator. Using this alternate syntax, it
411is possible to further prune commits by specifying multiple branch cut offs.
412
413[[refspec-combi]]
414Combining Revisions Specification
415~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
416
417Revisions options can to some degree be combined, which makes it possible to
418say "show at most 20 commits from within the last month that changed files
419under the Documentation/ directory."
420
421-----------------------------------------------------------------------------
422$ tig -- --since=1.month -n20 -- Documentation/
423-----------------------------------------------------------------------------
424
425[[refspec-all]]
426Examining All Repository References
427~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
428
429In some cases, it can be useful to query changes across all references in a
430repository. An example is to ask "did any line of development in this
431repository change a particular file within the last week". This can be
432accomplished using:
433
434-----------------------------------------------------------------------------
435$ tig -- --all --since=1.week -- Makefile
436-----------------------------------------------------------------------------
437
438include::BUGS[]
439
440[[copy-right]]
441Copyright
442---------
443
444Copyright (c) 2006 Jonas Fonseca <fonseca@diku.dk>
445
446This program is free software; you can redistribute it and/or modify
447it under the terms of the GNU General Public License as published by
448the Free Software Foundation; either version 2 of the License, or
449(at your option) any later version.
450
451[[references]]
452References and Related Tools
453----------------------------
454
455Manpages:
456
457 - gitlink:tig[1]
458 - gitlink:tigrc[5]
459
460Online resources:
461
462include::SITES[]
463
464Git porcelains:
465
466 - link:http://www.kernel.org/pub/software/scm/git/docs/[git],
467 - link:http://www.kernel.org/pub/software/scm/cogito/docs/[Cogito]
468
469Other git repository browsers:
470
471 - gitk(1)
472 - qgit(1)
473 - gitview(1)