15 comments

[ 0.25 ms ] story [ 4.7 ms ] thread
Do the exec() tail call?
Its a weird feeling to see something posted on here and remembering it being posted nearly 10 years ago

I think of this every time I write git git status

I never have this exact problem.

It's rare that my stale prompt has a "git" in it.

Most of my git commands have mnemonic aliases like "gs", "gd", "gl".

I usually have the problem where a stale "ls" or "vim" inhabits the prompt.

I need one called "gits" that accepts a command "tatus".
And sometimes when I type fast there is "gis tatus"
I’m a bad typist, so it’s ‘hoy’ for me.
> See what other git alias’ I have

This should be "aliases".

Never had this, but I kinda wanna add the alias just in case now
So this is what people do with their spare time.
It's amazing the lengths people go to in order to avoid typing more carefully.
Buffalo Buffalo buffalo Buffalo buffalo?
I recommend also adding this:

   [alias]
     really = !exec git
This solves the common situation where you could’ve sworn you pushed your worl, but colleague can’t find it regardless. You can then `git really push` to be sure.
The exec matters here. Without it each extra git would stack another shell process.