On Apr 6 02:09, Yitzchak Scott-Thoennes wrote:
> Corinna, have you a chance to think about this? I've come to think that
> using the MinGW rules makes most sense.
I didn't think any further about this. It's not that important since
it's easily workaroundable. I also fear we get the usual compl
On Thu, Jan 20, 2005 at 10:26:13AM +0100, Corinna Vinschen wrote:
> Yitzchak,
>
> On Jan 19 15:34, Yitzchak Scott-Thoennes wrote:
> > > $ ./nocygparent cygchild
> > > [a\b"c]
> >
> > Can anybody else confirm this?
>
> I can. I already had a look into this. The command line handling in
> Cygwin
On Jan 20 01:41, Yitzchak Scott-Thoennes wrote:
> On Thu, Jan 20, 2005 at 10:26:13AM +0100, Corinna Vinschen wrote:
> > Yitzchak,
> >
> > On Jan 19 15:34, Yitzchak Scott-Thoennes wrote:
> > > > $ ./nocygparent cygchild
> > > > [a\b"c]
> > >
> > > Can anybody else confirm this?
> >
> > I can. I
On Thu, Jan 20, 2005 at 10:26:13AM +0100, Corinna Vinschen wrote:
> Yitzchak,
>
> On Jan 19 15:34, Yitzchak Scott-Thoennes wrote:
> > > $ ./nocygparent cygchild
> > > [a\b"c]
> >
> > Can anybody else confirm this?
>
> I can. I already had a look into this.
Wonderful! Thanks a lot!
> The comm
Yitzchak,
On Jan 19 15:34, Yitzchak Scott-Thoennes wrote:
> > $ ./nocygparent cygchild
> > [a\b"c]
>
> Can anybody else confirm this?
I can. I already had a look into this. The command line handling in
Cygwin is different from the command line handling in MingW or, FWIW,
VC++ CLI applications.
ygwin.com
> > Subject: Re: cygwin programs called from non-cygwin programs
> > mauling \" in args
> >
> > On Wed, Jan 12, 2005 at 10:42:48PM -0800, Yitzchak
> > Scott-Thoennes wrote:
> > > $ cat child.c
> > > #include
> > &
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Yitzchak Scott-Thoennes
> Sent: Wednesday, January 19, 2005 5:34 PM
> To: cygwin@cygwin.com
> Subject: Re: cygwin programs called from non-cygwin programs
> mauling \" i
On Wed, Jan 12, 2005 at 10:42:48PM -0800, Yitzchak Scott-Thoennes wrote:
> $ cat child.c
> #include
> int main(int argc, char **argv)
> {
> printf("[%s]\n", argv[1]);
> return 0;
> }
>
> $ cat parent.c
> #include
> int main(int argc, char **argv) {
> char *args[] = { argv[1], "a\\\"b\\\"c"
On Wed, Jan 12, 2005 at 10:42:48PM -0800, Yitzchak Scott-Thoennes wrote:
> Given a simple child process that prints its argument, and a parent
> that execs it passing a\"b\"c, trying combinations of cygwin and non-
> cygwin parent and child shows inconsistency in what's received:
>
> $ cat child.c
9 matches
Mail list logo
