delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-0.5 required=5.0 tests=BAYES_05,T_RP_MATCHES_RCVD |
X-Spam-Check-By: | sourceware.org |
X-IronPortListener: | Outbound_SMTP |
From: | "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder AT niaid DOT nih DOT gov> |
To: | "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com> |
Date: | Fri, 2 Apr 2010 15:46:17 -0400 |
Subject: | RE: Show window for BASH script run with /bin/run |
Message-ID: | <0105D5C1E0353146B1B222348B0411A208DEF244D1@NIHMLBX02.nih.gov> |
References: | <28121386 DOT post AT talk DOT nabble DOT com> <e8r7hop3dv0 DOT fsf AT FLM000025LVE9F DOT catmktg DOT com> |
In-Reply-To: | <e8r7hop3dv0.fsf@FLM000025LVE9F.catmktg.com> |
MIME-Version: | 1.0 |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
J. David Boyd sent the following at Friday, April 02, 2010 2:32 PM >JPMcGrath <JPMcGrath AT JPMcGrath DOT net> writes: >> I am running a bash script under cygwin from within another >> (non-cygwin) program. The script normally does not interact with the >> user, so I use /usr/bin/run when running the script to avoid having a >> bash window constantly popping up and going away. However, if the >> script encounters an error, I need to show the user what went wrong. >> What I am looking for is a way for the script to show the hidden window >> if it encounters an error. >> Does anyone know how to do this? >> >> Thanks in advance. > >Write the error output of the hidden script to a file that was removed >before the script ran. If the file exists after the script exits, pop it >up and show the contents to the user. If the file doesn't exist after >the script exits, everything is fine. You might also look at the options available with cygstart. Please note that I've never had to do this, so I may be misunderstanding the man page. Good luck, - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |