3 ms·
I recommend just skipping blame and going to git log -L to see the full evolution of a range of lines, I set up a little keybind in vim which does this for the
by PhilipRoman 3y ago
I recommend just skipping blame and going to git log -L to see the full evolution of a range of lines, I set up a little keybind in vim which does this for the current visual selection and it works much better than blame.
- a_e_k 3y agoAnd for those using Magit in Emacs, you can do this by selecting a region of lines and hitting `C-c M-g l`. https://magit.vc/manual/magit/Commands-for-Buffers-Visiting-Files.html#index-C_002dc-M_002dg-l https://magit.vc/manual/magit/Commands-for-Buffers-Visiting-...
- jmholla 3y agoNice. Can you share your vim configuration for that?
- PhilipRoman 3y agoMy config is kind of cluttered so this is a simplified version without dependencies. Glogr is for range history, GLogf for file history and <leader>gc for showing a commit based on hash: nnoremap <leader>gc :Gshow <C-R><C-W><cr> command! -nargs=1 Gshow enew | set ft=diff buftype=nofile | 0r!git log -p -n 1 "<args>" command! -nargs=0 Glogf tabnew | set ft=diff buftype=nofile | 0r!git -C "#:h" log -p --follow "#:t" command! -nargs=0 -range Glogr tabnew | set ft=diff buftype=nofile | 0r!git -C "#:h" log -L "<line1>,<line2>:#:t"