From: Chris Faylor <cgf@cygnus.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: xterms and vi
Date: Tue, 10 Aug 1999 21:44:00 -0000 [thread overview]
Message-ID: <19990811004628.B4110@cygnus.com> (raw)
In-Reply-To: <LOBBLPGIHMIEGBEAFDMCMEIFCAAA.ssiddiqi@ipass.net>
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
WARNING: multiple messages have this Message-ID
From: Chris Faylor <cgf@cygnus.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: xterms and vi
Date: Tue, 31 Aug 1999 23:49:00 -0000 [thread overview]
Message-ID: <19990811004628.B4110@cygnus.com> (raw)
Message-ID: <19990831234900.3iqSVB87VRhreQxSen8OfPth6lceEoGaW_MMZ7VvYhM@z> (raw)
In-Reply-To: <LOBBLPGIHMIEGBEAFDMCMEIFCAAA.ssiddiqi@ipass.net>
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
next prev parent reply other threads:[~1999-08-10 21:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-10 16:47 Earnie Boyd
1999-08-10 17:49 ` Glenn Spell
1999-08-10 21:36 ` Chris Faylor
1999-08-31 23:49 ` Chris Faylor
1999-08-31 23:49 ` Glenn Spell
1999-08-10 17:52 ` Suhaib M. Siddiqi
1999-08-10 21:44 ` Chris Faylor [this message]
1999-08-31 23:49 ` Chris Faylor
1999-08-31 23:49 ` Suhaib M. Siddiqi
1999-08-11 10:48 ` Geoff Hart
1999-08-31 23:49 ` Geoff Hart
1999-08-31 23:49 ` Earnie Boyd
-- strict thread matches above, loose matches on Subject: below --
1999-08-10 15:08 Geoff Hart
1999-08-31 23:49 ` Geoff Hart
1999-07-15 6:38 Ryan L McFall
1999-07-15 7:17 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Suhaib M. Siddiqi
1999-07-15 11:52 ` Chris Faylor
1999-07-16 8:10 ` Ryan L McFall
1999-07-31 18:34 ` Ryan L McFall
1999-07-31 18:34 ` Chris Faylor
1999-07-31 18:34 ` Ryan L McFall
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=19990811004628.B4110@cygnus.com \
--to=cgf@cygnus.com \
--cc=cygwin@sourceware.cygnus.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).