CTRLGGitBlame.vim
Append git blame information to the output of <C-g> (by andlrc)
fzf-git.sh
bash and zsh key bindings for Git objects, powered by fzf (by junegunn)
| CTRLGGitBlame.vim | fzf-git.sh | |
|---|---|---|
| 5 | 3 | |
| 9 | 411 | |
| - | - | |
| 0.0 | 6.8 | |
| over 1 year ago | 7 days ago | |
| Vim Script | Shell | |
| MIT License | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CTRLGGitBlame.vim
Posts with mentions or reviews of CTRLGGitBlame.vim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-25.
-
VIM Dashboard!
With my small plugin https://github.com/andlrc/CTRLGGitBlame.vim the later is easy to get going as @c will be hydrated with the sha for the blamed line.
- Echoing git blame - my first real vimscript success
-
Project & File navigation
Last but not least, I use my own plugin that extends to include git blame information: https://github.com/andlrc/CTRLGGitBlame.vim This helps me understand the motivation behind a change. It also populates @c with the commit, making it possible to write things like:
-
The ! command, what do you use it for?
git log -p ties into https://github.com/andlrc/CTRLGGitBlame.vim populating the c register.
- Extend <C-g> with git blame information
fzf-git.sh
Posts with mentions or reviews of fzf-git.sh.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-17.
-
fzf-flatpak script and shell function for flatpak
So I tried creating a flatpak scripts powered by fzf was inpired by this (fzf-git.sh). Andalso just seen this post and added this to shell function.
-
Project & File navigation
Which now I see has been migrated to https://github.com/junegunn/fzf-git.sh
- fzf-git.sh: bash and zsh key bindings for Git objects, powered by fzf
What are some alternatives?
When comparing CTRLGGitBlame.vim and fzf-git.sh you can also consider the following projects:
scripts - My ~/bin
dootsfile - 🏠 - Personal Dotfiles (Managed by GNU Stow)
vim-git-arglist - Vim commands for manipulating the arglist based on the current Git repository
ranger.vim - Ranger integration in vim and neovim
jless - jless is a command-line JSON viewer designed for reading, exploring, and searching through JSON data.
fzf.vim - fzf :heart: vim
vimfiles
vim-lsp - async language server protocol plugin for vim and neovim
tig - Text-mode interface for git
add-ed - Embeddable ED in rust
nerdtree - A tree explorer plugin for vim.
CTRLGGitBlame.vim vs scripts
fzf-git.sh vs dootsfile
CTRLGGitBlame.vim vs vim-git-arglist
fzf-git.sh vs ranger.vim
CTRLGGitBlame.vim vs jless
fzf-git.sh vs fzf.vim
CTRLGGitBlame.vim vs vimfiles
fzf-git.sh vs vim-lsp
CTRLGGitBlame.vim vs fzf.vim
fzf-git.sh vs tig
CTRLGGitBlame.vim vs add-ed
fzf-git.sh vs nerdtree