On 2005-10-16 04:07:52 +0000 Nicola Pero <[EMAIL PROTECTED]>
wrote:
(I believe an empty GNUSTEP_CONFIG_FILE should cause no config file to
be read and the compiled-in defaults to be used with no warnings, but I
suppose we need to check if that really works).
Yes ... the base code has been issuing warnings about undefined
GNUSTEP_SYSTEM_ROOT, GNUSTEP_LOCAL_ROOT, and GNUSTEP_NETWORK_ROOT for a very
long time... but I agree that it really doesn't need to, so I've removed
those three warning messages.
Maybe to disable config files you'd set the corresponding variable /
config value to a non-existing or empty file. I suppose that might work,
it's easy to ignore non-existing or empty files. ;-)
I thought of that ... but it's not as conceptually tidy as setting the file
to nothing (an empty string), and I prefer an earlier suggestion you made
... add a new variable in the system config file to turn off parsing of the
user config file.
eg.
GNUSTEP_DISABLE_USER_CONFIG=YES
PS. If we have boolean switches like that,. what do we want their allowed
values to be?
I think an undefined or empty value should be false, but I'm not sure
whether to support a single 'YES' or common variations such as '1', 'True'
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
