From: Michael Heerdegen <michael_heerdegen@web.de>
To: Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: High CPU load after pressing arbitrary key (mostly in C mode)
Date: Fri, 19 Aug 2011 19:15:19 +0200 [thread overview]
Message-ID: <878vqpb9w8.fsf@web.de> (raw)
In-Reply-To: <mailman.1500.1313609268.939.help-gnu-emacs@gnu.org> (Michal Sojka's message of "Wed, 17 Aug 2011 17:56:41 +0200")
Hi,
just guessing: such an effect can be caused by settings that cause
frequent updating of the mode-line, like setting `display-time-interval'
to 1 or so. Every redisplay of the mode-line causes the global menu
structure to be recalculated. Do you define own menus?
Michael.
next parent reply other threads:[~2011-08-19 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1500.1313609268.939.help-gnu-emacs@gnu.org>
2011-08-19 17:15 ` Michael Heerdegen [this message]
2011-08-17 15:56 High CPU load after pressing arbitrary key (mostly in C mode) Michal Sojka
2011-08-18 11:59 ` suvayu ali
2011-08-18 12:08 ` Michal Sojka
2011-08-18 12:17 ` suvayu ali
2011-08-18 12:43 ` Michal Sojka
2011-08-18 13:11 ` suvayu ali
2011-08-19 20:48 ` Ian Zimmerman
2011-08-22 14:49 ` Michal Sojka
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=878vqpb9w8.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).