Git git git git git (opens in new tab)

I do. And I also write "vim vim thefile.txt" and stuff like that.

Finally I've written a small shell function that corrects "gi tpull" to "git pull", because that happens at least once a day.

I often type "git clone ", then switch to a browser to copy/paste the URL, which is usually fine, but there are still many times where I've happened to include "git clone" in the copied string. (So I end up with "git clone git clone $URL").

The one I do is `git clone ` then paste in the repository URL from bitbucket, and end up with `git clone git clone https://....`

I don't think that can be solved here though.

Not this, but I do fairly often think assume I'm in vim when I'm not.

`alias :q="echo NOT IN VIM!!!"`

> Does anyone else actually do this besides OP.

Guilty as charged. I'll commonly start typing git, think about something else, switch to my editor, browser or an other terminal tab, then come back and type "git <command>" in full.

Unsurprisingly…

    > rg 'git =' ~/.gitconfig 
    7:	git = ! git

Something I have noted as part of my venturing into mechanical keyboards lead me to the revelation that many of my "mistakes" were really the keyboard failing me (ie, not properly register my keystrokes). All my life I assume was me the idiot that not know how use it. Only after I pay attention to how I use the keyboard (looking at my hands for a while) I start to see this.

So, I need to more firmly hit the keys in my actual driver (MS Ergo Keyboard) and now building my own mech...

P.D: ie: Maybe one of the different mech switches are more suited to the way YOU type:

http://www.wasdkeyboards.com/mechanical-keyboard-guide

---

P.D 2: This is a reply to all the ones that state that type wrong some commands.

Also, and maybe more common, is just bad typing. I was far worse before the use of the MS Ergo Keyboard (it DEMAND to use both hands.) So, if the performance change by keyboards (happend to me) maybe is a indication that are the tools at fault here..

I totally do this. I also occasionally will have something breaking and soon realize I typed 'git' randomly in the middle of a file instead of in my terminal...

All the time, at least twice already today. Another common command that I'll start typing only to switch context from is vim.

It's usually more "type git in a terminal then open a new tab to look something up and ALT-TAB back to the terminal" rather than a physical going away.

I type `ls ls something` a lot because of this.

As a related issue, it bothers me a lot when I type some command that I want to read the output, and then I proceed to run `ls` right in the sequence and move the output out of the screen.

FWIW, I'm also baffled that this is a problem to solve.

Surprised how many are affirming this. Kind of a DAE moment. My fingers are a bit more tame from having spell check disabled & not falling back on these typo-aliases, as shown by the author's other aliases. Especially their t-prefix aliases which imply zsh aliasing gi to git

I sometimes do, though not specifically with git. Can be emacs, can be ls, can be anything where I interrupt my thought process.

So... I really fail to see why this article is of any relevance at all, really. Or at least a more global solution would have been better, but I think it's not really an annoyance. For me, it's the same as wanting to fix a UI so that I wouldn't re-double-click a software that I've already started (well, some prevent it, and generally when they do, it means there are sessions, and it annoys me).

I do the same with man instead (even though I only used that program like 50 times the last year) … it even happens in any other program where you can input text …

Yup. With lots of commands, not just git.

Leave the computer? No, never.

The author seems to have a lot of issues with spelling.

Everyone is different. I know an electrical engineer who grew up with dyslexia. So everyone finds their own solutions.

Personally I very rarely spell things wrong in cli.

It happens to me when cloning a repo. Sometimes I just write git clone ..., go to browser and the command already contains git clone, then i end up having sth like git clone git clone ...

I do. Everyone has their own tics; one of mine is that.

I do it all the time, but never thought it was the problem. Most often its to look up a reference number for a commit,

Then I get distracted on HN ...

No. I have aliases for most things git:

gs = git status

ga = git add

gc = git commit

gp = git push

gl = git pull

gt = git tag

I do not. I thought the only reason that this was on the front page was because it was funny.

+1, what are you all looking at when typing git over and over again?

Yep. And I did the exact same thing the OP did about it.

Yes, I do this all the time with all sorts of commands.

Sometimes, while copy pasting.

Often, yes.

I do it fairly often.

Yup, I do.

Fish shell like syntax highlighting for zsh: https://github.com/zsh-users/zsh-syntax-highlighting

Fish-like autosuggestions for zsh: https://github.com/zsh-users/zsh-autosuggestions

That's kinda what fish -- the friendly interactive shell - does, but more towards tab autocompletion than error detection.

Fish does this for missing files (though not invalid subcommands): https://fishshell.com/

Hey, don't forget about zsh with a highlighting plugin! :)

Somewhat related, from my .bashrc

  for a in $(git var -l | sed -nE 's/^alias\.([^=]*)=.*/\1/p') ; do
      if ! command -v g$a >/dev/null 2>&1 ; then
          alias g$a="git $a"
      fi
  done

