[BUG 1.7.6.1] `git config --bool --get-regexp' omits separating space... sometimes!
- From
- Brian Foster <brian.foster@maxim-ic.com>
- Date
- Oct 10, 2011, 10:20 UTC
- Message-ID
- <201110101220.21890.brian.foster@maxim-ic.com>
Hello,
# Script to illustrate the problem:
rm -f Config
cat <<\EOF >Config
[Example]
Boolean
Other = yes
EOF
git_Config() { git config --file Config "$@"; }git version git_Config --get-regexp '.*\.Boolean' #1. ✓ Ok: example.boolean git_Config --bool --get-regexp '.*\.Boolean' #2. ✗ NO: example.booleantrue git_Config --get-regexp '.*\.Other' #3. ✓ Ok: example.other yes git_Config --bool --get-regexp '.*\.Other' #4. ✓ Ok: example.other true exit
# Output: git version 1.7.6.1 example.boolean example.booleantrue example.other yes example.other true
Case 2 omits the space between the key-name and (generated) value, making the output difficult to parse/process. Without checking, I assume --int (and friends) have a similar bug?
cheers! -blf-
-- Brian FOSTER Principal MTS, Software Maxim Integrated Products (Microcontroller BU), formerly Innova Card Web : http://www.maxim-ic.com/