From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] completion: fix completion of certain aliases
Date: Fri, 13 Dec 2013 15:16:24 +0100 [thread overview]
Message-ID: <20131213141624.GA28369@goldbirke> (raw)
In-Reply-To: <1386421873-27863-1-git-send-email-felipe.contreras@gmail.com>
Hi,
On Sat, Dec 07, 2013 at 07:11:13AM -0600, Felipe Contreras wrote:
> Some commands need the first word to determine the actual action that is
> being executed, however, the command is wrong when we use an alias,
This first sentence was hard to understand for me because of the wrong
terminology used. How about this instead:
Some completion helper functions need to know the name of the git
command to act properly. However, ...
> for
> example 'alias.p=push', if we try to complete 'git p origin ', the
> result would be wrong because __git_complete_remote_or_refspec() doesn't
> know where it come from.
Are there other helper functions that are affected? After a quick
glance I didn't find any. In this case we could even write the above
as
The __git_complete_remote_or_refspec() completion helper function
needs to know ...
> So let's override words[1], so the alias 'p' is override by the actual
> command, 'push'.
words[1] is not always the name of the git command, it can also be an
option to the main git command, e.g. in case of 'git -c key=value push
...' with this patch '-c' would be overwritten.
Best,
Gábor
> Reported-by: Aymeric Beaumet <aymeric.beaumet@gmail.com>
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> ---
> contrib/completion/git-completion.bash | 1 +
> contrib/completion/git-completion.zsh | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index dba3c15..c14bac4 100644
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -2530,6 +2530,7 @@ __git_main ()
>
> local expansion=$(__git_aliased_command "$command")
> if [ -n "$expansion" ]; then
> + words[1]=$expansion
> completion_func="_git_${expansion//-/_}"
> declare -f $completion_func >/dev/null && $completion_func
> fi
> diff --git a/contrib/completion/git-completion.zsh b/contrib/completion/git-completion.zsh
> index fac5e71..3eeb7f8 100644
> --- a/contrib/completion/git-completion.zsh
> +++ b/contrib/completion/git-completion.zsh
> @@ -96,6 +96,7 @@ __git_zsh_bash_func ()
>
> local expansion=$(__git_aliased_command "$command")
> if [ -n "$expansion" ]; then
> + words[1]=$expansion
> completion_func="_git_${expansion//-/_}"
> declare -f $completion_func >/dev/null && $completion_func
> fi
> --
> 1.8.4.2+fc1
>
>
prev parent reply other threads:[~2013-12-13 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 13:11 [PATCH] completion: fix completion of certain aliases Felipe Contreras
2013-12-13 14:16 ` 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=20131213141624.GA28369@goldbirke \
--to=szeder@ira.uka.de \
--cc=felipe.contreras@gmail.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).