From: Charles Plager <cplager+cygwin@physics.ucla.edu>
To: Cygwin Mailing list <cygwin@cygwin.com>
Subject: Problems with Emacs - Resolution(?)
Date: Fri, 13 Feb 2004 14:32:00 -0000 [thread overview]
Message-ID: <402CDE1F.40605@physics.ucla.edu> (raw)
To summarize:
Due to (self-inflicted) problems, I did a fresh install of cygwin to
1.5.7.1.
Emacs started behaving very strange:
* Random crashes
* Suddenly taking up 100% of cpu
This happened with all emacs versions I could get my hands on:
* 21.2.9
* 21.2.11
* 21.2.12
Earlier this week, I downgraded to cygwin 1.5.5.1 (I needed to downgrade
ash to 20031007-1). Since then I have had no problems with emacs.
So, to my untrained eye, it looks like something in the new cygwin dll
doesn't like emacs.
Charles
--
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/
next reply other threads:[~2004-02-13 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 14:32 Charles Plager [this message]
2004-02-14 15:39 ` Ehud Karni
2004-02-14 18:34 ` Ehud Karni
2004-02-25 15:59 ` Joe Buehler
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=402CDE1F.40605@physics.ucla.edu \
--to=cplager+cygwin@physics.ucla.edu \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).