X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-Envelope-To: X-Virus-Status: Clean Message-ID: <48A0AF77.30709@mscha.org> Date: Mon, 11 Aug 2008 23:30:31 +0200 From: Michael Schaap User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: PATCH: cygutils/cygstart - wait till task terminates (i.e. run in foreground) References: <40q0a4d1qej604aerns94mr6562dr5tigg AT 4ax DOT com> In-Reply-To: <40q0a4d1qej604aerns94mr6562dr5tigg@4ax.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 On 11-Aug-2008 18:26, Barry Kelly wrote: > I find cygstart useful generally, but ShellExecute/Ex has more options > than cygstart exposes. > > In particular, I'd like to be able to write a script that starts an > action and waits for it to complete, and then perform another action. > This means that I don't want cygstart to return until the process it has > started exits (modulo MDI etc). > > ShellExecuteEx can return the process handle, which can then be waited > on. > > I've written a patch against cygutils-1.3.2-1 that implements this > functionality via a new "-w | --wait" argument. > > I've attached the patch for review. Is there any other place I should be > posting to submit this patch? > > This is the right place, as far as I'm concerned. This seems useful and the patch looks good at first glance, but I'll have a better look at it, probably this weekend. Thanks, – Michael -- 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/