Revision f33c2c0f9e2258a80e6e406af39e9fa3fd6e430e authored by Ramkumar Ramachandra on 05 January 2014, 10:18:03 UTC, committed by Junio C Hamano on 06 January 2014, 17:14:48 UTC
There are situations where multiple classes of completions possible. For example branch.<TAB> should try to complete branch.master. branch.autosetupmerge branch.autosetuprebase The first candidate has the suffix ".", and the second/ third candidates have the suffix " ". To facilitate completions of this kind, create a variation of __gitcomp_nl () that appends to the existing list of completion candidates, COMPREPLY. Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent d028b89
t0005-signals.sh
#!/bin/sh
test_description='signals work as we expect'
. ./test-lib.sh
cat >expect <<EOF
three
two
one
EOF
test_expect_success 'sigchain works' '
test-sigchain >actual
case "$?" in
143) true ;; # POSIX w/ SIGTERM=15
271) true ;; # ksh w/ SIGTERM=15
3) true ;; # Windows
*) false ;;
esac &&
test_cmp expect actual
'
test_expect_success !MINGW 'signals are propagated using shell convention' '
# we use exec here to avoid any sub-shell interpretation
# of the exit code
git config alias.sigterm "!exec test-sigchain" &&
test_expect_code 143 git sigterm
'
test_done
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...