Change in 'cygstart' functionality?
Tue Sep 13 19:52:00 GMT 2016
Greetings, Nem W Schlecht!
> Thanks for the excellent breakdown, Ken. Makes sense with the colon
> ":". Still not sure why it did work a couple months ago and now
> doesn't. I was under the assumption that 'cygstart' was a very basic
> program that just passed whatever it was passed on to Windows to
> handle - similar to "Start-Process" in Powershell, or well, just like
> double-clicking on something on the Desktop.
> My 'cygstart's last mod time is Nov 24, 2015 and this was definitely
> working *after* that time, so something else changed. It's like
> 'cygstart' is assuming this is a file and trying to do something smart
> that way rather than just letting Windows handle it (as it would
> *need* to do if this were indeed a Cygwin path). Again, when I add in
> the extra slashes, S4B *does* get the SIP request. Without the
> slashes, something in Cygwin is assuming this is a filesystem call.
> I'll take a look at the 'cygstart' code and see if (with my lowly
> programming skills) I can suggest a patch. :)
In the meantime, you could use a workaround.
"$SYSTEMROOT/System32/cmd.exe" /C START "" /NOWAIT "sip:..."
With best regards,
Tuesday, September 13, 2016 22:01:17
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin