Committed comparisons
Development reference · View source
Tab d in the branch or worktree list opens a read-only committed
comparison: the current tip on the left, the selected local branch, cached
remote branch, or worktree HEAD on the right.
- It compares the contents at the two tips directly. Uncommitted changes, staged changes, and unsaved buffers are excluded.
- Nothing is fetched or checked out.
- Detached worktrees are labelled with their commit ID. A worktree with no available commit cannot be compared.
| Key | Action in the committed comparison list |
|---|---|
Enter | Open this file’s unified patch |
Tab d | Open this file’s complete versions in a temporary split |
Space g r | Capture fresh tips and refresh the list |
Reading it:
- The heading names both sides and their captured commit IDs.
- Each row shows the path on each side and added/removed line counts. The
summary totals and per-file counts use
change_addedandchange_removed(green and red in built-in themes); only the signed counts are coloured. - Renames show both names;
—marks an absent side. Narrow panes combine the two paths into one column. - Binary and metadata-only changes are labelled. Empty added or deleted files stay visible.
- Identical tips show
No committed differences.
Stability:
- The list, counts, patches, and splits all use the captured commits, even if a branch moves while you browse.
- Refresh keeps the selected file when possible.
- Closing a patch returns to the list at the same file and scroll position.
Closing either split side, or
:diff-off, collapses the pair and restores that position too. - Movement, search, selection, and copying work as usual. Binary files show their patch metadata but cannot open as a text split.