Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 14 Nov 2002 13:41:11 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: patched cygwin emacs available (for signal looping problem) Message-ID: <20021114184111.GB15314@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20021114172850.GB1550@redhat.com> <4515-Thu14Nov2002182404+0000-starksb@ebi.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4515-Thu14Nov2002182404+0000-starksb@ebi.ac.uk> User-Agent: Mutt/1.5.1i On Thu, Nov 14, 2002 at 06:24:04PM +0000, David Starks-Browning wrote: >On Thursday 14 Nov 02, Christopher Faylor writes: >> 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. > >No, I tried it, it does not help. Well, that's wonderful. One report of "It works, sort of" and one of "It doesn't fix the problem 100%". 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/