From: Torsten Mueller <dev-null@shared-files.de>
To: help-gnu-emacs@gnu.org
Subject: Re: CPU maxed out when idling under windows with 22.1
Date: Tue, 05 Jun 2007 13:16:32 +0200 [thread overview]
Message-ID: <uwsyimz1r.fsf@shared-files.de> (raw)
In-Reply-To: mailman.1571.1181036609.32220.help-gnu-emacs@gnu.org
remi.delmas.3000@free.fr wrote:
> I switched to 22.1 win32 stable this morning, and I have the
> following problem : emacs eats 99% CPU when idling, with just two or
> three files opened in c-mode.
What binary do you use? I compiled using MinGW and gcc 3.4.5 this
morning and everything works really fine, even on the first approach.
T.M.
next parent reply other threads:[~2007-06-05 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1571.1181036609.32220.help-gnu-emacs@gnu.org>
2007-06-05 11:16 ` Torsten Mueller [this message]
2007-06-05 18:37 ` CPU maxed out when idling under windows with 22.1 Rémi Delmas
[not found] ` <mailman.1591.1181068669.32220.help-gnu-emacs@gnu.org>
2007-06-05 20:07 ` Jason Rumney
2007-06-05 12:43 ` Chris McMahan
2007-06-05 18:35 ` Rémi Delmas
2007-06-05 9:43 remi.delmas.3000
2007-06-05 10:14 ` Juanma Barranquero
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=uwsyimz1r.fsf@shared-files.de \
--to=dev-null@shared-files.de \
--cc=Urlicht@gmx.net \
--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).