Total Commander

"About Total Commander" can show what wincmd.ini file is actually used by Lister, which is mainly useful when is Lister started as separate process (%COMMANDER_EXE% [/O] /S=L [<file to open>]).

On some tests I found that under some yet not very clear conditions it seems external Lister uses not expected settings, so knowing from what wincmd.ini it reads the settings can help to find out where is a problem...

2DrShark
I have found that it is better to use:
%COMMANDER_EXE% [/O] /i="%COMMANDER_INI%" /S=L [<file to open>]

Then Lister will always use the ini file that was used to when opening TC.

If you omit /i="%COMMANDER_INI%" and you had originally started TC with the parameter: /i=<inifile to use>, then TC will start Lister with the default ini file as configured and not the <inifile to use>

2petermad
I think you're right, but still adding that dialog to Lister could help especially if many Lister instances with different settings are launched.