Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Dave Korn" To: "'Cygwin List'" Subject: RE: Bash returns incorrect process status Date: Tue, 21 Sep 2004 15:42:00 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <6.1.0.6.0.20040921103816.03d49d30@pop.prospeed.net> Message-ID: X-OriginalArrivalTime: 21 Sep 2004 14:42:00.0843 (UTC) FILETIME=[2747CDB0:01C49FE9] > -----Original Message----- > From: cygwin-owner On Behalf Of Larry Hall > Sent: 21 September 2004 15:39 > 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. He was referring to the one in Pierre's post, to which his post was a reply. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/