Total Commander

The idea is to have some defwcmd.ini file with some custom settings defined by user in TC folder so when user starts
totalcmd.exe with /I=someepath\newwincmd.ini parameter where newwincmd.ini file doesn't exist, TC sholud copy defwcmd.ini to newwincmd.ini and then start itself using this settings file.
This way user can start TC with almost default settings but with some minor pre-defined tweaks. For example, in such defwcmd.ini I would set some short aliases to %COMMANDER_PATH%, %COMMANDER_EXE%, %COMMANDER_INI%.

This can be achieved by just using an hand-crafted ini file
with the required basic settings for such tests.
On the next test just copy over it again.

Horst.Epp wrote:This can be achieved by just using an hand-crafted ini file
with ... On the next test just copy over it again.

That "copy" part, even done using external scripting, isn't convenient. I'd prefer to start TC with /I=newwincmd.ini and focus on work.

DrShark wrote:

Horst.Epp wrote:This can be achieved by just using an hand-crafted ini file
with ... On the next test just copy over it again.

That "copy" part, even done using external scripting, isn't convenient.

The same is true from TC point of view