mirror of
https://github.com/amix/vimrc
synced 2025-07-02 05:05:00 +08:00
Updated plugins
This commit is contained in:
@ -49,8 +49,9 @@ that are part of Git repositories).
|
||||
|
||||
*fugitive-summary*
|
||||
:Git With no arguments, bring up a summary window vaguely
|
||||
akin to git-status. Press g? or see |fugitive-maps|
|
||||
for usage.
|
||||
akin to git-status. If a summary window is already
|
||||
open for the current repository, it is focused
|
||||
instead. Press g? or see |fugitive-maps| for usage.
|
||||
|
||||
*:Git_blame*
|
||||
:Git blame [flags] Run git-blame [flags] on the current file and open the
|
||||
@ -71,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
|
||||
<CR> to open up the commit, select the corresponding
|
||||
`-` line that you care about, and press <CR> 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:
|
||||
|
Reference in New Issue
Block a user