Manual WinMerge using between commandline calls manipulates CL results

[ukr966]

Working with WinMerge in the dialogue in the meantime (e.g. changing settings, column selection, report selection, etc.) changes the results of command line calls ("dark/batch calls"). CL calls must be able to be generated unchanged, even if WinMerge was used differently in the meantime for manual comparisons.

Ideas: [https://github.com/WinMerge/winmerge/discussions/2003]

[sdottaka]

By specifying the /inifile command line option as shown below, settings can be saved and loaded in the specified INI file instead of the registry.

"c:\Program Files\winmerge\WinMergeU.exe" /inifile c:\tmp\wm.ini

I recommend using this INI file when creating reports etc. on the command line.

[ukr966]

Thank you for pointing this out. I have indeed also tested with /inifile. However, I have tested so much in the meantime (compare folder/files) that I no longer know exactly why I discarded it. But it had brought me to: [https://github.com/WinMerge/winmerge/discussions/2005]

It is not clear to the user exactly which things are pulled from the INI, which are overwritten by other parameters, where results are written to and in which form.

That's why I asked for a real batch/dark call with a well-structured/designed interface, as suggested in [https://github.com/WinMerge/winmerge/discussions/2003].

I will test with /inifile again, but I would also be glad for a consideration/answer of the above tickets.