Add support for 'git remote rm' in Bash completion script
PATCH 1/1 Add support for 'git remote rm' in Bash completion script
--- contrib/completion/git-completion.bash | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
contrib/completion/git-completion.bash +4 -1
@@ -2334,7 +2334,7 @@ _git_remote () { local subcommands=" add rename remove set-head set-branches - get-url set-url show prune update + get-url set-url show prune rm update " local subcommand="$(__git_find_on_cmdline "$subcommands")" if [ -z "$subcommand" ]; then
@@ -2379,6 +2379,9 @@ _git_remote () prune,--*) __gitcomp_builtin remote_prune ;; + rm,--*) + __gitcomp_builtin remote_rm + ;; *) __gitcomp_nl "$(__git_remotes)" ;;
Signature · 1 line
2.20.1.windows.1
Hi Sergey,
There was a previous discussion of this in December 2017, which might be useful:
It didn't end with a patch applied, but it's likely worth reading to help you make a case for a similar patch.
One of the points in that thread is that the rm subcommand is not shown in completion intentionally, as the preferred subcommand is remove. But it should be possible to offer completion of the remotes after a user types rm, which I imagine is the more helpful part of the completion.
Also, you'll want to add a signoff to the patch if/when you resend it (refer to Documentation/SubmittingPatches, if you haven't already).
Quoted 9 lines · Sergey Zolotarev
--- contrib/completion/git-completion.bash | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)contrib/completion/git-completion.bash +0
-0
contrib/completion/git-completion.bash _git_remote () · line 2339
Quoted 7 lines
contrib/completion/git-completion.bash +1
-1@@ -2334,7 +2334,7 @@ _git_remote () { local subcommands=" add rename remove set-head set-branches - get-url set-url show prune update + get-url set-url show prune rm update " local subcommand="$(__git_find_on_cmdline "$subcommands")"
So instead of this change you could adjust the subcommand line, something like:
- local subcommand="$(__git_find_on_cmdline "$subcommands")"
+ # Don't advertise rm by including it in subcommands, but complete
+ # remotes if it is used.
+ local subcommand="$(__git_find_on_cmdline "$subcommands rm")"
I haven't test that, but the code looks like it hasn't changed since the last time we talked about this -- when I did test the suggestion :).
contrib/completion/git-completion.bash _git_remote () · line 2387
Quoted 11 lines
contrib/completion/git-completion.bash +3
-0if [ -z "$subcommand" ]; then@@ -2379,6 +2379,9 @@ _git_remote () prune,--*) __gitcomp_builtin remote_prune ;; + rm,--*) + __gitcomp_builtin remote_rm + ;; *) __gitcomp_nl "$(__git_remotes)" ;;
I don't think you need this chunk, do you? I think that's only useful for completing options to the subcommand, which 'git remote rm' lacks.
I believe you can simply skip it and let the case fall through to the last item which simply completes the available remotes, just as 'git remote remove' does.
Hope that helps,
Signature · 1 line
Todd
It would be great if we could land this. Non of the other solutions since I proposed my patch have happened, so in the meantime this would be nice to have.
--
Keith Smiley
Quoted 76 lines · Todd Zullinger
Hi Sergey,
There was a previous discussion of this in December 2017, which might be useful:
It didn't end with a patch applied, but it's likely worth reading to help you make a case for a similar patch.
One of the points in that thread is that the rm subcommand is not shown in completion intentionally, as the preferred subcommand is remove. But it should be possible to offer completion of the remotes after a user types rm, which I imagine is the more helpful part of the completion.
Also, you'll want to add a signoff to the patch if/when you resend it (refer to
Documentation/SubmittingPatches, if you haven't already).Quoted 9 lines · Sergey Zolotarev
---
contrib/completion/git-completion.bash | 5 ++++-1 file changed, 4 insertions(+), 1 deletion(-)contrib/completion/git-completion.bash +0
-0contrib/completion/git-completion.bash _git_remote () · line 2339
Quoted 7 lines
contrib/completion/git-completion.bash +1
-1@@ -2334,7 +2334,7 @@ _git_remote () { local subcommands=" add rename remove set-head set-branches - get-url set-url show prune update + get-url set-url show prune rm update " local subcommand="$(__git_find_on_cmdline "$subcommands")"So instead of this change you could adjust the subcommand line, something like:
(quoted diff) +3
-1- local subcommand="$(__git_find_on_cmdline "$subcommands")" + # Don't advertise rm by including it in subcommands, but complete + # remotes if it is used. + local subcommand="$(__git_find_on_cmdline "$subcommands rm")"I haven't test that, but the code looks like it hasn't changed since the last time we talked about this -- when I did test the suggestion :).
contrib/completion/git-completion.bash _git_remote () · line 2387
Quoted 11 lines
contrib/completion/git-completion.bash +3
-0if [ -z "$subcommand" ]; then@@ -2379,6 +2379,9 @@ _git_remote () prune,--*) __gitcomp_builtin remote_prune ;; + rm,--*) + __gitcomp_builtin remote_rm + ;; *) __gitcomp_nl "$(__git_remotes)" ;;I don't think you need this chunk, do you? I think that's only useful for completing options to the subcommand, which 'git remote rm' lacks.
I believe you can simply skip it and let the case fall through to the last item which simply completes the available remotes, just as 'git remote remove' does.
Hope that helps,
Signature · 1 line
Todd
Hi,
Quoted 72 lines · Keith Smiley
Quoted 72 lines · Todd Zullinger
Hi Sergey,
There was a previous discussion of this in December 2017, which might be useful:
It didn't end with a patch applied, but it's likely worth reading to help you make a case for a similar patch.
One of the points in that thread is that the rm subcommand is not shown in completion intentionally, as the preferred subcommand is remove. But it should be possible to offer completion of the remotes after a user types rm, which I imagine is the more helpful part of the completion.
Also, you'll want to add a signoff to the patch if/when you resend it (refer to
Documentation/SubmittingPatches, if you haven't already).Quoted 9 lines · Sergey Zolotarev
---
contrib/completion/git-completion.bash | 5 ++++-1 file changed, 4 insertions(+), 1 deletion(-)contrib/completion/git-completion.bash +0
-0contrib/completion/git-completion.bash _git_remote () · line 2339
Quoted 7 lines
contrib/completion/git-completion.bash +1
-1@@ -2334,7 +2334,7 @@ _git_remote () { local subcommands=" add rename remove set-head set-branches - get-url set-url show prune update + get-url set-url show prune rm update " local subcommand="$(__git_find_on_cmdline "$subcommands")"So instead of this change you could adjust the subcommand line, something like:
(quoted diff) +3
-1- local subcommand="$(__git_find_on_cmdline "$subcommands")" + # Don't advertise rm by including it in subcommands, but complete + # remotes if it is used. + local subcommand="$(__git_find_on_cmdline "$subcommands rm")"I haven't test that, but the code looks like it hasn't changed since the last time we talked about this -- when I did test the suggestion :).
contrib/completion/git-completion.bash _git_remote () · line 2387
Quoted 11 lines
contrib/completion/git-completion.bash +3
-0if [ -z "$subcommand" ]; then@@ -2379,6 +2379,9 @@ _git_remote () prune,--*) __gitcomp_builtin remote_prune ;; + rm,--*) + __gitcomp_builtin remote_rm + ;; *) __gitcomp_nl "$(__git_remotes)" ;;I don't think you need this chunk, do you? I think that's only useful for completing options to the subcommand, which 'git remote rm' lacks.
I believe you can simply skip it and let the case fall through to the last item which simply completes the available remotes, just as 'git remote remove' does.
Quoted 5 lines
Quoted 2 lines
Hope that helps,
It would be great if we could land this. Non of the other solutions since I proposed my patch have happened, so in the meantime this would be nice to have.
Yeah, it seems like we should either complete the remotes for 'git remote rm <tab>' or follow up with the removal of the rm subcommand as Duy and Junio fleshed out in the thread from July. If the command were to be removed, doing it right after the 2.22 cycle begins would be as good a time as any.
If the command remains, here's a suggestion for how it might be submitted (perhaps with more details in the commit to justify why we're completing arguments to a deprecated subcommand?).
It's really not an itch of mine, so I'm just tossing this out in case someone that wants it more will push it forward.
---- >8 ----
Subject: [PATCH] completion: complete remotes for 'remote rm'
The remote 'rm' subcommand was removed from the completed subcommands list in e17dba8fe1 ("remote: prefer subcommand name 'remove' to 'rm'", 2012-09-06). While we don't advertise it, we can still complete the list of remotes for users who type 'git remote rm <tab>' as a courtesy.
--- contrib/completion/git-completion.bash | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
contrib/completion/git-completion.bash +3 -1
@@ -2336,7 +2336,9 @@ _git_remote () add rename remove set-head set-branches get-url set-url show prune update " - local subcommand="$(__git_find_on_cmdline "$subcommands")" + # We don't advertise rm by including it in subcommands, but if it is + # used we want to complete remotes. + local subcommand="$(__git_find_on_cmdline "$subcommands rm")" if [ -z "$subcommand" ]; then case "$cur" in --*)
Signature · 1 line
Todd