Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Mon, 18 Nov 2002 11:53:52 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Hey hey, I now have the emacs 100% cpu usage bug too [CGF, this one is for you] Message-ID: <20021118165352.GC30780@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20021115220304 DOT GE27413 AT redhat DOT com> <20021115230010 DOT 50079 DOT qmail AT web20809 DOT mail DOT yahoo DOT com> <20021116041055 DOT GA31944 AT redhat DOT com> <20021116065905 DOT GB12422 AT redhat DOT com> <024701c28f21$d91c79d0$0b00d5c0 AT cipi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <024701c28f21$d91c79d0$0b00d5c0@cipi> User-Agent: Mutt/1.5.1i On Mon, Nov 18, 2002 at 06:45:05PM +0200, Ciprian Ciubotariu wrote: >I can also send you the full log if necessary. > >FYI, (and hoping I'll get back my beloved emacs :) Did you actually read all of the messages in this thread or just some of them? The problem has been identified and fixed and a proposed update is available in the latest snapshot. If you are going to report a problem like this, you owe it to yourself and to the community to either try any solution that was offered in the email or, if you actually have tried it, to specifically report that fact rather than let us read between the lines. Since you didn't indicate that you'd tried a cygwin snapshot, I'm going to assume that you just thought you had to read email reporting the bug and ignored email where it was mentioned that the bug was fixed. cgf -- Please do not send me personal email with cygwin questions or observations. Use the resources at http://cygwin.com/ . -- 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/