X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: Eli Zaretskii To: help-gnu-emacs AT gnu DOT org, cygwin AT cygwin DOT com In-reply-to: (message from Oleksandr Gavenko on Thu, 03 Jun 2010 23:33:44 +0300) Subject: Re: Why call-process removes '{' and '}' chars from arguments??? References: <83wruhru5j DOT fsf AT gnu DOT org> <4C07C495 DOT 7040709 AT cygwin DOT com> Message-Id: Date: Fri, 04 Jun 2010 04:56:28 -0400 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > From: Oleksandr Gavenko > Date: Thu, 03 Jun 2010 23:33:44 +0300 > Cc: cygwin AT cygwin DOT com > > %* in .bat file not proper work - it strip all chars after > first new line occurrence. > > I think in Windows there are no anything scriptable with > "$*" like in POSIX sh. Yes, there is: it's %*. The problem is that the Windows shells do not support command lines with embedded newlines at all. > To workaround this I create executable > which linked with Cygwin runtime and as in BusyBox > to 'execvp' passed base name as command and all args without > changes. Cygwin 'execvp' first search for 'prog' then > for 'prog.exe' so trick worked! > > So I switch from simple .bat wrapper to > special executable. To enable another Cygwin script 'foo' > for Emacs I just copy existing executable: > > $ cp hg.exe foo.exe Mixing the native Windows build of Emacs with Cygwin is asking for trouble. I expect you to see more surprises down the line. I highly recommend to install the Cygwin build of Emacs and use that instead. -- 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