unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ista Zahn <istazahn@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 21077@debbugs.gnu.org
Subject: bug#21077: 24.5; Slow printing in inferior python buffer with python-shell-enable-font-lock
Date: Thu, 30 Jul 2015 20:27:15 -0400	[thread overview]
Message-ID: <CA+vqiLF-e5_tjyi+=4urc2p0Ymm5h2bpzvephXq0+LW6AOJURQ@mail.gmail.com> (raw)
In-Reply-To: <jwvh9olck2o.fsf-monnier+emacsbugs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

On Jul 30, 2015 7:19 PM, "Stefan Monnier" <monnier@iro.umontreal.ca> wrote:
>
> > Sorry for the delay in responding. I think a reasonable short term
> > measure is to set python-shell-enable-font-lock to nil by default, and
> > perhaps add a warning to the doc string to the effect that setting it
> > to a non-nil value can dramatically slow down printing.
>
> As mentioned, font-lock is but one of the parts of Emacs that slow down
> as lines get longer.

python-shell-enable-font-lock is the only place I've encountered were
things become unusable. I'm not all that concerned with things slowing down
slightly, but I do think the cases (like this one) that render emacs
unusable need to be fixed or worked around.
>
> In the case of comint modes, rather than disable font-lock we should
> refrain from font-locking the text after the last \n (since that's the
> line that keeps getting expanded, so we end up re-font-locking it O(N)
> times for a line of length N, for a total amount of work of O(N^2)).
> IIRC I have a similar hack in grep.el or compile.el.

OK, but unless there are clear plans to fix this soon the default value of
python-shell-enable-font-lock should be changed to nil until such time as a
fix is in place.

Best,
Ista
>
>
>         Stefan

[-- Attachment #2: Type: text/html, Size: 1578 bytes --]

  reply	other threads:[~2015-07-31  0:27 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
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 [this message]
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='CA+vqiLF-e5_tjyi+=4urc2p0Ymm5h2bpzvephXq0+LW6AOJURQ@mail.gmail.com' \
    --to=istazahn@gmail.com \
    --cc=21077@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).