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: Tue, 17 Feb 2004 15:01:31 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: EMACS problems with cygwin 1.5.7.1 Message-ID: <20040217200130.GA32302@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin@cygwin.com On Tue, Feb 17, 2004 at 02:30:25PM -0500, Thomas L Roche wrote: >That being said, emacs is still not nearly as stable now as it was on >1.5.5-1--in fact, I got an exit 128 (haven't seen one of those before, >usually it's just SEGVs) while composing this reply. So while I don't >believe Plager's response (dropping back to 1.5.5-1) was optimal, I >can see why one might choose that route. Instead I hope to debug emacs >after the unzip problem (which more directly harms my productivity) is >fixed I don't know if I have mentioned this but since I don't use emacs, barring any debugging of the problem or reproducible test case, this breakage will also be in cygwin 1.5.8. If you or someone is going to debug this then it will have to be quick. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/