Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 14 Nov 2002 12:28:50 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: patched cygwin emacs available (for signal looping problem)
Message-ID:	<20021114172850.GB1550@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<ar0fgk$m93$1 AT main DOT gmane DOT org>
Mime-Version:	1.0
In-Reply-To:	<ar0fgk$m93$1@main.gmane.org>
User-Agent:	Mutt/1.5.1i

On Thu, Nov 14, 2002 at 10:31:09AM -0500, Joe Buehler wrote:
>Would those people having a problem with the Cygwin emacs
>going into an infinite signal loop please try testing the
>new emacs binaries that can be found at the following location?
>
>http://68.98.180.124:3000/cygwin/emacs/
>
>No guarantee that it will fix anything, but I have applied a patch
>that was necessary to fix a similar problem under a version of UNIX.
>
>If this fixes anything, I will release a new version of emacs for
>Cygwin.

There is a new cygwin snapshot which *may* fix this behavior, too.
Please try it.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -