I'm trying to run growlnotify.exe from a Windows bash prompt. Recompiling it for mingw32 isn't a good option for me.
growlnotify works if I use it from the cmd prompt, but it fails (mostly) from the bash prompt. It only seems to be able to take a single argument, one without a switch (which is the notification message). If there is more than one argument, it fails silently. If there is a single switch and no other arguments, that switch is sent as the message.
I've managed to dig up some hints on Google that it has something to do with the way Windows doesn't provide a real tty, but no fixes. Is there any clever way to force this to work? Some way of escaping the arguments correctly such that it behaves as expected?
If I run it it with tripled slashes, the arguments are ignored. Whereas if I run it with what is the correct format in DOS, it fails silently.
Failure (also failes if I use //):
growlnotify /a:'Application Name' /n:'Notification Type' 'message goes here'
growlnotify ///a:'Application Name' ///n:'Notification Type' 'message goes here'
That one will send a notices with the 'message goes here', but as if I hadn't bothered to include the first two arguments. Single or double slashes though, it never sends a notice (as if I included no arguments at all).
Quadruple and quintuple slashes behave the same as triple slashes.