Page 1 of 1
Command line params /Ini, /NewIni
Posted: 21.10.2007, 14:39
by Alex
Command line params:
FreeCommander.exe start FC with plugins and use FreeCommander.ini file
FreeCommander.exe /NewIni=FCTest.ini /NoPlugins start FC without plugins and create always new FCTest.ini settings file (delete any existing FCTest.ini file before)
FreeCommander.exe /Ini=FCTest.ini /NoPlugins start FC without plugins and use existing FCTest.ini settings file
Empty file path means FC folder.
Posted: 21.10.2007, 16:52
by Dreamer
I support this request. It would be very useful when testing bugs with default settings and without plugins. I'm not sure how it should work exactly...
FreeCommander.exe should start FC with plugins and use FreeCommander.ini file and...
FreeCommander.exe /I=New.ini /NoPlugins should start FC without plugins and create new New.ini settings file, right? But when I change some option and start FC with the same parameters? New New.ini file will be created / old will be deleted?
If so, I suggest another parameter, because we need to use default settings, change few options and restart FC to test some bug, so here is my suggestion (I have changes New.ini to FCTest.ini, perhaps you can find a better name, it's not so important):
FreeCommander.exe start FC with plugins and use FreeCommander.ini file
FreeCommander.exe /NewIni=FCTest.ini /NoPlugins start FC without plugins and create always new FCTest.ini settings file (delete any existing FCTest.ini file before)
FreeCommander.exe /Ini=FCTest.ini /NoPlugins start FC without plugins and use existing FCTest.ini settings file
Of course, the new instance of FC should be started always.
I have a special FC folder to test bugs with default settings now, but I have to update both folders for each new version and delete the ini file often. With the suggestions above we could just create two shortcuts.
Posted: 21.10.2007, 17:12
by Alex
FreeCommander.exe /I=New.ini /NoPlugins should start FC without plugins and create new New.ini settings file, right?
Should use the New.ini, if it exists, or create new if it doesn't exist.
Like in TC.
FreeCommander.exe /NewIni=FCTest.ini /NoPlugins start FC without plugins and create always new FCTest.ini settings file (delete any existing FCTest.ini file before)
FreeCommander.exe /Ini=FCTest.ini /NoPlugins start FC without plugins and use existing FCTest.ini settings file
Support!
Posted: 21.10.2007, 17:59
by Dreamer
Alex wrote:FreeCommander.exe /I=New.ini /NoPlugins should start FC without plugins and create new New.ini settings file, right?
Should use the New.ini, if it exists, or create new if it doesn't exist.
Like in TC.
Yes, but we'd still have to enter that dir and delete the ini often, therefore my new suggestions.
Posted: 23.10.2007, 20:58
by Dreamer
Alex wrote:FreeCommander.exe /NewIni=FCTest.ini /NoPlugins start FC without plugins and create always new FCTest.ini settings file (delete any existing FCTest.ini file before)
FreeCommander.exe /Ini=FCTest.ini /NoPlugins start FC without plugins and use existing FCTest.ini settings file
Support!
Added in the (beta) test version, not released yet. Works perfect! Thanks Marek.
Closed.