From: Peter Wu <peter@lekensteyn.nl>
To: git@vger.kernel.org
Subject: [PATCH 3/3] completion: handle git -C option
Date: Wed, 28 Oct 2015 18:21:25 +0100 [thread overview]
Message-ID: <1446052885-11173-4-git-send-email-peter@lekensteyn.nl> (raw)
In-Reply-To: <1446052885-11173-1-git-send-email-peter@lekensteyn.nl>
Avoid the "fatal: bad config file line 5 in config" message and properly
complete git commands having the "-C" option.
Besides the trivial command parsing, __gitdir is rewritten to apply any
directory changes requested via `git -C otherdir ...`.
Signed-off-by: Peter Wu <peter@lekensteyn.nl>
---
contrib/completion/git-completion.bash | 45 +++++++++++++++++++++++-----------
1 file changed, 31 insertions(+), 14 deletions(-)
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index fdf0f16..1646f61 100644
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -34,24 +34,39 @@ case "$COMP_WORDBREAKS" in
esac
# __gitdir accepts 0 or 1 arguments (i.e., location)
-# returns location of .git repo
+# outputs location of .git repo if it exists, nothing otherwise.
__gitdir ()
{
- if [ -z "${1-}" ]; then
- if [ -n "${__git_dir-}" ]; then
- echo "$__git_dir"
- elif [ -n "${GIT_DIR-}" ]; then
- test -d "${GIT_DIR-}" || return 1
- echo "$GIT_DIR"
- elif [ -d .git ]; then
- echo .git
+ local gitdir=${1:-}
+
+ if [ -z "$gitdir" ]; then
+ # Try the first matching --git-dir or GIT_DIR, print nothing if these
+ # directories are invalid.
+ for gitdir in "${__git_dir-}" "${GIT_DIR-}"; do
+ [ -n "$gitdir" ] || continue
+ if [[ "$gitdir" != /* ]]; then
+ gitdir="${__git_cd:-.}/$gitdir"
+ fi
+ if [ -d "$gitdir" ]; then
+ echo "$gitdir"
+ fi
+ return
+ done
+
+ if [ -d "${__git_cd:-.}/.git" ]; then
+ echo "${__git_cd:-.}/.git"
else
- git rev-parse --git-dir 2>/dev/null
+ git -C "$__git_cd" rev-parse --git-dir 2>/dev/null
fi
- elif [ -d "$1/.git" ]; then
- echo "$1/.git"
else
- echo "$1"
+ if [[ "$gitdir" != /* ]]; then
+ gitdir="${__git_cd:-.}/$gitdir"
+ fi
+ if [ -d "$gitdir/.git" ]; then
+ echo "$gitdir/.git"
+ elif [ -d "$gitdir" ]; then
+ echo "$gitdir"
+ fi
fi
}
@@ -2566,11 +2581,12 @@ _git_whatchanged ()
__git_main ()
{
- local i c=1 command command_word_index __git_dir __git_options
+ local i c=1 command command_word_index __git_dir __git_options __git_cd=.
while [ $c -lt $cword ]; do
i="${words[c]}"
case "$i" in
+ -C) ((c++)) ; __git_cd="${words[c]}" ;;
--git-dir=*) __git_dir="${i#--git-dir=}" ;;
--git-dir) ((c++)) ; __git_dir="${words[c]}" ;;
--bare) __git_dir="." ;;
@@ -2583,6 +2599,7 @@ __git_main ()
done
__git_options=(
+ -C "$__git_cd"
--git-dir="$(__gitdir)"
)
--
2.6.1
prev parent reply other threads:[~2015-10-28 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 17:21 [PATCH 0/3] bash-completion fixes for global git options handling Peter Wu
2015-10-28 17:21 ` [PATCH 1/3] completion: ignore git options for subcommand completion Peter Wu
2015-10-28 17:21 ` [PATCH 2/3] completion: pass --git-dir to more commands Peter Wu
2015-10-28 17:21 ` Peter Wu [this message]
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=1446052885-11173-4-git-send-email-peter@lekensteyn.nl \
--to=peter@lekensteyn.nl \
--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).