Multiple --conf options in calling dosbox-x via CLI #4304
Unanswered
hadjiprocopis
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The manual says:
I have discovered that the way it is overlaid is that if there exist, say, 2 config files on the CLI and both have the same section, say
[ne2000]
then those parameters specified in the 1st config file will be overwritten by those that may exist in the 2nd config file (under said section). So, if the 1st hasne2000=true
and the 2nd (the one later in the command-line) hasne2000=false
then the 2nd prevails:ne2000=false
.HOWEVER. if (by accident or after many cycles of experimentation or plain incompetence) I comment the parameter in the 2nd config file. Then, the parameter in the 1st file will be read and then all (uncommented) parameters in the 2nd file.
I personally find this mix+match as cause for accidental behaviour and hours of debugging (and forum questions).
I propose that multiple config files are allowed on the command line. But if a section (even if empty) exists in the 2nd config file, then the all the parameters under this same section in the 1st config file are ignored. In a few words, multiple config options are still allowed but they work on the section level and not on the parameter-under-each-section level.
Of course this is a proposal based on what I personally consider "normal behaviour" (and also because I spent 4 hours trying to debug networking not working when I separated the config files :) ).
Thank you for the excellent software you are providing us
Beta Was this translation helpful? Give feedback.
All reactions