{"thread":{"id":"49178","subject":"Feature request: detecting mistyped command and isdentical possible matches","startedAt":"2018-08-21T13:02:02Z","lastAt":"2018-08-21T13:02:02Z","messageCount":1,"participants":["Erik Huizinga"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"356167","messageId":"CADA507y8NAgN_v2-cxdWYZEvGUgzxFbFD52KmdyynWr6MufvRA@mail.gmail.com","threadId":"49178","inReplyTo":null,"subject":"Feature request: detecting mistyped command and isdentical possible matches","fromName":"Erik Huizinga","fromEmail":"huizinga.erik@gmail.com","sentAt":"2018-08-21T13:01:48Z","receivedAt":"2018-08-21T13:02:02Z","isPatch":false,"sender":{"key":"huizinga.erik@gmail.com","avatar":null},"body":"Hi!\n\nI have an alias for 'git status': 'git st'. I also have configured\nthat an unrecognised (mistyped) Git command runs the closest match. In\nthis case I did the following:\n\n'''\n$ git stt\ngit: 'stt' is not a git command. See 'git --help'.\n\nThe most similar commands are\n  st\n  status\n'''\n\nIn this particular case it would have been nice if Git also understood\nthat 'git st' and 'git status' are equivalent in my configuration, so\nthat it shouldn't have to warn me about them as different matches, but\ninstead just run any of them.\n\nThank you for Git. Maybe I'll see this feature in the future!\n\nBest,\nErik\n"}]}