5 ms·

If it's so great why are people not building it out of emacs :P

Tomte 5y ago
I think https://github.com/jonas/tig https://github.com/jonas/tig and several other such tools are kind-of like that.
thom 5y ago
Edamagit exists for VSCode and is actually quite a faithful conversion. I would love more modes like that in VSCode that just use editor buffers to get work done instead of feeling the need to create lots of inconsistent custom UI.
suprfnk 5y ago
Next to other posters, there's also LazyGit (https://github.com/jesseduffield/lazygit https://github.com/jesseduffield/lazygit), and vimagit (https://github.com/jreybert/vimagit https://github.com/jreybert/vimagit). So yea, people are building it out of emacs!
- izifortune 5y ago
  I have both but I found myself struggling to use vimagit over lazygit as it feel faster to work with. Do you have any specific workflows that you prefer one over the other?
- zelphirkalt 5y ago
  On the lazygit repo readme an animation is shown with a single line commit prompt/dialog. Suspicious. Is there a way to expand that one-lined thing to enter more? So I looked up "multiline commit" in the issues. Several not solved but closed issues came up and multiline commit messages seem to still not be available. This would be an instant deal breaker for me, if I were trying to use lazygit. Commit messages are not bullet points or titles. In magit I can simply type in a new buffer as much as I want to.
  - dceddia 5y ago
    In lazygit you can hit lowercase 'c' to bring up that one-line commit prompt, but you can also hit capital 'C' to open the commit message in your $EDITOR and write out a detailed commit message.
globular-toast 5y ago
Part of its greatness comes from the fact that it's in emacs. Although it might look like a GUI/TUI, magit's interface is all normal emacs buffers with all the normal navigation, selection and editing (where appropriate) features available. That's huge, but difficult to explain why if you don't use emacs. It's frustrating for me because I believe magit is the best git interface there is. Using it increases your understanding of git and decreases your chances of error. I'd really like the rest of my team to use it instead of the CLI. But when I think about it outside of emacs, it just doesn't work.

I think https://github.com/jonas/tig https://github.com/jonas/tig and several other such tools are kind-of like that.

thom 5y ago

Edamagit exists for VSCode and is actually quite a faithful conversion. I would love more modes like that in VSCode that just use editor buffers to get work done instead of feeling the need to create lots of inconsistent custom UI.

suprfnk 5y ago

Next to other posters, there's also LazyGit (https://github.com/jesseduffield/lazygit https://github.com/jesseduffield/lazygit), and vimagit (https://github.com/jreybert/vimagit https://github.com/jreybert/vimagit). So yea, people are building it out of emacs!

izifortune 5y ago
I have both but I found myself struggling to use vimagit over lazygit as it feel faster to work with. Do you have any specific workflows that you prefer one over the other?
zelphirkalt 5y ago
On the lazygit repo readme an animation is shown with a single line commit prompt/dialog. Suspicious. Is there a way to expand that one-lined thing to enter more? So I looked up "multiline commit" in the issues. Several not solved but closed issues came up and multiline commit messages seem to still not be available. This would be an instant deal breaker for me, if I were trying to use lazygit. Commit messages are not bullet points or titles. In magit I can simply type in a new buffer as much as I want to.
- dceddia 5y ago
  In lazygit you can hit lowercase 'c' to bring up that one-line commit prompt, but you can also hit capital 'C' to open the commit message in your $EDITOR and write out a detailed commit message.

globular-toast 5y ago

Part of its greatness comes from the fact that it's in emacs. Although it might look like a GUI/TUI, magit's interface is all normal emacs buffers with all the normal navigation, selection and editing (where appropriate) features available. That's huge, but difficult to explain why if you don't use emacs. It's frustrating for me because I believe magit is the best git interface there is. Using it increases your understanding of git and decreases your chances of error. I'd really like the rest of my team to use it instead of the CLI. But when I think about it outside of emacs, it just doesn't work.