From: Paul Stodghill <stodghil@cs.cornell.edu>
Cc: ding@gnus.org, xemacs-beta@xemacs.org
Subject: Re: XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop
Date: 21 May 2001 15:13:51 -0400 [thread overview]
Message-ID: <yz1g0dy8s6f.fsf@milhouse.cs.cornell.edu> (raw)
In-Reply-To: <4.3.2.7.2.20010521090646.00d66480@san-francisco.beasys.com> (Andy Piper's message of "Mon, 21 May 2001 09:07:34 -0700")
> Try defining BROKEN_SIGIO in your s/cygwin32.h and see how that goes. It will
> enable C-g but led to random lockups last time I tried it.
I installed and tried cygwin 1.3.2 (I presume that this has the signals
changes that were mentioned before). C-g still doesn't work.
I put "#define BROKEN_SIGIO" as the very first line in s/cygwin32.h, did a
"make clean ; make". C-g _still_ doesn't work.
> But we need a crash test dummy ....
I think that I'll put this on my resume. Yow!
next prev parent reply other threads:[~2001-05-21 19:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 13:50 Paul Stodghill
2001-05-21 14:09 ` Hrvoje Niksic
2001-05-21 14:37 ` Josh Huber
2001-05-21 15:05 ` Olivier Fambon
2001-05-21 15:15 ` Paul Stodghill
2001-05-21 16:07 ` Andy Piper
2001-05-21 19:13 ` Paul Stodghill [this message]
2001-05-21 19:14 ` Paul Stodghill
2001-05-28 17:45 ` fill bug still there [Re: XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop] Paul Stodghill
2001-05-29 17:20 ` Simon Josefsson
2001-05-29 17:24 ` Paul Stodghill
2001-05-29 17:22 ` Kai Großjohann
2001-05-29 17:26 ` Paul Stodghill
2001-05-29 17:50 ` Kai Großjohann
2001-05-29 17:56 ` Paul Stodghill
2001-05-27 3:38 ` critical quit Re: XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop Ben Wing
2001-05-28 17:44 ` Paul Stodghill
2001-05-30 1:28 ` Ben Wing
2001-05-30 7:08 ` Wow Ken McGlothlen
2001-05-30 9:26 ` Wow Kai Großjohann
2001-05-30 21:19 ` Wow Ken McGlothlen
2001-05-30 21:26 ` Wow Kai Großjohann
2001-05-31 9:10 ` Wow Steinar Bang
2001-06-01 21:30 ` Wow Ken McGlothlen
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=yz1g0dy8s6f.fsf@milhouse.cs.cornell.edu \
--to=stodghil@cs.cornell.edu \
--cc=ding@gnus.org \
--cc=xemacs-beta@xemacs.org \
/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 NNTP newsgroup(s).