# [PATCH] bash: complete full refs 4 messages from 2008-11-27 to 2008-11-28. Participants: SZEDER Gábor, Shawn O. Pearce. Thread: https://gitlist.dev/t/16499 ## SZEDER Gábor, 2008-11-27 13:35 Subject: [PATCH] bash: complete full refs Message-ID: <1227792947-4055-1-git-send-email-szeder@ira.uka.de> URL: https://gitlist.dev/e/1227792947-4055-1-git-send-email-szeder%40ira.uka.de ``` Sometimes it's handy to complete full refs, e.g. the user has some refs outside of refs/{heads,remotes,tags} or the user wants to complete some git command's special refs (like 'git show refs/bisect/bad'). To do that, we check whether the ref to be completed starts with 'refs'. If it does, then we offer full refs for completion; otherwise everything works as usual. This way the impact on the common case is fairly small (hopefully not many users have branches or tags starting with 'refs'), and in the special case the cost of typing out 'refs' is bearable. While at it, also remove the unused 'cmd' variable from '__git_refs'. Signed-off-by: SZEDER Gábor --- contrib/completion/git-completion.bash | 19 +++++++++++++++---- 1 files changed, 15 insertions(+), 4 deletions(-) diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash index 0ee071b..39bf18b 100755 --- a/contrib/completion/git-completion.bash +++ b/contrib/completion/git-completion.bash @@ -188,11 +188,22 @@ __git_tags () __git_refs () { - local cmd i is_hash=y dir="$(__gitdir "$1")" + local i is_hash=y dir="$(__gitdir "$1")" + local cur="${COMP_WORDS[COMP_CWORD]}" format refs if [ -d "$dir" ]; then - if [ -e "$dir/HEAD" ]; then echo HEAD; fi - git --git-dir="$dir" for-each-ref --format='%(refname:short)' \ - refs/tags refs/heads refs/remotes + case "$cur" in + refs*) + format="refname" + refs="${cur%/*}" + ;; + *) + if [ -e "$dir/HEAD" ]; then echo HEAD; fi + format="refname:short" + refs="refs/tags refs/heads refs/remotes" + ;; + esac + git --git-dir="$dir" for-each-ref --format="%($format)" \ + $refs return fi for i in $(git ls-remote "$dir" 2>/dev/null); do -- 1.6.0.4.814.gfe502 ``` ## Shawn O. Pearce, 2008-11-27 21:29 Subject: Re: [PATCH] bash: complete full refs Message-ID: <20081127212938.GB23984@spearce.org> URL: https://gitlist.dev/e/20081127212938.GB23984%40spearce.org In-Reply-To: <1227792947-4055-1-git-send-email-szeder@ira.uka.de> ``` SZEDER GGGbor wrote: > Sometimes it's handy to complete full refs, [...] > > To do that, we check whether the ref to be completed starts with > 'refs'. ... > diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash > index 0ee071b..39bf18b 100755 > --- a/contrib/completion/git-completion.bash > +++ b/contrib/completion/git-completion.bash > @@ -188,11 +188,22 @@ __git_tags () > > __git_refs () > { > - local cmd i is_hash=y dir="$(__gitdir "$1")" > + local i is_hash=y dir="$(__gitdir "$1")" > + local cur="${COMP_WORDS[COMP_CWORD]}" format refs > if [ -d "$dir" ]; then > - if [ -e "$dir/HEAD" ]; then echo HEAD; fi > - git --git-dir="$dir" for-each-ref --format='%(refname:short)' \ > - refs/tags refs/heads refs/remotes > + case "$cur" in > + refs*) I wonder if the pattern shouldn't be: refs|refs/*) to reduce the risk of matching "refs-" and trying to do a full ref match instead of a short ref match. Otherwise, Acked-by: Shawn O. Pearce -- Shawn. ``` ## SZEDER Gábor, 2008-11-28 00:46 Subject: [PATCH] bash: complete full refs Message-ID: <20081128004638.GA6854@neumann> URL: https://gitlist.dev/e/20081128004638.GA6854%40neumann In-Reply-To: <20081127212938.GB23984@spearce.org> ``` Sometimes it's handy to complete full refs, e.g. the user has some refs outside of refs/{heads,remotes,tags} or the user wants to complete some git command's special refs (like 'git show refs/bisect/bad'). To do that, we check whether the ref to be completed starts with 'refs/' or is 'refs' (to reduce the risk of matching 'refs-'). If it does, then we offer full refs for completion; otherwise everything works as usual. This way the impact on the common case is fairly small (hopefully not many users have branches or tags starting with 'refs'), and in the special case the cost of typing out 'refs' is bearable. While at it, also remove the unused 'cmd' variable from '__git_refs'. Signed-off-by: SZEDER Gábor --- On Thu, Nov 27, 2008 at 01:29:38PM -0800, Shawn O. Pearce wrote: > I wonder if the pattern shouldn't be: > > refs|refs/*) > > to reduce the risk of matching "refs-" and trying to do a full ref > match instead of a short ref match. Good point. Adjusted the code and commit message accordingly. contrib/completion/git-completion.bash | 19 +++++++++++++++---- 1 files changed, 15 insertions(+), 4 deletions(-) diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash index 0ee071b..244ed41 100755 --- a/contrib/completion/git-completion.bash +++ b/contrib/completion/git-completion.bash @@ -188,11 +188,22 @@ __git_tags () __git_refs () { - local cmd i is_hash=y dir="$(__gitdir "$1")" + local i is_hash=y dir="$(__gitdir "$1")" + local cur="${COMP_WORDS[COMP_CWORD]}" format refs if [ -d "$dir" ]; then - if [ -e "$dir/HEAD" ]; then echo HEAD; fi - git --git-dir="$dir" for-each-ref --format='%(refname:short)' \ - refs/tags refs/heads refs/remotes + case "$cur" in + refs|refs/*) + format="refname" + refs="${cur%/*}" + ;; + *) + if [ -e "$dir/HEAD" ]; then echo HEAD; fi + format="refname:short" + refs="refs/tags refs/heads refs/remotes" + ;; + esac + git --git-dir="$dir" for-each-ref --format="%($format)" \ + $refs return fi for i in $(git ls-remote "$dir" 2>/dev/null); do -- 1.6.0.4.814.gfe502 ``` ## Shawn O. Pearce, 2008-11-28 00:51 Subject: Re: [PATCH] bash: complete full refs Message-ID: <20081128005136.GE23984@spearce.org> URL: https://gitlist.dev/e/20081128005136.GE23984%40spearce.org In-Reply-To: <20081128004638.GA6854@neumann> ``` SZEDER GGGbor wrote: > Sometimes it's handy to complete full refs, e.g. the user has some > refs outside of refs/{heads,remotes,tags} or the user wants to > complete some git command's special refs (like 'git show > refs/bisect/bad'). ... > On Thu, Nov 27, 2008 at 01:29:38PM -0800, Shawn O. Pearce wrote: > > I wonder if the pattern shouldn't be: > > > > refs|refs/*) > > > > to reduce the risk of matching "refs-" and trying to do a full ref > > match instead of a short ref match. > Good point. Adjusted the code and commit message accordingly. Thanks. Acked-by: Shawn O. Pearce > contrib/completion/git-completion.bash | 19 +++++++++++++++---- > 1 files changed, 15 insertions(+), 4 deletions(-) > > diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash > index 0ee071b..244ed41 100755 > --- a/contrib/completion/git-completion.bash > +++ b/contrib/completion/git-completion.bash > @@ -188,11 +188,22 @@ __git_tags () > > __git_refs () > { > - local cmd i is_hash=y dir="$(__gitdir "$1")" > + local i is_hash=y dir="$(__gitdir "$1")" > + local cur="${COMP_WORDS[COMP_CWORD]}" format refs > if [ -d "$dir" ]; then > - if [ -e "$dir/HEAD" ]; then echo HEAD; fi > - git --git-dir="$dir" for-each-ref --format='%(refname:short)' \ > - refs/tags refs/heads refs/remotes > + case "$cur" in > + refs|refs/*) > + format="refname" > + refs="${cur%/*}" > + ;; > + *) > + if [ -e "$dir/HEAD" ]; then echo HEAD; fi > + format="refname:short" > + refs="refs/tags refs/heads refs/remotes" > + ;; > + esac > + git --git-dir="$dir" for-each-ref --format="%($format)" \ > + $refs > return > fi > for i in $(git ls-remote "$dir" 2>/dev/null); do > -- > 1.6.0.4.814.gfe502 > -- Shawn. ```