A work-in-progress Magit clone for Neovim • Hacker News Board

Re: A work-in-progress Magit clone for Neovim

#51

Post by gpderetta » Thu, Jul 08, 2021, 12:37 PM UTC

NateEag wrote: post #50

gpderetta wrote: post #31

Earlier quoted context omitted.

magit does similar things with interactive rebases, although it is keyboard driven (I never tried to use the mouse). Another nice feature is the instant fixup where you can easily commit+rebase+fixup (think of commit --amend, but against any commit).

FYI, command-line Git is where fixup and autosquash come from: https://blog.sebastian-daschner.com/entries/git-commit-fixup... Magit makes the feature easier to use and more discoverable, though.

yes of course, the magit rebase buffer is literally the git rebase file with a custom emacs mode on top for interactivity.

Re: A work-in-progress Magit clone for Neovim

#52

Post by rjzzleep » Thu, Jul 08, 2021, 1:11 PM UTC

ackyshake wrote: post #34

Very early on in my vim journey, I used to use fugitive[1], which is sort of a lighter equivalent of magit for vim. However, I found that too overkill and unwieldy. I never really found any benefits to forcing myself to stay inside vim to run some git command. These days, I just use git in a tmux split rather than trying to force vim to show some arbitrary git UI. For a nice interactive git UI, I use tig[1]. Tig is e…

Well that's useful.

I've been using `!tig` forever. For some reason it was convenient enough for me to never turn it into a mapping. I feel like `tig` damaged me in the sense that using tig and then pressing `S` is my usual workflow, so I just can't get used to either fugitive or magit.

Thanks for these mappings

Re: A work-in-progress Magit clone for Neovim

#53

Post by rjzzleep » Thu, Jul 08, 2021, 1:16 PM UTC

rerx wrote: post #43

tbabej wrote: post #40

Earlier quoted context omitted.

> Commiting hunks on command line is tedious afaik. You would have to specify row numbers. Not necessarily tedious - you can just use "git add -p" to stage hunks individually.

In Magit you can easily select arbitrary regions of code to stage (or chunks as you would via the command line). I haven't seen any git interface that is as intuitive for this task.

Try pressing `S` in `tig`. Works like magit but is much faster(when I say faster I'm also including interface lag). I realize that you won't switch, nor do you need to, but the general things people suggest of why magit is superior exist elsewhere as well.

Re: A work-in-progress Magit clone for Neovim

#54

Post by synthc » Thu, Jul 08, 2021, 1:46 PM UTC

tut-urut-utut wrote: post #10

Although I'm a heavy Emacs user, I never understood why is magit so praised. IMHO, source control just doesn't belong to IDE. Why learn how to use git with Emacs/magit, vim, IntelliJ IDEA, Eclipse, Visual Studio / Code, ... when you can just master the official command line client and forget about the rest? It's available and usable everywhere, while each of these IDE plugins is different and one need to learn and ge…

because Magit is so much more convenient and user friendly than the CLI?

You don't have to learn all the plugins, I only use magit.

Re: A work-in-progress Magit clone for Neovim

#55

Post by rerx » Thu, Jul 08, 2021, 1:46 PM UTC

rjzzleep wrote: post #53

rerx wrote: post #43

Earlier quoted context omitted.

In Magit you can easily select arbitrary regions of code to stage (or chunks as you would via the command line). I haven't seen any git interface that is as intuitive for this task.

Try pressing `S` in `tig`. Works like magit but is much faster(when I say faster I'm also including interface lag). I realize that you won't switch, nor do you need to, but the general things people suggest of why magit is superior exist elsewhere as well.

Thanks for the tip, I haven't tried tig yet. That might actually be useful on remote systems in situations where I don't have access to my personally configured emacs.

Re: A work-in-progress Magit clone for Neovim

#56

Post by scooble » Thu, Jul 08, 2021, 2:14 PM UTC

NateEag wrote: post #46

tbabej wrote: post #40

Earlier quoted context omitted.

> Commiting hunks on command line is tedious afaik. You would have to specify row numbers. Not necessarily tedious - you can just use "git add -p" to stage hunks individually.

`git add -p` is nice, but Magit's UI is superior, IMO. I don't know a way to stage individual lines from a given hunk separately in Git's interactive add, but in Magit's that's easy - just select the line you want and press s. I've even occasionally staged part of a line via selection, when I've actually had two distinct bugfixes on the same line.

Iirc you can edit the patch in git add -p. So fine editing is possible.

Re: A work-in-progress Magit clone for Neovim

#57

Post by catern » Thu, Jul 08, 2021, 2:28 PM UTC

As an alternative, there's no reason why one couldn't use neovim and magit (using Emacs only for magit). Emacs is an application framework, there's no reason why one has to use the "editor" application if all you want to use is the "magit" applciation.

Re: A work-in-progress Magit clone for Neovim

#58

Post by airblade » Thu, Jul 08, 2021, 2:29 PM UTC

tomxor wrote: post #19

tut-urut-utut wrote: post #10

Although I'm a heavy Emacs user, I never understood why is magit so praised. IMHO, source control just doesn't belong to IDE. Why learn how to use git with Emacs/magit, vim, IntelliJ IDEA, Eclipse, Visual Studio / Code, ... when you can just master the official command line client and forget about the rest? It's available and usable everywhere, while each of these IDE plugins is different and one need to learn and ge…

> ... when you can just master the official command line client and forget about the rest? I generally agree, I want the full git interface, which is available everywhere and has no limitations and is not bound to a particular editor. There is however one area I do find useful to have integrated into an editor, various kinds of code annotations... e.g gitgutter, I use this in vim - these type of features compliment g…

> gitgutter is no git diff

FYI in gitgutter you can preview the diff for any change (and also edit the hunk and stage it).

Re: A work-in-progress Magit clone for Neovim

#59

Post by probotect0r » Thu, Jul 08, 2021, 2:50 PM UTC

ackyshake wrote: post #34

Very early on in my vim journey, I used to use fugitive[1], which is sort of a lighter equivalent of magit for vim. However, I found that too overkill and unwieldy. I never really found any benefits to forcing myself to stay inside vim to run some git command. These days, I just use git in a tmux split rather than trying to force vim to show some arbitrary git UI. For a nice interactive git UI, I use tig[1]. Tig is e…

I have started using lazygit in tmux splits or neovim terminals and I love it!

Re: A work-in-progress Magit clone for Neovim

#60

Post by sodapopcan » Thu, Jul 08, 2021, 3:23 PM UTC

ackyshake wrote: post #34

Very early on in my vim journey, I used to use fugitive[1], which is sort of a lighter equivalent of magit for vim. However, I found that too overkill and unwieldy. I never really found any benefits to forcing myself to stay inside vim to run some git command. These days, I just use git in a tmux split rather than trying to force vim to show some arbitrary git UI. For a nice interactive git UI, I use tig[1]. Tig is e…

Fugitive is really useful for a lot of stuff, though I don't use anywhere near all of its functionality. For example, I never rebase within vim. But blaming and especially staging/committing is a far better experience with fugitive than in plain terminal.