Re: [hatari-devel] --natfeats on and -c order

[ Thread Index | Date Index | More Archives ]

Am Thu, 30 Dec 2021 22:28:43 +0100
schrieb Miro Kropáček <miro.kropacek@xxxxxxxxx>:

> Hi,
> not a critical bug but perhaps still worth fixing: it seems that
> hatari doesn't honour order of command line options equally.
> This overrides (disables) natfeats but keeps trace:
> hatari --natfeats on --trace os_base -c debug.cfg
> while this:
> hatari -c debug.cfg --natfeats on --trace os_base
> enables both natfeats and trace. Of course, my preferred behaviour
> would be to have natfeats enabled. ;)

Do you have "bNatFeats = FALSE" in your debu.cfg? If so, this is the
expected behaviour: Options are evaluated from left to right, so if you
specify your config file as last option, the values in there override
the ones that you specify earlier.

As for "--trace", I think these values are not saved in the config
files, so for this option, the value does not get overwritten by the
"-c debug.cfg" option.


Mail converted by MHonArc 2.6.19+