RE: Re: Client-side hook doesn

> Cmd.exe is not a hook script, it is just the command interpreter. You
> need to provide the path to the actual script, e.g. start-commit.bat,
> start-commit.js, start-commit.exe, my-own-hook.cmd, or whatever your
> hook is called.

Simon, thanks for the reply. I know that cmd.exe is not a meaningful program in this context, I just wanted to have **something** executed. I had configured the start_commit_script as a *.bat file which only contains the follwing text:

echo %0 %*
pause

...which only showed the flashing command prompt window, so I tried cmd.exe instead.

I believe I found the reason for the problem:
To execute the *.bat hook script, cmd.exe is run, but input and output are redirected (probably, to/from the NUL device), so the pause command, like cmd.exe itself, thinks this is the end of the input, and exits; likewise, the echo command echoes to nowhere, and the command windows remains empty. The command

pause > con < con

in contrast, outputs "press any key", and then waits for a keypress!

I guess this behaviour makes sense for automated scripting, but for testing scripts, it comes as a bit of a surprise...

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3000395

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-08-23 11:05:07 CEST