- Mar
- 30
- 0
Unexpected things happening with batch scripts (from a CMD perspective)
I have finally moved to TCC/LE as my default shell. When I run batch scripts I get some different behaviour from CMD. I would like to stop them from happening.
First of all, del stdout is echoed, when it would not be in CMD. Can I stop this from happening? I know that about the /q switch and 2>nul, but I would rather use a global options that makes it act as CMD in this regard, so that I do not need to edit all my scripts just because of this.
On every scripts which I have used SetLocal, I get an error at the EndLocal line saying that there was no SetLocal, when there was. I have tried different capitalisation combinations, but it does not seem to realise that I have SetLocal. What is going on?
When running scripts I get erratic behaviour where the console clears, as though there has been a cls command. There does not seem to be a pattern to this happening. Why does this happen and can it be stopped?
Thanks.
I have finally moved to TCC/LE as my default shell. When I run batch scripts I get some different behaviour from CMD. I would like to stop them from happening.
First of all, del stdout is echoed, when it would not be in CMD. Can I stop this from happening? I know that about the /q switch and 2>nul, but I would rather use a global options that makes it act as CMD in this regard, so that I do not need to edit all my scripts just because of this.
On every scripts which I have used SetLocal, I get an error at the EndLocal line saying that there was no SetLocal, when there was. I have tried different capitalisation combinations, but it does not seem to realise that I have SetLocal. What is going on?
When running scripts I get erratic behaviour where the console clears, as though there has been a cls command. There does not seem to be a pattern to this happening. Why does this happen and can it be stopped?
Thanks.