From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>, 'Jeenu V' <jeenuv@gmail.com>
Subject: RE: Wait for cygstart finish
Date: Tue, 13 Jan 2009 01:17:00 -0000 [thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A211B41E5E@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <5195c8760901120845m74185024hbf60a3bd5fd79632@mail.gmail.com>
Jeenu V wrote on Monday, January 12, 2009 11:45 AM:
> On Mon, Jan 12, 2009 at 9:58 PM, Larry Hall (Cygwin)
> <reply-to-list-only-lh@cygwin.com> 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/
prev parent reply other threads:[~2009-01-12 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 12:51 Jeenu V
[not found] ` <496B6FBB.2060400@cygwin.com>
2009-01-12 17:49 ` Jeenu V
2009-01-13 1:17 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0105D5C1E0353146B1B222348B0411A211B41E5E@NIHMLBX02.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--cc=cygwin@cygwin.com \
--cc=jeenuv@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).