Skip to content

Commit d35a743

Browse files
ianwgitster
authored andcommitted
Documentation: alias: add notes on shell expansion
When writing inline shell for shell-expansion aliases (i.e. prefixed with "!"), there are some caveats around argument parsing to be aware of. This series of notes attempts to explain what is happening more clearly. Signed-off-by: Ian Wienand <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 174443e commit d35a743

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

Documentation/config/alias.txt

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,3 +27,17 @@ it will be treated as a shell command. For example, defining
2727
repository, which may not necessarily be the current directory.
2828
* `GIT_PREFIX` is set as returned by running `git rev-parse --show-prefix`
2929
from the original current directory. See linkgit:git-rev-parse[1].
30+
* Shell command aliases always receive any extra arguments provided to
31+
the Git command-line as positional arguments.
32+
** Care should be taken if your shell alias is a "one-liner" script
33+
with multiple commands (e.g. in a pipeline), references multiple
34+
arguments, or is otherwise not able to handle positional arguments
35+
added at the end. For example: `alias.cmd = "!echo $1 | grep $2"`
36+
called as `git cmd 1 2` will be executed as 'echo $1 | grep $2
37+
1 2', which is not what you want.
38+
** A convenient way to deal with this is to write your script
39+
operations in an inline function that is then called with any
40+
arguments from the command-line. For example `alias.cmd = "!c() {
41+
echo $1 | grep $2 ; }; c" will correctly execute the prior example.
42+
** Setting `GIT_TRACE=1` can help you debug the command being run for
43+
your alias.

0 commit comments

Comments
 (0)