Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040921103816.03d49d30@pop.prospeed.net> X-Sender: Date: Tue, 21 Sep 2004 10:38:46 -0400 To: Eric Hanchrow , cygwin@cygwin.com From: Larry Hall Subject: Re: Bash returns incorrect process status In-Reply-To: <87vfe7lmkx.fsf@offby1.atm01.sea.blarg.net> References: <90459864DAD67D43BDD3D517DEFC2F7D7138@axon.Axentia.local> <3.0.5.32.20040917225811.00818730@incoming.verizon.net> <87vfe7lmkx.fsf@offby1.atm01.sea.blarg.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 10:32 AM 9/21/2004, you wrote: >This patch also fixes a long-standing problem that I've had: > > My .bash_profile is rather complex (actually, it sources .bashrc, > which is where most of the complexity is), and at the end it runs a > program called `keychain'. That program always does some output and > sometimes does some input. Before I applied this patch, most (but > not all) of the time, keychain appeared to run in the background -- > that is, I'd see a prompt from bash, implying that it had finished > executing commands from its startup files, but then I'd see output > from keychain. Worse, if keychain wanted to read input, it seemed > to "hear" only a garbled version of what I typed (in fact, the input > that it wants is my password, and would always claim I'd mistyped > it). With the patch, however, it works perfectly. You forgot to include the patch. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/