From: Eli Zaretskii <eliz@gnu.org>
To: Ista Zahn <istazahn@gmail.com>
Cc: 21077@debbugs.gnu.org
Subject: bug#21077: 24.5; Slow printing in inferior python buffer with python-shell-enable-font-lock
Date: Thu, 16 Jul 2015 21:34:20 +0300 [thread overview]
Message-ID: <83615k6jf7.fsf@gnu.org> (raw)
In-Reply-To: <CA+vqiLGTwe4b+O-1iuiyAwM4W59--V5qjEcmPTkTfsnb4xTvSQ@mail.gmail.com>
> From: Ista Zahn <istazahn@gmail.com>
> Date: Thu, 16 Jul 2015 12:42:39 -0400
>
> 1. Start emacs with 'emacs -Q'
> 2. Start inferior python process with 'M-x run-python'
> 3. Run 'print(list(range(9999)))' in the *Python* buffer
>
> Result: emacs grinds to a halt and has to be killed.
No, it doesn't: it just becomes very slow, and you need to wait longer
for it to finish. In my case, it took a whopping 14 minutes, and
produced this in the *Messages* buffer:
Error during redisplay: (jit-lock-function 52112) signaled (error "Stack overflow in regexp matcher")
Error during redisplay: (jit-lock-function 56220) signaled (error "Stack overflow in regexp matcher")
Error during redisplay: (jit-lock-function 57879) signaled (error "Stack overflow in regexp matcher")
next prev parent reply other threads:[~2015-07-16 18:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 16:42 bug#21077: 24.5; Slow printing in inferior python buffer with python-shell-enable-font-lock Ista Zahn
2015-07-16 18:34 ` Eli Zaretskii [this message]
2015-07-16 19:09 ` Ista Zahn
2015-07-16 19:34 ` Eli Zaretskii
2015-07-16 19:50 ` Ista Zahn
2015-07-17 6:53 ` Eli Zaretskii
2015-07-17 8:33 ` Stefan Monnier
2015-07-17 8:56 ` Rasmus
2015-07-29 20:50 ` Ista Zahn
2015-07-30 23:19 ` Stefan Monnier
2015-07-31 0:27 ` Ista Zahn
2015-07-31 22:07 ` Stefan Monnier
2015-08-01 1:46 ` Ista Zahn
2015-08-01 12:36 ` Wolfgang Jenkner
2015-08-01 16:26 ` Ista Zahn
2015-08-03 23:57 ` Wolfgang Jenkner
2016-07-14 1:31 ` npostavs
2015-08-01 12:42 ` Wolfgang Jenkner
2015-08-03 21:41 ` Stefan Monnier
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=83615k6jf7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21077@debbugs.gnu.org \
--cc=istazahn@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).