From d4914b361b081c4d983e924f1dd337c143152833 Mon Sep 17 00:00:00 2001 From: Tim Pope Date: Wed, 6 Sep 2023 14:25:04 -0400 Subject: [PATCH] Discourage use of P and ~ in blame window. Since 09908d82efc602fde72ef02ae05a75953376f842, I've been getting a parade of issues and PRs about "missing" documentation. Resolves: https://github.com/tpope/vim-fugitive/pull/2210 References: https://github.com/tpope/vim-fugitive/issues/2070 --- doc/fugitive.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/fugitive.txt b/doc/fugitive.txt index 63a399e..d5d4300 100644 --- a/doc/fugitive.txt +++ b/doc/fugitive.txt @@ -72,6 +72,16 @@ that are part of Git repositories). p jump to patch or blob in preview window - reblame at commit + The maps |fugitive_P| and |fugitive_~| are also + supported to reblame on a parent commit, but this is + inherently fragile, as the line being blamed will no + longer exist. The preferred alternative is to use + to open up the commit, select the corresponding + `-` line that you care about, and press twice + more to reblame at that line. Viewing the commit also + gives you additional context as to why the line + changed. + *g:fugitive_dynamic_colors* In the GUI or a 256 color terminal, commit hashes will be highlighted in different colors. To disable this: