unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marco Gidde <marco.gidde@tiscali.de>
Subject: Re: Problem with python mode
Date: Fri, 31 Mar 2006 21:35:39 +0200	[thread overview]
Message-ID: <85sloyif04.fsf@tristan.br-automation.com> (raw)
In-Reply-To: mailman.242.1143822471.2481.help-gnu-emacs@gnu.org

"Leo Liou" <leo.liou@centrify.com> writes:

> Several times now, when I am editing .py file, inexplicably, the mini buffer
> would show "Forced full reparse", CPU spikes to 100%, and never come out of
> it. Feels like a infinite loop. I had to kill emacs from another windows.
> Anyone have seen this? What is the resolution?
>
> SuSE    9.1
> Emacs   21.3.1
> Py-mode 4.35

If you are using the sematic package you might take a look into their
mailing list archive. I think there was an issue a few months ago.


Regards,

Marco Gidde

       reply	other threads:[~2006-03-31 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.242.1143822471.2481.help-gnu-emacs@gnu.org>
2006-03-31 19:35 ` Marco Gidde [this message]
2006-03-31 16:27 Problem with python mode Leo Liou

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=85sloyif04.fsf@tristan.br-automation.com \
    --to=marco.gidde@tiscali.de \
    /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).