From: bojohan+news@dd.chalmers.se (Johan Bockgård)
To: help-gnu-emacs@gnu.org
Subject: Re: Excess CPU usage during idle, Carbon Emacs
Date: Sat, 19 May 2007 16:21:09 +0200 [thread overview]
Message-ID: <yoijps4wq4h6.fsf@gamma02.me.chalmers.se> (raw)
In-Reply-To: mailman.857.1179581614.32220.help-gnu-emacs@gnu.org
Fred Seibel <fseibel@sprintmail.com> writes:
> Running the Spring release of Carbon Emacs on an Intel Core 2 Duo
> powerbook, I have noticed that the fan stops running shortly after
> exiting emacs. The Activity Monitor shows emacs running at nearly
> 100% even after an extended idle period. I presume this is
> contributing to a faster than necessary drain on the battery. Any
> ideas about the cause of this behavior and how to cure it?
Maybe this?
http://lists.gnu.org/archive/html/emacs-pretest-bug/2006-10/msg00016.html
--
Johan Bockgård
next parent reply other threads:[~2007-05-19 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.857.1179581614.32220.help-gnu-emacs@gnu.org>
2007-05-19 14:21 ` Johan Bockgård [this message]
2007-05-19 4:43 Excess CPU usage during idle, Carbon Emacs Fred Seibel
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=yoijps4wq4h6.fsf@gamma02.me.chalmers.se \
--to=bojohan+news@dd.chalmers.se \
--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).