CTRLGGitBlame.vim
Append git blame information to the output of <C-g> (by andlrc)
hired
A modern take on 'ed' (by sidju)
| CTRLGGitBlame.vim | hired | |
|---|---|---|
| 5 | 6 | |
| 9 | 117 | |
| - | - | |
| 0.0 | 6.0 | |
| over 1 year ago | 3 months ago | |
| Vim Script | Rust | |
| MIT License | 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
hired
Posts with mentions or reviews of hired.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-02-13.
- Hired: A Modern Take on 'Ed'
-
The ! command, what do you use it for?
( The ed clone I am writing: https://github.com/sidju/hired , and its backend: https://github.com/sidju/add-ed )
- Thoughts on some of the actively developed text editors written in Rust?
-
Nano vs Vim (text editor)
OR, use modern ED! https://github.com/sidju/hired Syntax highlighting, command history and replaceable backend.
-
Interface test for all structs that implement a trait
My current solution is to have it written implementation agnostic for the only implementation that currently exists. ( Seen here: https://github.com/sidju/hired/blob/bde09775eca11c3f98f88f29eb006f4dc6e057fd/src/buffer/vecbuffer.rs#L249 ) In the longer term I intend on writing a macro that essentially creates that exact test but replaces the constructor ("VecBuffer::new()") with whatever string is given to the macro. That should work well, but will have to wait a little.
What are some alternatives?
When comparing CTRLGGitBlame.vim and hired you can also consider the following projects:
fzf-git.sh - bash and zsh key bindings for Git objects, powered by fzf
lapce - Lightning-fast and Powerful Code Editor written in Rust
scripts - My ~/bin
kibi - A text editor in ≤1024 lines of code, written in Rust
vim-git-arglist - Vim commands for manipulating the arglist based on the current Git repository
pepper - simple and opinionated modal code editor for your terminal
jless - jless is a command-line JSON viewer designed for reading, exploring, and searching through JSON data.
glyph - My own personal code editor built with Rust + OpenGL
vimfiles
dotfiles - ❄️ My dotfiles for NixOS and macOS as a Nix flake. Neovim, Fish shell, Wezterm, etc.
fzf.vim - fzf :heart: vim
add-ed - Embeddable ED in rust