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

[BUG 1.7.6.1] `git config --bool --get-regexp' omits separating space... sometimes!

From
BFBrian 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/
Next: Matthieu Moy
Message 1 of 4 in “[BUG 1.7.6.1] `git config --bool --get-regexp' omits separating space... sometimes!”
  1. Brian FosterOct 10, 2011
  2. Matthieu MoyOct 10, 2011
  3. config: display key_delim for config --bool --get-regexpMatthieu Moy, Oct 10, 2011
  4. Junio C HamanoOct 10, 2011

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.