git sucks

$ git commig -a
git: 'commig' is not a git-command. See 'git --help'.

Did you mean this?
	commit

It knows what I want to do and yet it makes me spell it correctly, just to spite me.

30 thoughts on “git sucks”

  1. On the contrary – it knows what it *thinks* you want to do. And as far as I’m concerned, absolutely the worst thing a computer can do is to try to be helpful and get it wrong. If it can tell I’ve made a mistake, that’s good. But if it thinks it knows what I want to do, I *never* want it to just go ahead and do it. Never, never, never.

  2. I sincerely hope you’re joking. It would be a Very Bad Thing for tools to guess at what commands we meant to type and perform those actions.

    Luckily, after thinking about it, I’m pretty certain you’re joking.

    Sarcasm on the internet is hard, let’s go shopping.

  3. I just unsubscribed from planet.gnome.org thanks to you. I don’t wish to read something this stupid again.

  4. Probably the cause of people thinking you are serious is the fact that there have been some similar posts about git on planet gnome and planet ubuntu recently, featuring the exact same title?

  5. Indeed when there is a single choice, it should ask “Did you mean ‘commit’ (y/N)” — this gives the best solution : it would have both guessed and made sure it really got what you meant.

  6. maybe “man git-config” can help to convince you that git is not inherently evil:

    help.autocorrect
    Automatically correct and execute mistyped commands after waiting for the given number of deciseconds (0.1 sec). If more than one command can be deduced from the entered text, nothing will be executed. If the value of this option is negative, the corrected command will be executed immediately. If the value is 0 – the command will be just shown but not executed. This is the default.

  7. help.autocorrect
    Automatically correct and execute mistyped commands after waiting for the given number of deciseconds (0.1 sec).
    If more than one command can be deduced from the entered text, nothing will be executed. If the value of this
    option is negative, the corrected command will be executed immediately. If the value is 0 – the command will be
    just shown but not executed. This is the default.

  8. Heh. But it actually works:

    $ git config –global help.autocorrect 1
    $ git commig
    WARNING: You called a Git program named ‘commig’, which does not exist.
    Continuing under the assumption that you meant ‘commit’
    in 0.1 seconds automatically…
    […]

  9. When I saw the title in my feed I thought “oh no, here goes another Canonical employee…”.

    When I read the meaty bit, I laughed… hard!

    Nice retort to the rants, IMHO.

  10. With the resent flamewars where people have had worse comments as arguments (yeah, I have seen the “this tool does not read thoughts and therefore sucks – unlike mine that does not read toughts but for which I RTFM”-posts written totally serious) there really should be a sarcasm tag, since on the net it has become hard to tell if people are joking or just plain idiots.

  11. There’s a config option to make it do what you wanted to do πŸ™‚

    help.autocorrect

    Automatically correct and execute mistyped commands after waiting for the given number of deciseconds (0.1 sec). If more than one command can be deduced from the entered text, nothing will be executed. If the value of this option is negative, the corrected command will be executed immediately. If the value is 0 – the command will be just shown but not executed. This is the default.

  12. the sarcasm was clear

    git help config

    help.autocorrect
    Automatically correct and execute mistyped commands after waiting
    for the given number of deciseconds (0.1 sec). If more than one
    command can be deduced from the entered text, nothing will be
    executed. If the value of this option is negative, the corrected
    command will be executed immediately. If the value is 0 – the
    command will be just shown but not executed. This is the default.

  13. Sarcasm on the Internet is *never* obvious enough, you have to explicit state it. Otherwise, there will always be people who believes you to be completely serious.

  14. Wow, I thought this post was pretty funny – I thought there might be some flaming in the comments, but really wasn’t expecting to see people taking it so serious!

  15. they’re almost as funny as xkcd

    They’re only funny about 20% of the time nowadays, and 90% of the people commenting on them don’t actually understand them. So pretty much a perfect analogy for xkcd.

    – Chris

  16. Unless your sarcasm was so completely over the top that nobody could mistake it for anything else, then yes, you did need some kind of disclaimer. You might have been joking, but your post was quite indistinguishable from a great many entirely serious complaints – indeed, is quite innocuous compared to some of the other stupid rants I’ve seen of late.

  17. Your post was funny! Including sarcasm disclaimer spoils the funny! This is well known! So, good job! People need to lighten up! Etcetera!

Leave a Reply to Emilio Pozuelo Monfort Cancel reply

Your email address will not be published. Required fields are marked *