From: Wolfgang Jenkner <wjenkner@inode.at>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 21077@debbugs.gnu.org, Ista Zahn <istazahn@gmail.com>
Subject: bug#21077: 24.5; Slow printing in inferior python buffer with python-shell-enable-font-lock
Date: Sat, 01 Aug 2015 14:42:14 +0200 [thread overview]
Message-ID: <85oair5gex.fsf@iznogoud.viz> (raw)
In-Reply-To: <CA+vqiLGTwe4b+O-1iuiyAwM4W59--V5qjEcmPTkTfsnb4xTvSQ@mail.gmail.com>
On Thu, Jul 30 2015, Stefan Monnier wrote:
> 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.
But comint-output-filter does
(font-lock-prepend-text-property prompt-start (point)
'font-lock-face
'comint-highlight-prompt)
So keyword fontification seems to be inhibited anyway. Is this done in
a particularly inefficient way?
Wolfgang (who ought to go read the source)
next prev parent reply other threads:[~2015-08-01 12:42 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85oair5gex.fsf@iznogoud.viz \
--to=wjenkner@inode.at \
--cc=21077@debbugs.gnu.org \
--cc=istazahn@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.