No fugitive (via vim) videos yet. You could help us improve this page by suggesting one.
Based on our record, fugitive (via vim) should be more popular than Flox. It has been mentiond 69 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
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 1 year 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: over 1 year ago
For an option that works on Vim, if you already use tpope's vim-fugitive, there's vim-rhubarb (for GitHub) and fugitive-gitlab.vim (for GitLab). Source: almost 2 years ago
I replace vim-fugitive with :! git. Source: almost 2 years ago
The only thing I truly miss from Emacs is [Magit](https://magit.vc/) since I still consider it the best git wrapper available. It is just too good. Unfortunately [Neogit](https://github.com/TimUntersberger/neogit) is not quite there yet although I hope it makes it at some point. I didn't like [Fugitive]https://github.com/tpope/vim-fugitive), but I ended up finding a good enough workaround by using... Source: almost 2 years ago
Is the objective to get inside a container to do dev stuff? Reminds me of https://www.jetify.com/devbox and https://flox.dev/. - Source: Hacker News / about 1 month ago
I think it's a bad addition since it pushes people towards a worse solution to a common problem. Using "go tool" forces you to have a bunch of dependencies in your go.mod that can conflict with your software's real dependency requirements, when there's zero reason those matter. You shouldn't have to care if one of your developer tools depends on a different version of a library than you. It makes it so the tools... - Source: Hacker News / 3 months ago
I think that's a bit reductive, but I get the intent. A lot of people see systemic problems in their development and turn to tools to reduce the cognitive load, busywork, or just otherwise automate a solution. For example "we always argue over formatting" -> use an automated formatter. That makes total sense as long as managing/interacting with the tool is less work, not just different work. With Nix I still think... - Source: Hacker News / 4 months ago
Try flox [0]. It's an imperative frontend for Nix that I've been using. I don't know how to use nix-shell/flakes or whatever it is they do now, but flox makes it easy to just install stuff. [0]: https://flox.dev/. - Source: Hacker News / 4 months ago
If you like NixOs and virtual development environments, perhaps try https://www.jetify.com/devbox or https://flox.dev/. - Source: Hacker News / 4 months ago
lazygit - Simple terminal UI for git commands.
Podman - Simple debugging tool for pods and images
Magit - Front-end to the git revision control system for emacs.
devenv - Fast, Declarative, Reproducible, and Composable dev envs
tig - TIG Software Updates & Expansions. Download the most up-to-date, innovative software solutions for your TIG welder instantly to a memory card for enhanced performance.
DevBox - Everyday utilities for the everyday developer