From: wookietreiber <kizkizzbangbang@googlemail.com>
To: git@vger.kernel.org
Subject: [feature request] git add completion should exclude staged content
Date: Sat, 26 Jan 2013 18:21:37 +0100 [thread overview]
Message-ID: <20130126172137.GB5852@mobster.11n_AP_Router> (raw)
Dear Git Hackers,
I have a feature request for `git add` auto completion:
`git add` auto completion suggests all files / directories, filtered by nothing. I guess it would be
much nicer (as in increasing productivity) if it would only suggest unstaged content, as reported by
`git status`, because that would be the only content one would be able to add.
Example:
$ git status
# On branch develop
# Changes to be committed:
# (use "git reset HEAD <file>..." to unstage)
#
# modified: src/main/scala/XYChart.scala
#
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# notes/0.2.0.markdown
$ git add <auto-complete>
build.sbt .ensime .git/ project/ scalastyle-config.xml todo
COPYING .ensime_lucene/ notes/ README.md src/
$ git add
Where it should be:
$ git add <auto-complete>
$ git add notes/0.2.0.markdown
... because `notes/0.2.0.markdown` is the only thing I can add.
--
Beste Grüße / Best Regards
Christian Krause aka wookietreiber
-----------------------------------------------------------------------
EGAL WIE DICHT DU BIST, GOETHE WAR DICHTER.
next reply other threads:[~2013-01-26 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 17:21 wookietreiber [this message]
2013-01-27 23:00 ` [feature request] git add completion should exclude staged content Junio C Hamano
2013-01-28 9:26 ` Manlio Perillo
2013-01-28 12:52 ` Michael J Gruber
2013-01-28 14:02 ` Manlio Perillo
2013-01-28 16:22 ` Michael J Gruber
2013-01-28 17:52 ` Junio C Hamano
2013-01-28 20:16 ` Manlio Perillo
2013-01-30 14:06 ` Marc Khouzam
2013-01-30 18:24 ` Manlio Perillo
2013-01-30 18:55 ` Marc Khouzam
2013-01-30 19:58 ` Manlio Perillo
2013-01-28 20:13 ` Manlio Perillo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130126172137.GB5852@mobster.11n_AP_Router \
--to=kizkizzbangbang@googlemail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).