j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM7<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=461.msg4709#msg4709">Quote from: gavinandresen on July 21, 2010, 12:11:10 PM</a></div><div class="quote">I just did a quick survey of 20 .conf files in /etc on my debian system, and found:<br/> 1 file used "key value"<br/> 5 used "key=value" <br/></div>Thanks for that survey!<br/><br/>I find "key value" a little unnatural. There ought to be a more definite separator between key and value that suggests assignment. The space people may just be getting lazy using their language's split function.<br/>key=some full sentence with spaces in it. # seems more clear<br/>key some full sentence with spaces in it. # than this<br/><br/>Allright then, lets go with self-parsed mapConfig, syntax:<br/># comment<br/>key=value<br/><br/>file extension .conf. What's the filename, is it ~/.bitcoin/settings.conf or ~/.bitcoin/bitcoin.conf or what? <br/><br/>I think we better strip whitespace at the beginning and end of the key and the value.<br/># user who likes column formatted <br/>k = value<br/>key = value<br/>longerkey = this sentence would be this # "this sentence would be this"<br/> key = value # guess this is ok too<br/> nextkey = value<br/> right = justified<br/><br/>The normal syntax should be "key=value", but you can't blame people for the occasional "key = value".</div> text/html
https://whatsonchain.com/tx/da60b30b50b49705ce85f2f2f46da6af27db00ece930a2e5f3c017aededb4ed0