I wrote a script that takes two git commits and opens all changed files in vimdiff tabs side by side. I find lots of things too hard to see in github gui. It depends one [tpope's vim-fugitive]. [tpope's vim-fugitive]: https://github.com/tpope/vim-fugitive I'll paste it next time I'm on that machine. - Source: Hacker News / 5 months ago

For vim heads also worth checking out tpope's fugitive: https://github.com/tpope/vim-fugitive Very useful for inspecting and staging changes, making commits, etc. I find you can pretty much do anything with it, and it's much faster than anything else, but it does have a slight learning curve. The documentation is very good! - Source: Hacker News / 5 months ago

I tried helix a few months ago. Before that, I gave it a try several times. The editor is fine, but I always go back to vim and vscode for these reasons: - In vim, I can use vim-fugitive [1] to easily run git add and git commit. Not sure if helix has that level of integration with Git (I like the gutter, though). - I prefer vscode to code in Rust because of rust-analyzer [2]. That plugin gives me type type... - Source: Hacker News / 9 months ago

I agree, navigating blame history is incredibly useful, if only to save you from asking the wrong person about a particular change. Vim's Fugitive[1] can do this and also in Textmate to. So I would hope that most editor git plugins can. 1. https://github.com/tpope/vim-fugitive. - Source: Hacker News / over 2 years ago

You'll want to invest the time in learning Magit, which will change your life once you get the hang of it (and I was a heavy user of Fugitive in Vim previously!), and it's unlikely you'll find a better integration with GDB anywhere else on the planet than with Emacs, though I can't say that empirically. You just need to take the plunge and start learning it, then cut over and take the hit in productivity one day... Source: almost 3 years ago

Try pasting your code into a validator to see if you don't have a typo somewhere: https://beautifytools.com/javascript-validator.php. Source: about 4 years ago

So everything works fine the way I see it and that error only comes up after a few clicks. Since I'm not a js wizard I did put your script code into a javascript validator and it looks like you're missing a couple of semi colons here and there, maybe that'll fix it. Source: over 4 years ago