From: Nem W Schlecht <nem@emptec.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Change in 'cygstart' functionality?
Date: Tue, 13 Sep 2016 19:05:00 -0000 [thread overview]
Message-ID: <CA+2x6-LnaY5TWyor14N8pcU-JYfFT_BMmW7r-R3xQC-KBz9F9w@mail.gmail.com> (raw)
In-Reply-To: <a6817bbe-4f5f-a410-3aa6-272e9acc7df3@cornell.edu>
On Tue, Sep 13, 2016 at 12:44 PM, Ken Brown <kbrown@cornell.edu> wrote:
> On 9/13/2016 10:50 AM, Nem W Schlecht wrote:
>>
>> 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.
>>
>>
[deletia]
>
>
> There's no code in cygstart to recognize the SIP protocol. (It wouldn't be
> hard to add such code, as was done a few years ago for "mailto:". See line
> 598 of cygstart.c in the sources for the cygutils package.)
>
> So cygstart treats "sip:user@domain.com" as a file name. The funny Unicode
> character you see comes from Cygwin's translation to allow ":" as part of a
> file name. See
>
>
> https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars
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. :)
--
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 prev parent reply other threads:[~2016-09-13 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 16:31 Nem W Schlecht
2016-09-13 17:53 ` Ken Brown
2016-09-13 19:05 ` Nem W Schlecht [this message]
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-LnaY5TWyor14N8pcU-JYfFT_BMmW7r-R3xQC-KBz9F9w@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).