Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lazygit: A simple terminal UI for Git commands

github.com

Post reply on HN
Print view View original

121–130 of 143 posts

Re: Lazygit: A simple terminal UI for Git commands

#121

Post by phonebucket »

ahurmazda wrote: post #86
7kay wrote: post #72

Earlier quoted context omitted.

May I ask what made you choose lazygit instead of fugitive? I'm using the latter and am quite happy with it, but I'm keen to learn what I'm missing out on.

Personally I’m not a fan of the fugitive/magit style UI, ie learn a bunch of esoteric commands (:Git blah) so that you don’t need to remember the other set of original commands. With lazygit/tig, at least there is a visual pager with shortcut letter I need to press along with a text hint about what it actually does.

> ie learn a bunch of esoteric commands (:Git blah) so that you don’t need to remember the other set of original commands

I use fugitive, but haven't remembered these commands. I map what they do to shortcuts of my choosing e.g. \gad = git add; \gco = git commit; \gpus = git push etc.

Re: Lazygit: A simple terminal UI for Git commands

#122

Post by deergomoo »

drainyard wrote: post #35
Groxx wrote: post #23

Earlier quoted context omitted.

Literally every git GUI I've used has screwed up a git repository at some point, requiring relatively-advanced CLI use to untangle it. They're wildly untrustworthy IMO. They also almost never perform reasonably on truly large repos, aside from gitk. Since using a GUI has inevitably required me to learn CLI in depth, and adds the complexity of figuring out what the hell the GUI actually did because of course it doesn'…

I found this to be true for a long time, but these days you have something like Fork which is much lore user friendly and FAST! We used to use Sourcetree, which is an abomination in comparison. I always use(d) the terminal, but Fork is the first time I am considering using a GUI as my main tool. Granted I haven't had to do anything complicated yet with it, so I don't know if it supports it, but I love it for the basi…

Fork is fantastic, plus it’s nice to have a piece of quality software that doesn’t require a subscription. That said, if they released a new major version I would likely pay for it because I’ve been very happy.

Re: Lazygit: A simple terminal UI for Git commands

#123

Post by cvak »

ekianjo wrote: post #109
agileAlligator wrote: post #97

Earlier quoted context omitted.

You can try vim emulation inside vscode, there is an extension for that. https://marketplace.visualstudio.com/items?itemName=vscodevi...

It does not support all vims features.

there's also this: https://github.com/asvetliakov/vscode-neovim

Re: Lazygit: A simple terminal UI for Git commands

#125

Post by ducktective »

smallerfish wrote: post #93
ilaksh wrote: post #54

Earlier quoted context omitted.

I think that it's just difficult to submit updates to Ubuntu or get them incorporated. I think you can just download the binary and put it in /usr/bin or clone and run go install as per the instructions.

That's bad practice though. Devs should be comfortable having older (security patched) versions of software in repos, which provide a valuable service for users. It's hostile for devs to push PPAs only, as it implies that their ability to push updates faster is more important than the distro's review process.

Take the nix pill

Re: Lazygit: A simple terminal UI for Git commands

#126

Post by sharperguy »

brigandish wrote: post #91

> Rant time: You've heard it before, git is powerful, but what good is that power when everything is so damn hard to do? Interactive rebasing requires you to edit a goddamn TODO file in your editor? Are you kidding me? To stage part of a file you need to use a command line program to step through each hunk and if a hunk can't be split down any further but contains code you don't want to stage, you have to edit an arc…

This is the main reason I use "git gui". When I tell people they tend to have the kneejerk reaction "eww you use a gui with git, learn the command line its more powerful and not that hard".

But being able to right-click individual lines of code to stage/unstage them is basically the only thing I use it for, since editing patch files is a pain. The tool is also very lightweight and opens instantly, which would be a reason to switch to something else if it weren't the case.

Re: Lazygit: A simple terminal UI for Git commands

#127

Post by sharperguy »

agilob wrote: post #16
jordanmorgan10 wrote: post #12

If there is one thing that terrifies me it's using Git, or any source control, from the command line. No matter how long I've been in this industry, I just can't get cozy with doing a lot of heavy lifting in any shell environment. Give me the GUI all day every day.

Exactly the opposite for me. I absolutely do not trust GUIs to do the right thing. I don't trust text area to use correct line endings consistently across platforms, I don't trust them to be up to date with new options for `commit` or `checkout`, they never show examples what result will be (--dry-run). None GUI is ever up to date with documentation and contains all functionality which I can autocomplete with [tab][t…

I agree with you, but it does feel strange whenever I do dip into IDEs which have thousands of features built-in to keep you inside the IDE but to then revert back to the command-line to do git stuff. I can imagine for someone who typically uses an IDE, especially if they work on Windows or OSX it would be even weirder.

Re: Lazygit: A simple terminal UI for Git commands

#129

Post by yjftsjthsd-h »

recursive wrote: post #99
BoorishBears wrote: post #30

Earlier quoted context omitted.

The entire point of a GUI is you get the behavior of -p and --dry-run in a much richer context! I've never seen a GUI that doesn't let you very easily select specific lines for commits and I honestly wouldn't use one that didn't. I cannot imagine using git and only being able to push entire files... - And for the record, I use Sublime Merge and it does a great job mapping to terminal commands. Hover over any button a…

I cannot imagine using git and having a reason to commit only half a file. I've known it was possible for several years. But never once has it been a solution to any problem I've had. I suppose we both have limited imaginations.

I know this is covering a mistake, but I've occasionally done one thing, then done a separate thing without committing (especially easy to do with things like one-line version bumps or super trivial bug fixes), then used git commit -p to commit+push the first change while still working on the second change locally. Obviously this only comes up because I suck at task management, but it is a real-life time when the feature is helpful.
Post reply on HN