Hacker News Reader

Comment by kristjan | Hacker News Reader

But you're still typing `git` every time!

    alias g=git

I've got my Git configs up at https://github.com/kristjan/.dotfiles/blob/master/.gitconfig if you'd like to sift through them. The very most common, like `git status`, get their own Bash aliases too (https://github.com/kristjan/.dotfiles/blob/master/.aliases#L...). Who can be bothered to type a space?

View on HN

Not sure if I'm in the majority or minority here, but I actually prefer that the main command (git in this case) not be shortened. The rest of the options are where I find aliasing to be useful. Only because as the numbers of aliases you use grows, it becomes more likely that you'll overwrite your single-letter aliases.

Certainly everything in moderation - I only give letters to commands I literally type hundreds of times daily. Over the past 10 years, I've accumulated 5:

    b=`bundle exec`, though this is becoming less often used and I may remove it
    d=dotenv to easily wrap a command in environment variables 
        (https://github.com/bkeepers/dotenv)
    g=git
    h=hub (GitHub's extensions to Git)
    j=autojump to move to common directories using just a few characters
        from their name (https://github.com/wting/autojump)

I'm the same way, and along with that I don't use aliases directive in my gitconfig either. I create bash scripts that are named git-* that way I can be more advanced in them without having a crappy experience creating them.

Reply on news.ycombinator.com