git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: feature request: better support for typos

From
Duy Nguyen <pclouds@gmail.com>
Date
Aug 15, 2015, 09:12 UTC
Message-ID
<CACsJy8DGUo0-zFm2xtAKE6wy0c2GdbiOe-X2+B0HnCNg3SKa8g@mail.gmail.com>
In-Reply-To
<CAN0XMOLDamBeWswDi0cn_naZ2TX+gd89+g48zNwPPKxTh+ZTww@mail.gmail.com>
On Sat, Aug 8, 2015 at 1:12 AM, Ralf Thielow <ralf.thielow@gmail.com> wrote:
Show 8 quoted lines
> Hi,
>
> when a user made a typo, Git is not good in guessing what
> the user could have meant, except for git commands. I think
> this is an area with room for improvements.
> Let's look into branches. When I "clone --branch" and make
> a typo, Git could show me what branch I could have meant. It's
> the same when I try to merge or track a branch.
Good candidate for those micro-projects next year.
> It might even
> be possible to show suggestions for options for all Git commands.

You mean if you type "--brnch" it should suggest "--branch"? I was bugged about this and wanted to do something, only to realize in most cases git would show "git <cmd> -h", which does a much better job because it would explain what --branch is for as well.

> What I'm trying to say is, there are arguments with a limited
> amount of possible values that Git know, so Git can show
> suggestions when the user made a typo for such an argument.
-- 
Duy
Previous: Ralf ThielowNext: Lawrence Siebert
Message 2 of 3 in “feature request: better support for typos”
  1. Ralf ThielowAug 7, 2015
  2. Duy NguyenAug 15, 2015
  3. Lawrence SiebertAug 16, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.