From: Nem W Schlecht <nem@emptec.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Change in 'cygstart' functionality?
Date: Tue, 13 Sep 2016 16:31:00 -0000 [thread overview]
Message-ID: <CA+2x6-LBn+9Sotx97Vvs+bxAj4NcV8eqkwyVKwGCtmdgSwYj3A@mail.gmail.com> (raw)
Hello all,
So, I used to be able to do this in Cygwin to open a chat session (in
my case, With Skype for Business aka S4B):
cygstart "sip:user@domain.com"
But I noticed recently that this now fails with:
Unable to start 'sipuser@domain.com': The specified file was not found.
I have no idea why the colon ":" is getting converted into an a UTF
F038 character. I'm also unsure of when this stopped working, since I
don't use it all that often.
I thought maybe having some slashes would be required, so I tried:
cygstart "sip:/user@domain.com"
Error:
Unable to start 'sip\user@domain.com': The specified file was not found.
And yes, I did cut-paste that and *yes* the direction of the slash *changed*.
With 2 slashes, a get an error in S4B that the address doesn't
exist/is incorrect.
With 3 slashes, a new chat window opens! But its with user
"///user@domain" (ie - non-existant user).
Is the way the SIP protocol needs to be called broken or did something
change in Cygwin to require slashes as a part of cygstart?
Any suggestions on this?
Thanks everybody!
--
Nem W Schlecht
"Perl did the magic. I just waved the wand."
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2016-09-13 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 16:31 Nem W Schlecht [this message]
2016-09-13 17:53 ` Ken Brown
2016-09-13 19:05 ` Nem W Schlecht
2016-09-13 19:52 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+2x6-LBn+9Sotx97Vvs+bxAj4NcV8eqkwyVKwGCtmdgSwYj3A@mail.gmail.com \
--to=nem@emptec.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).