On Wed, Sep 26, 2012 at 05:51:19PM -0400, Jeff King wrote:
> This is not a complete fix, as the completion result does
> will still contain metacharacters, so it would need extra
> quoting to actually be used on a command line. But it's
> still a step in the right direction, because:
> [...]
> 2. We don't know yet what the final fix will look like,
> but this is probably the first step towards it. It
> handles quoting on the input side of compgen; the next
> step will likely be handling the quoting on the output
> side of compgen to yield a usable string for the
> command line.
Here is on attempt at that. It seems to work for me, but I know it is
not what bash does internally with:
$ ls
name with spaces
$ cat name<TAB>
Because in bash's internal case, it knows that "name with spaces" is the
real entry (because if you have many entries and double-tab, it shows it
without the quotes), and only later adds the quoting.
So while this works, I'm not sure if it is optimal or if it has any
weird side effects.
-- >8 --
Subject: [PATCH] completion: quote completions we find
If you try to complete a filename with spaces, you might end
up with this:
$ git show HEAD:name<TAB>
$ git show HEAD:name with spaces
which is technically correct, but does not help you, since
the shell will split the words as soon as you hit enter.
Instead, let's quote completions coming out of __gitcomp_nl
to yield:
$ git show HEAD:'name with spaces'
Signed-off-by: Jeff King <p...@peff.net>
---
contrib/completion/git-completion.bash | 23 +++++++++++++++++++++++
t/t9902-completion.sh | 6 +++---
2 files changed, 26 insertions(+), 3 deletions(-)
diff --git a/contrib/completion/git-completion.bash
b/contrib/completion/git-completion.bash
index b0416ea..1fc43f7 100644
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -274,6 +274,29 @@ __gitcomp_nl ()
{
local IFS=$'\n'
COMPREPLY=($(compgen -P "${2-}" -S "${4- }" -W "$(__git_quote "$1")" --
"${3-$cur}"))
+
+ local i
+ for (( i=0; i < ${#COMPREPLY[@]}; i++ )); do
+ # Hack to handle the extra space we add for some
+ # entries, since we use "-o nospace".
+ local stripped
+ case "${COMPREPLY[$i]}" in
+ *\ )
+ stripped=' '
+ COMPREPLY[$i]=${COMPREPLY[$i]% }
+ ;;
+ esac
+
+ # Now we can check if we need actual quoting.
+ case "${COMPREPLY[$i]}" in
+ *[\ \$\'\"\(\)]*)
+ COMPREPLY[$i]="'${COMPREPLY[$i]//\'/\'\\\'\'}'"
+ ;;
+ esac
+
+ # And then restore any stripped space.
+ COMPREPLY[$i]="${COMPREPLY[$i]}$stripped"
+ done
}
__git_heads ()
diff --git a/t/t9902-completion.sh b/t/t9902-completion.sh
index da67705..d2c5104 100755
--- a/t/t9902-completion.sh
+++ b/t/t9902-completion.sh
@@ -274,7 +274,7 @@ test_expect_success 'complete tree filename with spaces' '
git add . &&
git commit -m spaces &&
test_completion_long "git show HEAD:nam" <<-\EOF
- name with spaces_
+ '\''name with spaces'\''_
EOF
'
@@ -283,8 +283,8 @@ test_expect_success 'complete tree filename with
metacharacters' '
git add . &&
git commit -m meta &&
test_completion_long "git show HEAD:nam" <<-\EOF
- name with ${meta}_
- name with spaces_
+ '\''name with ${meta}'\''_
+ '\''name with spaces'\''_
EOF
'
--
1.7.12.10.g31da6dd
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
