The title says it all.
I believe such an option would be very useful for testing and bug-tracking purposes.
For instance, empty .ini could be recreated in %temp% each time upon command invocation.
I understand that an experienced user can simulate such behavior in one way or another.
But the idea is intended to also deal with another scope of users for whom some instructions like how to install another copy of Total Commander (which is as it appears buggy by itself), or edit wincmd.ini, are compatible with the flight to the Moon, and therefore should be avoided, while with the proposed approach you just can share a ready-to-go button.
PS
Some examples:cm_Exit 32 could replace those em_(s), and being internal could be easily shared.
I believe such an option would be very useful for testing and bug-tracking purposes.
For instance, empty .ini could be recreated in %temp% each time upon command invocation.
I understand that an experienced user can simulate such behavior in one way or another.
But the idea is intended to also deal with another scope of users for whom some instructions like how to install another copy of Total Commander (which is as it appears buggy by itself), or edit wincmd.ini, are compatible with the flight to the Moon, and therefore should be avoided, while with the proposed approach you just can share a ready-to-go button.
PS
Some examples:
Code:
[em_noini]cmd=%commander_exe% /i=nul /f=nul[em_nul]cmd=cm_exit,em_noiniCode:
[em_tempini]cmd=%commander_exe% /i=%temp%\wincmd.ini /f=%temp%\wcx_ftp.ini[em_temp]cmd=cm_exit,em_tempiniCode:
[em_tempiniclean]cmd=pwsh -command Get-ChildItem $env:Temp -recurse -include ('wincmd.ini','wcx_ftp.ini')|Remove-Item -force[em_temp]cmd=cm_exit,em_tempiniclean,em_tempiniCode:
[em_tempinicleancmd]cmd=%comspec% /q/c del/q "%temp%\wincmd.ini" "%temp%\wcx_ftp.ini"[em_temp]cmd=cm_exit,em_tempinicleancmd,em_tempiniStatistics: Posted by beb — 2024-01-07, 18:15 UTC