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

Post by earenndil » Sun, Aug 05, 2018, 6:30 AM UTC

kungtotte wrote: post #118

mateuszf wrote: post #113

Earlier quoted context omitted.

Just change your OS?

I think it kind of proves my point when the solution to not being able to set an editor up is to change your entire OS... (Also: no)

Post by john2x » Sun, Aug 05, 2018, 6:35 AM UTC

yellowapple wrote: post #126

dmortin wrote: post #124

Earlier quoted context omitted.

If you status, commit, diff often then you don't want to leave your editor, because every little things (switching to a terminal just to do git stuff) adds up in the long run. Version control functions should be available right in your editor (e.g. magit) and you can't really beat one character hotkeys for version control stuff. It doesn't get more convenient than that.

Seconding the in-editor approach. Magit is wonderful (though I often do end up heading to the command-line for certain things out of habit).

Post by remar » Sun, Aug 05, 2018, 6:42 AM UTC

hyperpallium wrote: post #125

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…

What is ` kF-aa `?

    # x| = cursor is in insert mode, after char 'x'
    # |x| = cursor is in command mode, on char 'x'
    # () = keystrokes entered resulting in prompt on next line

    $ git ci -m ""|    ()
    $ |                     (k)    # puts shell prompt into command mode () and cycles upwards to previous command (k)
    $ git ci -m "|"|   (F-)        # from current position, reverse search (F) and stop on first occurence of '-'
    $ git ci |-|m ""   (aa)        # cursor is on '-' char, append (a) 'a', i.e. transition into insert mode by advancing cursor after current char, then insert 'a' literally
    $ git ci -a|m ""   ()      # execute command
    $ |

Post by h1d » Sun, Aug 05, 2018, 7:00 AM UTC

jordigh wrote: post #44

stockkid wrote: post #21

Personally I have been typing all git commands manually into the terminal and never felt a need for GUIs or tools such as this. There are a number of git shortcuts defined in my zsh aliases [0]. It goes like: # Git aliases alias g='git' alias ga='git add' alias ghb='git browse' # hub alias ghpr='git pull-request' # hub alias gp='git push' alias gpoh='git push origin HEAD' ... Using these aliases, we rarely have to ty…

With Mercurial, I like that all commands can be abbreviated to their shortest unique prefix, plus some built-in aliases. So I type a lot of `hg up`, `hg pus`, `hg ci`, `hg pul`, `hg bo`, and so forth. Most of these are almost the same length as your aliases. Whenever I have to touch git and `git co` doesn't work, I think, okay, fine, we'll go through the full dress rehearsal; `git checkout` it is.

Post by kelnage » Sun, Aug 05, 2018, 7:04 AM UTC

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…