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

Show HN: I made a tool that made me faster at Git

github.com

Post reply on HN
Print view View original

171–180 of 235 posts

Re: Show HN: I made a tool that made me faster at Git

#171

Post by k_ »

hv42 wrote: post #130
jolmg wrote: post #66

> are YOU tired of typing every git command directly into the terminal I'm not. Are there many people that are? Is this not just a matter of learning to use shell keybindings effectively? That and aliases does wonders to avoid repetitive typing. Many times I type `git s` (alias for `git status -s`) out of reflex when I really meant to do `ls`. When I forget to add `-a` to `git ci -m ...` (`ci` being `commit`) and get…

If you editor has a correct git support, you never need to do git status because it will show you which files had been edited since the last commit. Every time I hear people saying how much they prefer the git command line is because they never seriously tried to leverage the git features of their IDE. Vs code with git lens or intellij idea have excellent git integration. Everything is one shortcut away. The git comm…

I only expect my editor to read some information from my git repository. Gutters displaying new/modified hunks and shortcuts to jump to them are pretty much the only things I find useful (for my use; I understand some will find other features helpful).

But any action I want to be made on the repository, I do it myself.

I have some exceptions though, like if I want to revert the hunk I have the cursor on it's nice to be able to revert (or even stage, but I still use `git add --patch` for that) it with one shortcut.

Re: Show HN: I made a tool that made me faster at Git

#172

Post by int_19h »

abhishekjha wrote: post #151
hv42 wrote: post #130

Earlier quoted context omitted.

If you editor has a correct git support, you never need to do git status because it will show you which files had been edited since the last commit. Every time I hear people saying how much they prefer the git command line is because they never seriously tried to leverage the git features of their IDE. Vs code with git lens or intellij idea have excellent git integration. Everything is one shortcut away. The git comm…

I do a git diff after every git status before adding/committing. Do IDEs show diff before committing? Jetbrains IDEs do show diff between subsequent commits. Although they do highlight which files have been modified.

> Do IDEs show diff before committing?

Not as part of the same operation, but the usual workflow is that there's a pane in the somewhere that lists all modified and staged files, and you can click on those to see diffs (or just click "commit" if you don't care).

Re: Show HN: I made a tool that made me faster at Git

#173

Post by danpalmer »

I’ve yet to find a git setup that is more productive (for me at least) than SublimeGit for Sublime Text. The combination of a text based interface with single character shortcuts, and the quick support for staging individual parts of files, means I’m probably twice as fast as the next best thing. It’s the reason I haven’t moved from Sublime to VS Code.

This looks like it could be close, and I’ll definitely give it a try. If I could decouple myself a bit more from Sublime that would be great. The plugin community just isn’t the same as VS Code.

Re: Show HN: I made a tool that made me faster at Git

#174

Post by throwaway0255 »

hv42 wrote: post #130
jolmg wrote: post #66

> are YOU tired of typing every git command directly into the terminal I'm not. Are there many people that are? Is this not just a matter of learning to use shell keybindings effectively? That and aliases does wonders to avoid repetitive typing. Many times I type `git s` (alias for `git status -s`) out of reflex when I really meant to do `ls`. When I forget to add `-a` to `git ci -m ...` (`ci` being `commit`) and get…

If you editor has a correct git support, you never need to do git status because it will show you which files had been edited since the last commit. Every time I hear people saying how much they prefer the git command line is because they never seriously tried to leverage the git features of their IDE. Vs code with git lens or intellij idea have excellent git integration. Everything is one shortcut away. The git comm…

> Every time I hear people saying how much they prefer the git command line is because they never seriously tried to leverage the git features of their IDE.

I think this statement is much more powerful in reverse. People who prefer the git features of their IDE have probably never seriously tried to leverage the features of git...

I prefer the git command line. It supports every single feature of git, and as an interface it’s completely and totally frictionless.

People trying to create tools and UX around git usually do so under the false impression that git is the source of friction, when really they are.

> Also if you ever try to teach someone git, it's not as intuitive as you think [1]. Having a consistent UX can help.

Are there people who need this kind of help learning, but then go on to do well at it?

I’ve found programming in general is extremely binary. Either you’re the kind of person that can grasp it and has the motivation to track down answers yourself and hack away, or you aren’t.

Being able to pick up a new system or technology and understand it very quickly is what it means to be a programmer, even more so than the act of programming itself in my opinion. I think trying to find shortcuts around that to teach people is a bit of a catch-22.

Re: Show HN: I made a tool that made me faster at Git

#175

Post by kungtotte »

cup-of-tea wrote: post #161
kungtotte wrote: post #110

Earlier quoted context omitted.

Whenever I read a comment or blog post about Emacs I'm like "I should definitely try it out, because that sounds awesome", then I do try it and it turns out it's a pain in the ass to make it work on Windows and I spend more time fiddling with it than I do working with it. It's the same thing with vim for that matter. A basic-ish text editor setup is trivial in both editors but beyond that things start to fall apart.…

> I think that's why VSCode has gained so much traction. For coding it's got easily 90% of the same features as both vim and Emacs Is that a joke? How can you possibly know this if you haven't used emacs for a start. Do you really think it has 90% of the features of a 35 year old project? If emacs is difficult to set up on Windows you should stop using it. The awesome stuff you hear about is mostly the result of usin…

I have used vim for god knows who long, and I've tried Emacs several times for a few months at a time before giving up. So I do think that for coding VSCode absolutely has 90% of the features that both vim and emacs offer. Note how I said "for coding"? That's not an accidental or trivial part of my comment. For writing and managing code the feature-sets are on par in all three for sure and if you disagree then I am going to suggest to you that you actually give all three a try and focus only on coding and you'll see what I mean.

I should stop using Windows because a single application is difficult to set up? Throw out my entire OS with the plethora of other applications I use because a single application that has had 35 years to get its shit together simply won't work well? That's a reasonable position for sure!

Developing on Windows works absolutely fine, and if you wan't to talk about prisons and what "Microsoft lets me have" how about we talk about the WSL? They have no reason to include it in Windows but they do. A whole bunch of Linux software became available over night in a native Windows environment because of something Microsoft did. The ones who are digging their heels in at this point are all the *nix developers who refuse to support Windows as a first-class platform, so talk about being in a prison! Your software only works well on a subset of all operating systems.

Re: Show HN: I made a tool that made me faster at Git

#177

Post by weitzj »

pandler wrote: post #42

Awesome work OP! I’m a big fan of using tools like this to supplement git, especially when it comes to some of the more complex operations. Personally I use tig, which is basically this but different. I used to use Sourcetree and I loved it but it slowed to a crawl with bigger projects with long histories. https://github.com/jonas/tig Best screenshots I can find on google are ironically from the Atlassian blog: https…

I use tig as well but I am currently experimenting with FZF and some gitconfig aliases.

Re: Show HN: I made a tool that made me faster at Git

#178

Post by iwwr »

pjc50 wrote: post #176

You know what would make me faster at git? "git undo" : undo the last git command line, whatever it did. Especially if you don't understand what it did or it overwrote local files.

You could store your git refs in another git repo and take a snapshot of those after each command that changes things.

Re: Show HN: I made a tool that made me faster at Git

#180

Post by lgas »

pjc50 wrote: post #176

You know what would make me faster at git? "git undo" : undo the last git command line, whatever it did. Especially if you don't understand what it did or it overwrote local files.

https://github.com/tj/git-extras provides "git undo" (among others).
Post reply on HN