Ever found you’ve accidentally entered too many gits in your terminal and wondered if there’s a solution to it? I quite often type git then go away and come back, then type a full git status after it. This leads to a lovely (annoying) error out the box: $ git git status git: 'git' is not a git command. See 'git --help'. What a git. My initial thought was overriding the git binary in my $PATH and having it strip any leading arguments that match git, so we end up running just the git status at the end of the arguments.
  • graynk@discuss.tchncs.deEnglish
    31·
    3 days ago

    Ever found you’ve accidentally entered too many gits in your terminal

    No. Not once. In fact, I barely type git into the terminal at all these days and I think CLI is the worst possible way to interact with git repos in majority of cases

    • JakenVeina@midwest.socialEnglish
      1·
      3 days ago

      Agreed.

      It also strikes me that, while it’s mildly funny that they were able to make this work… it can’t POSSIBLY be worth the effort it took, however minimal, to make this work, just to avoid the handful of seconds in a day that you might save by not having to just re-do the typo’d commands. And yet, this is presented as a completely serious fix for an issue.

      Posts like these make me feel like people who use primarily CLI tools live in a different reality than the rest of us.