unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Alan Mackenzie <acm@muc.de>
Cc: Juanma Barranquero <lekktu@gmail.com>,
	Paul Eggert <eggert@cs.ucla.edu>,
	14886@debbugs.gnu.org
Subject: bug#14886: Fwd: bug#14886: Fwd: A significant slowdown calling font-lock-fontify-buffer from a hook
Date: Sat, 27 Jul 2013 12:20:38 +0200	[thread overview]
Message-ID: <51F39EF6.8050408@gmx.at> (raw)
In-Reply-To: <20130727093556.GA3616@acm.acm>

 > I've tried a brief ediff between the font-lock files in 24.3 and trunk,
 > but haven't spotted the difference yet in font-lock-fontify-buffer which
 > I suspect is there.

Why should there be any difference?  The value that differs is that of
`font-lock-fontify-buffer-function'.  Calling `font-lock-fontify-buffer'
from prog-mode does `font-lock-default-fontify-buffer'.  Calling it from
c-mode does `jit-lock-refontify'.  Or what am I missing?

martin





  parent reply	other threads:[~2013-07-27 10:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAeL0SSqSShXtsnqfkiF3H9n+OxYwuJ4yi6ci=wwfdnb8JpqcQ@mail.gmail.com>
     [not found] ` <83ip0a2xlb.fsf@gnu.org>
     [not found]   ` <CAAeL0SQXebErPFigy5q03fPprJN+g6C=itt4as8vJ7JGMMDL7Q@mail.gmail.com>
     [not found]     ` <83ehay2vgw.fsf@gnu.org>
2013-07-16 23:03       ` bug#14886: Fwd: A significant slowdown calling font-lock-fontify-buffer from a hook Juanma Barranquero
2013-07-17  3:05         ` Juanma Barranquero
2013-07-17  4:02           ` Eli Zaretskii
2013-07-17  9:04             ` Juanma Barranquero
2013-07-17 11:42               ` Juanma Barranquero
2013-07-17 12:50                 ` Paul Eggert
2013-07-17 13:43                   ` Juanma Barranquero
2013-07-17 13:59                     ` Paul Eggert
2013-07-17 15:19                     ` Juanma Barranquero
2013-07-17 15:57                     ` Glenn Morris
2013-07-17 16:56                       ` Juanma Barranquero
2013-07-22  4:20                   ` Stefan Monnier
2013-07-22 22:11                     ` Juanma Barranquero
     [not found]                       ` <CAAeL0STtrBnWTbc0FSPn6XHArcDtxHwzNVaijvyG5bVKMLRo+w@mail.gmail.com>
2013-07-24 19:30                         ` bug#14886: Fwd: " Alan Mackenzie
2013-07-24 21:29                           ` Juanma Barranquero
2013-07-25  1:24                             ` Stefan Monnier
2013-07-25  6:53                               ` Juanma Barranquero
2013-07-26 19:44                                 ` Alan Mackenzie
2013-07-26 21:32                                   ` Juanma Barranquero
2013-07-27  9:35                                     ` Alan Mackenzie
2013-07-27 10:10                                       ` Juanma Barranquero
2013-07-27 10:20                                       ` martin rudalics [this message]
2013-07-27 14:03                                         ` Stefan Monnier
2013-07-28  9:58                                         ` Alan Mackenzie
2019-10-30 12:52                                           ` Lars Ingebrigtsen
2013-07-17 15:04               ` Eli Zaretskii
2013-07-17 15:16                 ` Juanma Barranquero

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=51F39EF6.8050408@gmx.at \
    --to=rudalics@gmx.at \
    --cc=14886@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=eggert@cs.ucla.edu \
    --cc=lekktu@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).