On Wed, Feb 12, 2003 at 07:23:49PM -0000, Dave Hooper wrote: > I finally got around to trying a recent freenet build, from clean, with a > "--config freenet.ini" configuration file. No wonder people are > complaining about so much brokenness on Windows. Since when have %s been > prepended to 'default settings' in the conf file? What does this mean for > anyone trying to *use* the conf file (e.g. windows frontends)? If %s are > going to be prepended to break freenet on Windows you may as well remove the > "[Freenet node]" header which was originally added only to assist Windows > compatibility :-) > > Does it mean - search for "clientPort=" and if that isn't found search for > "%clientPort="? Or does it, more likely, mean search for "clientPort=" and > if that isn't found use the node's default?
% is simply a different kind of comment. It indicates that the setup program knows about this option, but that it should be set to the node default because the user has not expressed a preference. > > If the latter, which I presume because of the conf file comment of "(so they > don't linger when we want to change the default settings)", is the > recommended way for such a frontend app to query the node for its defaults > to do something like freenet.config.Setup freenet.defaults --silent and > parse that? The important thing is that a setup program MUST comment out or not write options that do not need to be overridden. > > d -- Matthew Toseland [EMAIL PROTECTED][EMAIL PROTECTED] Full time freenet hacker. http://freenetproject.org/ Freenet Distribution Node (temporary) at http://amphibian.dyndns.org:8889/KcW66rKIGAU/ ICTHUS.
msg06748/pgp00000.pgp
Description: PGP signature
