| commit | 01160bafb6b0c94319bd33ba197a4c72ebbcbe96 | |
| author | Steffen "Daode" Nurpmeso <sdaoden@users.sf.net> | |
| Wed, 24 Oct 2012 21:11:47 +0000 (24 23:11 +0200) | ||
| committer | Steffen "Daode" Nurpmeso <sdaoden@users.sf.net> | |
| Thu, 25 Oct 2012 15:19:30 +0000 (25 17:19 +0200) | ||
| tree | e8330ff91817522e3f5d3601d37bac436e91c337 | treesnapshot (tar.gz zip) |
| parent | 6788f9bb3e8142054a0a0f3c4a38d4c3bdd53c95 | commitdiff |
Do not warn when handling -S, the first time..
(main.c: set -S twice! And about command line processing..,
2012-10-18).. fixed the problem that -S settings were not
active during further command line processing by set()ing the
user desire twice.
However, if the user effectively initiates an unset request it
most likely results in (at least) a warning of the option is not
set.
To overcome this use the unset_allow_undefined= mechanism to
suppress the warning for the first set(). If the second set()
that happens after the resource files are loaded still does not
find anything to unset the warning will be fine (maybe).
(main.c: set -S twice! And about command line processing..,
2012-10-18).. fixed the problem that -S settings were not
active during further command line processing by set()ing the
user desire twice.
However, if the user effectively initiates an unset request it
most likely results in (at least) a warning of the option is not
set.
To overcome this use the unset_allow_undefined= mechanism to
suppress the warning for the first set(). If the second set()
that happens after the resource files are loaded still does not
find anything to unset the warning will be fine (maybe).
| main.c | diffblobblamehistory |