diff options
| author | Dan Davison <dandavison7@gmail.com> | 2021-03-05 23:38:54 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-05 23:38:54 -0500 |
| commit | 2619d07fa4ee701a19a08351ac4d3e7622e42877 (patch) | |
| tree | 757e8b066611963ecb8183fe8379a1da06500de6 /README.md | |
| parent | 4fb55fa820aac3e4e534000bf65dc5050ec0630b (diff) | |
237 navigate improvement (#526)
* Change less invocation under navigate
Thanks @cben
* Don't pass regexp to less
* Append navigate regexp to transient copy of less history file
* Rustfmt
* Store delta less hist file in XDG data directory
* Don't use xdg on Windows
* Fix conditional compilation for Windows
* Get rid of advice not to use keep navigate feature activated
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 8 |
1 files changed, 0 insertions, 8 deletions
@@ -448,14 +448,6 @@ In order to support this feature, Delta has to look at the raw colors it receive Use the `navigate` feature to activate navigation keybindings. In this mode, pressing `n` will jump forward to the next file in the diff, and `N` will jump backwards. If you are viewing multiple commits (e.g. via `git log -p`) then navigation will also visit commit boundaries. -The recommended way to use `navigate` is to activate it only when needed, for example - -```bash -git -c delta.navigate=true log -p -``` - -The reason that `navigate` should not be used all the time is that Delta uses `less` as its pager, and the `navigate` feature works by doing `less --pattern <regex-matching-file-and-commit-lines>`. When the git output does not contain file/commit diff lines, `less --pattern` behaves unhelpfully (see [#234](https://github.com/dandavison/delta/issues/234), [#237](https://github.com/dandavison/delta/issues/237)). - ### 24 bit color (truecolor) |