From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Nicolas Morey-Chaisemartin <devel-git@morey-chaisemartin.com>
Cc: Shawn Pearce <spearce@spearce.org>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH v2] git-completion: Add support for git submodule options
Date: Tue, 12 Apr 2011 11:37:38 +0200 [thread overview]
Message-ID: <20110412093738.GA6817@goldbirke> (raw)
In-Reply-To: <4DA33EC8.5040704@morey-chaisemartin.com>
Hi,
On Mon, Apr 11, 2011 at 07:47:52PM +0200, Nicolas Morey-Chaisemartin wrote:
> Completion for git submodule only handled subcommands.
> Add support for options of each subcommand
>
> Signed-off-by: Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>
> ---
> Changes:
> - Inlined local variables listing options.
>
> contrib/completion/git-completion.bash | 32 +++++++++++++++++++++++++++++++-
> 1 files changed, 31 insertions(+), 1 deletions(-)
This change looks good overall, but I have a few nits, though.
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index 840ae38..20d0cf0 100755
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -2546,7 +2546,8 @@ _git_submodule ()
> __git_has_doubledash && return
>
> local subcommands="add status init update summary foreach sync"
> - if [ -z "$(__git_find_on_cmdline "$subcommands")" ]; then
> + local subcommand="$(__git_find_on_cmdline "$subcommands")"
> + if [ -z "$subcommand" ]; then
> local cur
> _get_comp_words_by_ref -n =: cur
> case "$cur" in
> @@ -2558,6 +2559,35 @@ _git_submodule ()
> ;;
> esac
> return
> + else
> + local cur
> + _get_comp_words_by_ref -n =: cur
Both branches of the if-else statement start with the same
local cur
_get_comp_words_by_ref -n =: cur
so these could be moved out in front of the if statement.
> + case "$subcommand,$cur" in
> + add,--*)
> + __gitcomp "--branch= --force --reference="
> + ;;
> + status,--*)
> + __gitcomp "--cached --recursive"
> + ;;
> + update,--*)
> + __gitcomp "--init --no-fetch --rebase --reference= --merge --recursive"
> + ;;
> + summary,--*)
> + __gitcomp "--cached --files --summary-limit="
> + ;;
> + summary,*)
> + __gitcomp "$(__git_refs)"
> + ;;
> + foreach,--*)
> + __gitcomp "--recursive"
> + ;;
> + sync,*)
> + COMPREPLY=()
> + ;;
> + *)
> + COMPREPLY=()
> + ;;
The 'sync,*' case is not necessary, because it has the same completion
reply as the '*' case, and that case would match it anyway.
And finally, please use tabs for indentation.
Best,
Gábor
prev parent reply other threads:[~2011-04-12 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 17:47 [PATCH v2] git-completion: Add support for git submodule options Nicolas Morey-Chaisemartin
2011-04-11 17:59 ` Jens Lehmann
2011-04-12 9:37 ` SZEDER Gábor [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=20110412093738.GA6817@goldbirke \
--to=szeder@ira.uka.de \
--cc=devel-git@morey-chaisemartin.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.