From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Faylor To: cygwin@sourceware.cygnus.com Subject: Re: xterms and vi Date: Tue, 10 Aug 1999 21:44:00 -0000 Message-id: <19990811004628.B4110@cygnus.com> References: <19990810234737.25494.rocketmail@web117.yahoomail.com> X-SW-Source: 1999-08/msg00181.html On Tue, Aug 10, 1999 at 08:52:09PM -0400, Suhaib M. Siddiqi wrote: >> Note: Make the appropriate backups before installing. >> Strangeness has been >> noted with interactive bash or sh starting another interactive bash or sh >> process which Chris is pulling his hair out trying to fix. > >Hmmm... I have seen that with one of the recent snapshot. I thought I was >doing something wrong. > >Also setting CYGWIN=nontsec in the recent snapshot is not helping much. If >I use >Crtl+C to kill a job, often bash will hang for a long time. Yup. If you type CTRL-C and something hangs, it's undoubtely your fault. You've probably disattenuated the potential relegator on your hard disk spin control by excessive use of the control key. This can cause bits to fly out of your hard disk and lodge in your CPU, causing momentary stunning of your CPU. Probably you'll have to reformat your hard drive and possibly even repaint your computer room to fix this problem. Also, remove all cats, as static electricity can be a known cause of all sorts of computer hangs. -chris -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Faylor To: cygwin@sourceware.cygnus.com Subject: Re: xterms and vi Date: Tue, 31 Aug 1999 23:49:00 -0000 Message-ID: <19990811004628.B4110@cygnus.com> References: <19990810234737.25494.rocketmail@web117.yahoomail.com> X-SW-Source: 1999-08n/msg00181.html Message-ID: <19990831234900.3iqSVB87VRhreQxSen8OfPth6lceEoGaW_MMZ7VvYhM@z> On Tue, Aug 10, 1999 at 08:52:09PM -0400, Suhaib M. Siddiqi wrote: >> Note: Make the appropriate backups before installing. >> Strangeness has been >> noted with interactive bash or sh starting another interactive bash or sh >> process which Chris is pulling his hair out trying to fix. > >Hmmm... I have seen that with one of the recent snapshot. I thought I was >doing something wrong. > >Also setting CYGWIN=nontsec in the recent snapshot is not helping much. If >I use >Crtl+C to kill a job, often bash will hang for a long time. Yup. If you type CTRL-C and something hangs, it's undoubtely your fault. You've probably disattenuated the potential relegator on your hard disk spin control by excessive use of the control key. This can cause bits to fly out of your hard disk and lodge in your CPU, causing momentary stunning of your CPU. Probably you'll have to reformat your hard drive and possibly even repaint your computer room to fix this problem. Also, remove all cats, as static electricity can be a known cause of all sorts of computer hangs. -chris -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com