git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v4 3/4] completion: fix branch.autosetup(merge|rebase)

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Jan 5, 2014, 10:18 UTC
Message-ID
<1388917085-18701-4-git-send-email-artagnon@gmail.com>
In-Reply-To
<1388917085-18701-1-git-send-email-artagnon@gmail.com>
When attempting to complete
  $ git config branch.auto<TAB>

'autosetupmerge' and 'autosetuprebase' don't come up. This is because "$cur" is matched with "branch.*" and a list of branches are completed. Add 'autosetupmerge', 'autosetuprebase' as candidates for completion too, using __gitcomp_nl_append ().

Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
 contrib/completion/git-completion.bash | 1 +
 1 file changed, 1 insertion(+)
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index 20febff..a57bcbe 100644
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -1841,6 +1841,7 @@ _git_config ()
 	branch.*)
 		local pfx="${cur%.*}." cur_="${cur#*.}"
 		__gitcomp_nl "$(__git_heads)" "$pfx" "$cur_" "."
+		__gitcomp_nl_append $'autosetupmerge\nautosetuprebase\n' "$pfx" "$cur_"
 		return
 		;;
 	guitool.*.*)
-- 
1.8.5.2.227.g53f3478
Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 4 of 5 in “Re-spin rr/completion-branch-config”
  1. 0/4 Re-spin rr/completion-branch-configRamkumar Ramachandra, Jan 5, 2014
  2. 1/4 zsh completion: find matching custom bash completionRamkumar Ramachandra, Jan 5, 2014
  3. 2/4 completion: introduce __gitcomp_nl_append ()Ramkumar Ramachandra, Jan 5, 2014
  4. 3/4 completion: fix branch.autosetup(merge|rebase)Ramkumar Ramachandra, Jan 5, 2014
  5. 4/4 completion: fix remote.pushdefaultRamkumar Ramachandra, Jan 5, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.