- Oct
- 381
- 2
Hello — I been running an old win10 32bit system as a vm and came across this issue — I have take v19 (long past it EOL but still works for me) and was running it as a stand-a-lone program with the switches
"/is /ix /ii /ip /q /c” so that it would run just 1 internal command and I would then capture the output of it. What I found out is that these switches for most part stop the default start up, but in this case the plugins were still auto-loaded from the plugins folder.
I check with the help/doc and it seems that /I is the parent option and the the other are specific to what to turn-off when tcc starts. So I changed the switches to just “i /q /c" and this setting stopped the plugins from loading.
Not sure if this is a bug, and I know its version 19 but should both sets of switches work the same way?
"/is /ix /ii /ip /q /c” so that it would run just 1 internal command and I would then capture the output of it. What I found out is that these switches for most part stop the default start up, but in this case the plugins were still auto-loaded from the plugins folder.
I check with the help/doc and it seems that /I is the parent option and the the other are specific to what to turn-off when tcc starts. So I changed the switches to just “i /q /c" and this setting stopped the plugins from loading.
Not sure if this is a bug, and I know its version 19 but should both sets of switches work the same way?