Which creates a shell alias prefixed with `g` for each of my configured git aliases if there is no conflict. So I get not only the `gst` command you mentioned and ones like `gco` (because I have Subversion-equivalent aliases for common commands), but more complex ones like `gstpup` (stash, pull upstream, stash pop). Combined with `alias g=git`, I seldom type "git" and the setup is pretty convenient. I've thought of making the above alias unconditionally, or report conflicts, as it can be jarring when an alias is missing. I've also considered expanding it to all git commands because sometimes my custom ones live as `git-$command` scripts and not aliases.

For me, it's because `gst` will only work on my machine. I like feeling at home on any system, so I'm loathe to depend heavily on aliases and configuration. One of the things I like about git git is that it appears to improve my experience without significantly affecting my habits.

I used to do that, but I found it wasn’t actually saving me any cognitive load.

My newer philosophy toward git aliases is the one described here: http://gggritso.com/human-git-aliases. After reading this I totally overhauled my .gitconfig and replaced it with the one described here and I’m a lot happier.

I've a variety of shell functions/aliases, like "gits" -> "git status -uno", gitd -> git diff, gitds -> git diff --staged, and so on.

I also have a variety of git aliases like:

        ## git log aliases
        #
        # p  -> --patch
        # o  -> --oneline
        # r  -> --reverse
        # s  -> --stat
        # 1  -> -n1
        # m  -> master..
        # om -> origin/master..
        dom     = diff origin/master..
        doom    = diff origin/master..
        rbiom   = rebase -i origin/master
        lp      = log -p
        lo      = log --oneline
        lo1     = log --oneline -n1
        lr      = log --reverse
        lm      = log master..
        lrm     = log --reverse master..
        lor     = log --oneline --reverse
        lorm    = log --oneline --reverse master..
        lorom   = log --oneline --reverse origin/master..
        lom     = log --oneline master..
        loom    = log --oneline origin/master..
        l1      = log -n1
        ...

Why type 'gst'? I use C-x g, which is bound to magit-status:-)

Somewhat more seriously, I haven't had to worry about typing 'git git' because I haven't typed 'git' on a daily basis in years. I think I've probably typed it once in the last month.

The zsh git plugin, and scm_breeze (https://github.com/scmbreeze/scm_breeze), are two of my favorite nice-to-haves for improving the Git experience.

I have alias wow='git status' in my .profile because it's more fun (to me).

I had a senior dev interview with a major company in SV last year where the lead and hiring manager claimed that the description for this behavior was "side-effect free".

I didn't want to ruin my chances by correcting him that side-effects and idempotence refer to different qualities.

I passed the interview, but I've never forgotten that. The guy also seemed to have washed into the interview off his surf board.

Oh well. It was a very major company, so I let it all go.

AKA https://github.com/nvbn/thefuck

Ha! I have almost the same thing:

gi() { ARG=$(echo $1 | sed s/^t//); shift; git "$ARG" "$@"; }

You are right, I checked and the resulting sub-process tree is the same regardless of whether !git or !exec git is used.

Also, I found one caveat from the same docs:

> Note that shell commands will be executed from the top-level directory of a repository, which may not necessarily be the current directory. GIT_PREFIX is set as returned by running git rev-parse --show-prefix from the original current directory.

So, if I have a modified file `bar` in subdirectory `foo` under project root, and I am currently in `foo`, git status will show:

    modified:   bar

but git git status will show:

    modified:   foo/bar

To fix this, we should use cd first:

    git config --global alias.git '!cd "$GIT_PREFIX" && git'

I don't think you are missing anything, good catch.

Exactly. If anything I appreciate when errors are _highlighted_ a la `sl` (Steam locomotive) for `ls` or the `gti` for `git` that has a golf gti run across the screen

That is true given automatic error correction can backfire, I don't see how git git -> git autocorrect can backfire.

Add double quotes around $@.

This isn't too hard. Aliases can expand to arbitrary shell commands, as shown in the article. So you can do something like:

    git config --global alias.bomb '!git bomb & git bomb'

to make a fork bomb.

Author here, I'm glad someone else appreciated it besides me. :-)

(It's especially pleasing to watch the system calls it generates via strace or dtrace!)

I heard Desiigner.. completed the title in my head with "I got broads in Atlanta"

One way around that issue is to prefix commands you intend to share with backslash:

    $ \gstatus
    gstatus: command not found

vs

    $ gstatus
    git status stuff

The backslash just disables alias expansion. This works on all shells I'm aware of. It won't help with other portability concerns like actual missing commands though, of course.

I find writing shell scripts is a different mental process than interacting with the commandline, so I think the problem of “starting a command then leaving the terminal” is non-existant in that context.

I think it was meant as light hearted humor.

Also `alias gti="echo 'vroom vroom'"`

Don't forget "igt".