From: Jason Rumney <jasonrumney@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs using 99 percent of winxp resources
Date: 27 May 2007 00:47:56 -0700 [thread overview]
Message-ID: <1180252076.734670.287460@q69g2000hsb.googlegroups.com> (raw)
In-Reply-To: <4658139d_3@mk-nntp-2.news.uk.tiscali.com>
On 26 May, 12:01, David R <angel_ov_no...@tiscali.co.uk> wrote:
> (add-to-list 'load-path "~/.emacs.d/cedet-1.0pre3")
> (add-to-list 'load-path "~/.emacs.d/cedet-1.0pre3/common")
> (require 'cedet)
cedet-1.0pre3 has a bug in it that causes 100% CPU usage while Emacs
is idle. You need to pull the latest revision of semantic-idle.el
from the cedet CVS to fix it.
I don't know when the cedet author plans to release a new version, but
this problem has been known about and fixed in CVS for some time now.
next prev parent reply other threads:[~2007-05-27 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 11:01 emacs using 99 percent of winxp resources David R
2007-05-26 12:16 ` David Kastrup
2007-05-26 16:05 ` David R
2007-05-27 7:47 ` Jason Rumney [this message]
2007-05-28 22:50 ` David R
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1180252076.734670.287460@q69g2000hsb.googlegroups.com \
--to=jasonrumney@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).