|
From: Yuri K. <yur...@gm...> - 2014-06-26 06:25:42
|
> > Another, perhaps easier workaround is to write your command, as you'd > type it at the cmd.exe prompt, to a batch file, and then invoke > cmd.exe to run that batch file. If you keep the batch file's name > without whitespace, the command that invokes it can side-step the > quoting issue altogether. It should work out even if it contains spaces, as long as I quote them. > When you are done, delete the batch file. It's not a script to be run once. It's to be executed from time to time. Additionally, before coming with pipe-to-cmd solution, I had other workaround in mind: >bash -l some\script.sh & hstart /elevate "cmd /k c:\path\to\nginx -s reload -c c:\path\to\nginx.conf" Come to think of it, I still use cmd.exe as you can see, so that the extra window wouldn't disappear right away and I could see the errors, if any. Regards, Yuri |