summaryrefslogtreecommitdiff
path: root/test/normal/insert-replace/cmd
diff options
context:
space:
mode:
authorJohannes Altmanninger <aclopte@gmail.com>2024-02-03 00:26:58 +0100
committerMaxime Coste <mawww@kakoune.org>2024-02-05 21:42:02 +1100
commit4e13fbef0a8d1d6fd63b29051bb408d436bd50d5 (patch)
treee258fd216b4430bb536ee8b10102ee8469d9461a /test/normal/insert-replace/cmd
parent24bf123503c06c44e73892aaf1ae550ae11af66e (diff)
rc tools git: support blame in git-diff and git-log buffers
Today we can recursively search history with "git blame-jump". However that command has some drawbacks, mainly that it's blocking. Making it async without any progress indicator might be confusing. Better to run plain "git blame"[1] and press Enter. Also it might be nice to enable recursive searches using only "git blame" and `<ret>` (since that is bound to "git blame-jump" while blame annotations are displayed). Make "git blame" in git-diff/git-log buffers run "git show $commit:$file" for the commit and file at cursor, and decorate this blob view with blame annotations. The latter allows to use `<ret>` and repeat. Unfortunately this relies on a hidden option "git_blob" to keep the commit ID and filename. Maybe we can put this metadata somewhere else like the buffer name or contents, ideally in a way that survives serialization. I'd still keep "git blame-jump" because it seems faster for the common case of tracking down a single line. [1]: In my testing, "git blame --incremental" is not any slower than "git blame -L123,123" at finding that line.
Diffstat (limited to 'test/normal/insert-replace/cmd')
0 files changed, 0 insertions, 0 deletions