From: LonelyStar <emacs@lonely-star.org>
Subject: Emacs taking very much cpu with semantic-idle-scheduler-time
Date: Tue, 5 Sep 2006 16:37:05 -0700 (PDT) [thread overview]
Message-ID: <6162482.post@talk.nabble.com> (raw)
Hello together,
When I leave emacs alone for a moment, it takes very cpu-time and some cpu
consuming applications (like i.E. games) loose resposivness.
The problem disapears if I set "semantic-idle-scheduler-idle-time" to a very
high value (so that it just does not happen).
Also: If I execute "semantic-complete-analyze-inline", emacs is busy for
quite long (maybe a minute) before giving me a message.
I am using the CVS version (22.0.50.1) with cedet.
Any Idea what coul be wrong?
Thanks!
Nathan
--
View this message in context: http://www.nabble.com/Emacs-taking-very-much-cpu-with-semantic-idle-scheduler-time-tf2224042.html#a6162482
Sent from the Emacs - Help forum at Nabble.com.
next reply other threads:[~2006-09-05 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 23:37 LonelyStar [this message]
[not found] <mailman.6449.1157499431.9609.help-gnu-emacs@gnu.org>
2006-09-06 7:11 ` Emacs taking very much cpu with semantic-idle-scheduler-time David Kastrup
2006-09-06 8:53 ` RolandK
2006-09-06 12:15 ` LonelyStar
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=6162482.post@talk.nabble.com \
--to=emacs@lonely-star.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).