all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Wolfgang Jenkner <wjenkner@inode.at>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: bug-cc-mode@gnu.org, Alan Mackenzie <acm@muc.de>,
	Katsumi Yamaoka <yamaoka@jpl.org>,
	emacs-devel@gnu.org
Subject: Re: Emacs revision #107149
Date: Sat, 11 Feb 2012 19:07:14 +0100	[thread overview]
Message-ID: <858vk9utv1.fsf@iznogoud.viz> (raw)
In-Reply-To: 87pqdlbby2.fsf@gnus.org

On Sat, Feb 11 2012, Lars Ingebrigtsen wrote:

> Alan Mackenzie <acm@muc.de> writes:
>
>> Why, should the case be, would you want to call font-lock-fontify-buffer
>> without initialising font lock mode first?  Would this not, perhaps,
>> indicate some other problem in mm-inline-text?
>
> mm sets `font-lock-mode-hook' (and friends) to nil to avoid problems
> when calling `(font-lock-fontify-buffer)', if I remember correctly.

I think the point is to inhibit anything that could delay fontification.

Please see (the whole) bug#10063 thread [1].  The bogus buffer local
binding of font-lock-mode-hook in mm-display-inline-fontify is still
there, by the way.

[1] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10063

Wolfgang



  reply	other threads:[~2012-02-11 18:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 23:20 Emacs revision #107149 Alan Mackenzie
2012-02-11 15:56 ` Lars Ingebrigtsen
2012-02-11 18:07   ` Wolfgang Jenkner [this message]
2012-02-11 19:59   ` Alan Mackenzie
2012-02-12 20:42     ` Lars Ingebrigtsen
2012-02-12 22:22       ` Alan Mackenzie
2012-02-13  1:00         ` Wolfgang Jenkner
2012-02-13 21:35           ` Alan Mackenzie
2012-02-13  3:15         ` Stefan Monnier
2012-02-13 21:42           ` Alan Mackenzie
2012-02-13 22:18             ` Stefan Monnier
2012-02-13 21:03         ` Lars Ingebrigtsen
2012-02-13 22:07           ` Alan Mackenzie
2012-02-20  9:51             ` Lars Ingebrigtsen
2012-02-21 15:16               ` Alan Mackenzie

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=858vk9utv1.fsf@iznogoud.viz \
    --to=wjenkner@inode.at \
    --cc=acm@muc.de \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=yamaoka@jpl.org \
    /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.