40 points | by alexmolas an hour ago
14 comments
I need one called "gits" that accepts a command "tatus".
And sometimes when I type fast there is "gis tatus"
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 recommend also adding this:
[alias] really = !exec git
Buffalo Buffalo buffalo Buffalo buffalo?
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
Never had this, but I kinda wanna add the alias just in case now
> See what other git alias’ I have
This should be "aliases".
Would it work with "giggity" too?
Do the exec() tail call?
Exec replaces the current process, so yes[1].
[1]: Unless git is doing fork()+exec() and then waiting for the exit code.
It's amazing the lengths people go to in order to avoid typing more carefully.
“Never make a typo” is not a reasonable expectation for a human user
So this is what people do with their spare time.
I need one called "gits" that accepts a command "tatus".
And sometimes when I type fast there is "gis tatus"
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 recommend also adding this:
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.Buffalo Buffalo buffalo Buffalo buffalo?
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
Never had this, but I kinda wanna add the alias just in case now
> See what other git alias’ I have
This should be "aliases".
Would it work with "giggity" too?
Do the exec() tail call?
Exec replaces the current process, so yes[1].
[1]: Unless git is doing fork()+exec() and then waiting for the exit code.
It's amazing the lengths people go to in order to avoid typing more carefully.
“Never make a typo” is not a reasonable expectation for a human user
So this is what people do with their spare time.