diff options
| author | Dan Davison <dandavison7@gmail.com> | 2021-11-15 10:22:17 -0500 |
|---|---|---|
| committer | Dan Davison <dandavison7@gmail.com> | 2021-11-15 10:22:17 -0500 |
| commit | d083953403da7ea52904d2d4b25dc0091de4155e (patch) | |
| tree | ad5236a8abae3f7be9bf524af0a36feac697054b | |
| parent | 986ebe023e3d2e713c305a0847ff922aa0eebf2c (diff) | |
README edit
| -rw-r--r-- | README.md | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -58,7 +58,7 @@ Code evolves, and we all spend time studying diffs. Delta aims to make this both - [Installation](#installation) - [Configuration](#configuration) - [Git config file](#git-config-file) - - [How delta works](#how-delta-works) +- [How delta works](#how-delta-works) - [Usage](#usage) - [Choosing colors (styles)](#choosing-colors-styles) - [Line numbers](#line-numbers) @@ -323,7 +323,7 @@ Delta also handles unified diff format, e.g. `diff -u a.txt b.txt | delta`. For Mercurial, you can add delta, with its command line options, to the `[pager]` section of `.hgrc`. -#### How delta works +## How delta works If you configure delta in gitconfig as above, then git will automatically send its output to delta. Delta in turn passes its own output on to a "real" pager. @@ -331,6 +331,7 @@ Note that git will only send its output to delta if git believes that its output In other words, if you do something like `git diff | grep ...` then you don't have to worry about delta changing the output from git, because delta will never be invoked at all. If you need to force delta to be invoked when git itself would not invoke it, then you can always pipe to delta explicitly. For example, `git diff | delta | something-that-expects-delta-output-with-colors` (in this example, git's output is being sent to a pipe, so git itself will not invoke delta). +In general however, delta's output is intended for humans, not machines. The pager that delta uses is determined by consulting the following environment variables (in this order): |