Hi Roman.
> Now if you call aaa.bat its ECHO state will not be affected by the
'@echo off' command found in the internal bbb.bat worker script.
In this situation:
aaa.bat - is my own script (that calls git.cmd)
bbb.bat - is git.cmd
So you also mean that we need to fix git.cmd to make it preserving echo
state?
Well, I just suggested a possible implementation that allows writing
Windows batch scripts that do not change their external ECHO state.
Whether that should be used for the git.cmd script in msysgit -
that's up to someone else, but it would allow you to do what you
requested - write your own wrapper scripts without having to worry about
git.cmd changing your ECHO state.
Hope this helps.
Best regards,
Jurko Gospodnetić
