NotNull wrote: ↑
Mon Apr 19, 2021 8:52 pm
I think you guys (M/F) are on different wavelengths.
As I see it, Horst is asking why you (@aviasd) use a tot.bat instead of c:\path to\totalcmd64.exe /parms
FWIW: the second one starts TC and activates it. Didn't test the first ( .bat) one.
Yes, running TC directly does activate it.
I'm using a wrapper script for different reasons:
1. I open paths in TC via various scenarios so a parsing script would need to accept those options: I.E: from cmd, from the clipboard, from everything, misbehaving apps in regards to quoting paths, and a few more..
2. When on a new machine the script will generate custom INI for TC (favorite folders) which is different than my regular workstations.
3. if I decide to make a change in the command line parameters for TC, I need to change it only in one place (the script) and not multiple places. I.E everything.ini, other scripts etc..
4. (which is getting obsolete as time passes) - detecting if I'm on 32bit machine and running the correct executable.
So you see, the script makes my life easier, I could use the direct invocation in everything without losing much but the cost of some convenience...