completion: improve doc for complex aliases
The completion code can be told to use a particular completion for aliases that shell out by using ': git <cmd> ;' as the first command of the alias. This only works if <cmd> and the semicolon are separated by a space, since if the space is missing __git_aliased_command returns (for example) 'checkout;' instead of just 'checkout', and then __git_complete_command fails to find a completion for 'checkout;'. The examples have that space but it's not clear if it's just for style or if it's mandatory. Explicitly mention it. Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Philippe Blain committed
Sep 12, 2023 at 17:02 UTC
4333267995662ccc9f4db3b628eebb78599e0025
1 file changed
+1
contrib/completion/git-completion.bash
+1
@@ -28,6 +28,7 @@
28
# completion style. For example '!f() { : git commit ; ... }; f' will
29
# tell the completion to use commit completion. This also works with aliases
30
# of form "!sh -c '...'". For example, "!sh -c ': git commit ; ... '".
31
+# Be sure to add a space between the command name and the ';'.
32
#
33
# If you have a command that is not part of git, but you would still
34
# like completion, you can use __git_complete: