{"thread":{"id":"40034","subject":"feature request: better support for typos","startedAt":"2015-08-07T18:12:10Z","lastAt":"2015-08-16T07:19:48Z","messageCount":3,"participants":["Ralf Thielow","Duy Nguyen","Lawrence Siebert"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"267623","messageId":"CAN0XMOLDamBeWswDi0cn_naZ2TX+gd89+g48zNwPPKxTh+ZTww@mail.gmail.com","threadId":"40034","inReplyTo":null,"subject":"feature request: better support for typos","fromName":"Ralf Thielow","fromEmail":"ralf.thielow@gmail.com","sentAt":"2015-08-07T18:12:10Z","receivedAt":"2015-08-07T18:12:10Z","isPatch":false,"sender":{"key":"ralf.thielow@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1275832?v=4"},"body":"Hi,\n\nwhen a user made a typo, Git is not good in guessing what\nthe user could have meant, except for git commands. I think\nthis is an area with room for improvements.\nLet's look into branches. When I \"clone --branch\" and make\na typo, Git could show me what branch I could have meant. It's\nthe same when I try to merge or track a branch. It might even\nbe possible to show suggestions for options for all Git commands.\nWhat I'm trying to say is, there are arguments with a limited\namount of possible values that Git know, so Git can show\nsuggestions when the user made a typo for such an argument.\n\nRalf\n"},{"id":"268121","messageId":"CACsJy8DGUo0-zFm2xtAKE6wy0c2GdbiOe-X2+B0HnCNg3SKa8g@mail.gmail.com","threadId":"40034","inReplyTo":"CAN0XMOLDamBeWswDi0cn_naZ2TX+gd89+g48zNwPPKxTh+ZTww@mail.gmail.com","subject":"Re: feature request: better support for typos","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2015-08-15T09:12:37Z","receivedAt":"2015-08-15T09:12:37Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Sat, Aug 8, 2015 at 1:12 AM, Ralf Thielow wrote:\n> Hi,\n>\n> when a user made a typo, Git is not good in guessing what\n> the user could have meant, except for git commands. I think\n> this is an area with room for improvements.\n> Let's look into branches. When I \"clone --branch\" and make\n> a typo, Git could show me what branch I could have meant. It's\n> the same when I try to merge or track a branch.\n\nGood candidate for those micro-projects next year.\n\n> It might even\n> be possible to show suggestions for options for all Git commands.\n\nYou mean if you type \"--brnch\" it should suggest \"--branch\"? I was\nbugged about this and wanted to do something, only to realize in most\ncases git would show \"git -h\", which does a much better job\nbecause it would explain what --branch is for as well.\n\n> What I'm trying to say is, there are arguments with a limited\n> amount of possible values that Git know, so Git can show\n> suggestions when the user made a typo for such an argument.\n-- \nDuy\n"},{"id":"268145","messageId":"CAKDoJU7qx7xuzc5X4zJE6-9wvr9dB_h-_u0gYZN9p7ORK-u_mw@mail.gmail.com","threadId":"40034","inReplyTo":"CACsJy8DGUo0-zFm2xtAKE6wy0c2GdbiOe-X2+B0HnCNg3SKa8g@mail.gmail.com","subject":"Re: feature request: better support for typos","fromName":"Lawrence Siebert","fromEmail":"lawrencesiebert@gmail.com","sentAt":"2015-08-16T07:19:48Z","receivedAt":"2015-08-16T07:19:48Z","isPatch":false,"sender":{"key":"lawrencesiebert@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45034?v=4"},"body":"I believe They mean that if you type \"clone --branch mister\", it\nshould ask if you meant to \"clone --branch master\" instead, or\nsomething.\n\nBasically if you type a non existent branch name, calculate edit\ndistance for each branch name, probably either using a timeout or edit\ndistance to stop if something is too different from any branch so you\ndon't run for too long, and then, if a branch is within a certain edit\ndistance from the typo, suggest it.\n\nLawrence\n\nOn Sat, Aug 15, 2015 at 2:12 AM, Duy Nguyen wrote:\n> On Sat, Aug 8, 2015 at 1:12 AM, Ralf Thielow wrote:\n>> Hi,\n>>\n>> when a user made a typo, Git is not good in guessing what\n>> the user could have meant, except for git commands. I think\n>> this is an area with room for improvements.\n>> Let's look into branches. When I \"clone --branch\" and make\n>> a typo, Git could show me what branch I could have meant. It's\n>> the same when I try to merge or track a branch.\n>\n> Good candidate for those micro-projects next year.\n>\n>> It might even\n>> be possible to show suggestions for options for all Git commands.\n>\n> You mean if you type \"--brnch\" it should suggest \"--branch\"? I was\n> bugged about this and wanted to do something, only to realize in most\n> cases git would show \"git -h\", which does a much better job\n> because it would explain what --branch is for as well.\n>\n>> What I'm trying to say is, there are arguments with a limited\n>> amount of possible values that Git know, so Git can show\n>> suggestions when the user made a typo for such an argument.\n> --\n> Duy\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\n\n\n\n-- \nAbout Me: http://about.me/lawrencesiebert\nConstantly Coding: http://constantcoding.blogspot.com\n"}]}