From: "Leo Liou" <leo.liou@centrify.com>
Subject: Problem with python mode
Date: Fri, 31 Mar 2006 08:27:58 -0800 [thread overview]
Message-ID: <D6DE73398967E54096684518594D9931E3ABDB@exch-one.centrify.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 430 bytes --]
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
Thanks :-)
Leo Liou
Not a shred of evidence exists in favor of the notion that life is
serious ...
[-- Attachment #1.2: Type: text/html, Size: 1115 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
next reply other threads:[~2006-03-31 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 16:27 Leo Liou [this message]
[not found] <mailman.242.1143822471.2481.help-gnu-emacs@gnu.org>
2006-03-31 19:35 ` Problem with python mode Marco Gidde
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=D6DE73398967E54096684518594D9931E3ABDB@exch-one.centrify.com \
--to=leo.liou@centrify.com \
/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).