From: Stephen Boyd <bebarino@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: [PATCH 3/3] completion: use specified file (if any) when completing config vars
Date: Wed, 6 May 2009 23:18:13 -0700 [thread overview]
Message-ID: <1241677093-29937-2-git-send-email-bebarino@gmail.com> (raw)
In-Reply-To: <1241677093-29937-1-git-send-email-bebarino@gmail.com>
Only list the variables that can actually be affected by the command by
searching the arguments for a config file setting.
Signed-off-by: Stephen Boyd <bebarino@gmail.com>
---
contrib/completion/git-completion.bash | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index f179cc8..8a9863b 100755
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -1349,7 +1349,10 @@ _git_send_email ()
__git_config_get_set_variables ()
{
- for i in $(git --git-dir="$(__gitdir)" config --list); do
+ local args="--global --system --file= -f"
+ local config_file="$(__git_find_argument_and_value "$args")"
+ for i in $(git --git-dir="$(__gitdir)" config $config_file --list \
+ 2>/dev/null); do
case "$i" in
*.*)
echo "${i/=*/}"
--
1.6.3.rc4.29.g8146
next prev parent reply other threads:[~2009-05-07 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 6:15 [PATCH 1/3] completion: complete config variables for --get/getall/unset/unset-all Stephen Boyd
2009-05-07 6:15 ` [PATCH 2/3] completion: add find_argument_and_value() function Stephen Boyd
2009-05-07 6:18 ` Stephen Boyd
2009-05-07 6:18 ` Stephen Boyd [this message]
2009-05-07 15:12 ` [PATCH 3/3] completion: use specified file (if any) when completing config vars Shawn O. Pearce
2009-05-07 19:55 ` Stephen Boyd
2009-05-09 1:00 ` Stephen Boyd
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=1241677093-29937-2-git-send-email-bebarino@gmail.com \
--to=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.