add-ed
CTRLGGitBlame.vim
| add-ed | CTRLGGitBlame.vim | |
|---|---|---|
| 5 | 5 | |
| 12 | 9 | |
| - | - | |
| 5.9 | 0.0 | |
| 26 days ago | over 1 year ago | |
| Rust | Vim Script | |
| MIT License | MIT License |
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.
add-ed
-
Hired: A Modern Take on 'Ed'
It isn't too late yet, you can be the one to bring The Standard Editor to the Webshit masses!
The backing library https://github.com/sidju/add-ed could either be run through https://neon-bindings.com/ , or compiled into web assembly for that matter. Should just be a weekend project to create an electron `ed`, and if that isn't sufficiently bloated you can `node install everything`.
-
pacdef, the declarative package manager for Arch, releases v1.0.0
When/if "later (TM)" occurs, I recommend defining your tests using fixtures/check functions. For example, my library requires a fair bit of work both to setup an arbitrary state and read the resulting state after a test. Since that is needed in every test I have abstracted it into this function https://github.com/sidju/add-ed/blob/main/tests/shared/inner_fixture.rs , which I then create more readable/usable wrappers around here https://github.com/sidju/add-ed/blob/main/tests/shared/fixtures.rs .
-
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 )
- Intuitive: A crate for writing TUIs declaratively
CTRLGGitBlame.vim
-
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
What are some alternatives?
hired - A modern take on 'ed'
fzf-git.sh - bash and zsh key bindings for Git objects, powered by fzf
scripts - My ~/bin
jless - jless is a command-line JSON viewer designed for reading, exploring, and searching through JSON data.
vim-git-arglist - Vim commands for manipulating the arglist based on the current Git repository
intuitive - A library for building declarative text-based user interfaces
vimfiles
fzf.vim - fzf :heart: vim
tig - Text-mode interface for git
vim-gutentags - A Vim plugin that manages your tag files