3 ms·
I have started using lazygit, a CUI, or console user interface. It runs in my terminal window but gives me the same broader perspective a GUI does. Looking at t
by talkingtab 6y ago
I have started using lazygit, a CUI, or console user interface. It runs in my terminal window but gives me the same broader perspective a GUI does. Looking at the screenshots of Guitar, which look amazing, I realize with lazygit I get 95% of the benefit of a GUI but in a package that does not disturb my workflow.
https://github.com/jesseduffield/lazygit https://github.com/jesseduffield/lazygit
There are edge cases that lazygit does not handle well, but it is a simple matter to type "q", bop back to the terminal and run whatever git command and get on with life.
- xorcist 6y agoThe most well known TUI/CUI for git is probably tig: https://jonas.github.io/tig/ https://jonas.github.io/tig/ Emacs users will always have magit, but for everyone else it can be handy to use GUI tools for interactive staging and interactive rebase.
- tomaspollak 6y agoWhich cases does lazygit not handle well? Asking because I'm working on something similar, although probably simpler and with less features [0]. [0] https://tomas.github.io/jix https://tomas.github.io/jix
- talkingtab 6y agoWhen I think about the situations where I don't use lazygit, it is when I am unsure of what I am doing and therefore unsure what lazygit is doing. Almost everything I normally do with git, I can do with lazygit, but there are things I am not confident about. Squashing commits versus picking and do they go up or down, etc? Rebasing. I tend to go to command-line git in those cases, not because lazygit does not handle them but because I don't. :-) The crucial advantage of lazygit for me is the "situational awareness" I gain in one window - more than any added functionality. The other take away is for your tools to be utterly trustworthy. :-)
- tomaspollak 6y agoGotcha, thanks.