Re: Feature request: short cuts for git add /diff etc

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 4, 2012, 18:03 UTC
Message-ID: <7vehmhbr7p.fsf@alter.siamese.dyndns.org>
In-Reply-To: <6110218480.20120904152542@reg.ru>

Коньков Евгений <kes@reg.ru> writes:

Show 29 quoted lines

> # git status
> # On branch yandex_mail_new_api
> # Your branch is ahead of 'origin/yandex_mail_new_api' by 2 commits.
> #
> # Changes not staged for commit:
> #   (use "git add <file>..." to update what will be committed)
> #   (use "git checkout -- <file>..." to discard changes in working directory)
> #
> #       modified(1):   a1.txt
> #       modified(2):   a2.txt
> #
> # Untracked files:
> #   (use "git add <file>..." to include in what will be committed)
> #
> #   (3)    new.txt
>
>
> sot this allow:
> git diff 1       same as        git diff a1.txt
> git diff 2       same as        git diff a2.txt
>
> git add 1        same as        git add a1.txt
> in case there are may be files with such names I may appply option -s,for example
> git add [ -s | --stage ] 1 . This will force to add file from list of
> 'git status' and do not use '1' as file name.
>
> git add 3        same as         git add new.txt
>
> This very handy and will keep developer from useless typing =)

When I know I want to add a1.txt, I can say "git add a1.txt", but with your version of Git, I now have to say "git status" to first find out what file number a1.txt corresponds to so that I can say "git add 1"? Worse yet, after saying "git diff 1" to check the progress of a1.txt, which may be long and scroll the output from "git status" off the top of my screen, I need to run "git status" again to see what file number a2.txt corresponds to?

That does not make any sense even as a typesaver. Besides, what if I have a file whose name is "1" that I would want to add?

You may be looking for either "git gui", or "git add -i" (if you do not like a windowed environment), both of which would let you choose pathnames with fewer keystrokes.