From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 453 invoked by alias); 12 Jan 2009 23:17:28 -0000 Received: (qmail 445 invoked by uid 22791); 12 Jan 2009 23:17:27 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from nihxway2out.hub.nih.gov (HELO nihxway2out.hub.nih.gov) (128.231.90.110) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 12 Jan 2009 23:16:42 +0000 X-IronPortListener: Outbound_SMTP Received: from nihcessmtp3.hub.nih.gov ([128.231.90.117]) by nihxway2out.hub.nih.gov with ESMTP; 12 Jan 2009 18:16:39 -0500 Received: from NIHHT01.nih.gov ([156.40.71.20]) by NIHCESSMTP3.hub.nih.gov with Microsoft SMTPSVC(6.0.3790.1830); Mon, 12 Jan 2009 18:16:38 -0500 Received: from NIHMLBX02.nih.gov ([156.40.71.32]) by NIHHT01.nih.gov ([156.40.71.20]) with mapi; Mon, 12 Jan 2009 18:16:39 -0500 From: "Buchbinder, Barry (NIH/NIAID) [E]" To: "cygwin@cygwin.com" , 'Jeenu V' Date: Tue, 13 Jan 2009 01:17:00 -0000 Subject: RE: Wait for cygstart finish Message-ID: <0105D5C1E0353146B1B222348B0411A211B41E5E@NIHMLBX02.nih.gov> References: <5195c8760901120434u42ce641asee9c72c247cabdb1@mail.gmail.com> <496B6FBB.2060400@cygwin.com> <5195c8760901120845m74185024hbf60a3bd5fd79632@mail.gmail.com> In-Reply-To: <5195c8760901120845m74185024hbf60a3bd5fd79632@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2009-01/txt/msg00334.txt.bz2 Jeenu V wrote on Monday, January 12, 2009 11:45 AM: > On Mon, Jan 12, 2009 at 9:58 PM, Larry Hall (Cygwin) > wrote: >> Just run the app without 'cygstart'? > > :) Well this was related to one of my earlier posts, if you recall, > where I had problems with running cmd.exe from screen. I now work > that around by calling cmd.exe with cygstart. Everything works fine - > just that I wanted to know if there's a way to make cygstart wait for > the application to finish. Currently there isn't; see $ man cygstart $ cygstart --help You could always apply the patch that you mentioned earlier yourself and re-compile cygstart. Work-around: You might try the following. $ cmd /c start /wait You also might want to see if start's "/b" option helps. B Start application without creating a new window. The application has ^C handling ignored. Unless the application enables ^C processing, ^Break is the only way to interrupt the application (Please note that I've never even tried "/b" -- my suggestion comes from start /?, not any experience.) - Barry -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/