From: Adam Dinwoodie
>John Wiersba wrote:
>>P.S. I don't know why, but my reply kept getting rejected as spam by
>>cygwin.org's filters, even though I was using yahoo's "plain text" mode:
>>
>> Remote host said: 552 spam score exceeded threshold (#5.6.1) [BODY]
>
>See http://cygwin.com/ml/#spam
ned.
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
From: "Buchbinder, Barry (NIH/NIAID) [E]"
Sent: Sunday, August 5, 2012 2:38 PM
Subject: RE: Cygstart bug: doesn't keep command line arguments intact
John Wiersb
John Wiersba wrote:
>P.S. I don't know why, but my reply kept getting rejected as spam by
>cygwin.org's filters, even though I was using yahoo's "plain text" mode:
>
> Remote host said: 552 spam score exceeded threshold (#5.6.1) [BODY]
See http://cygwin.com/ml/#spam for how to avoid that.
Also,
Thanks for your reply, Barry. Yes, it seems that way to me, too. But that
seems wrong. I would think that cygstart should pass arg1 as arg1 to the
specified command (winword.exe in my example). That's certainly the way it
works in the unix/linux world and cygstart should be considered as an
John Wiersba wrote August 03, 2012 3:18 PM
>Calling /c/program\ files/microsoft\ office/office12/winword.exe
>"a b c.doc" works.
>Calling cygstart /c/program\ files/microsoft\ office/office12/winword.exe "a b
>c.doc" tries to open a.doc, b.doc, and c.doc.
In the first, bash strips t
Calling /c/program\ files/microsoft\ office/office12/winword.exe
"a b c.doc" works.
Calling cygstart /c/program\ files/microsoft\ office/office12/winword.exe "a b
c.doc" tries to open a.doc, b.doc, and c.doc.
I couldn't find this reported in the mailing list archives.
--
Problem
6 matches
Mail list logo
