unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Mackenzie <acm@muc.de>
Cc: bug-cc-mode@gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs revision #107149
Date: Sat, 11 Feb 2012 16:56:53 +0100	[thread overview]
Message-ID: <87pqdlbby2.fsf@gnus.org> (raw)
In-Reply-To: <20120210232039.GC4340@acm.acm> (Alan Mackenzie's message of "Fri, 10 Feb 2012 23:20:39 +0000")

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.
Since it's that hook that sets
`c-standard-font-lock-fontify-region-function' (which is nil by
default), this breaks when viewing C mode files.

Is there any reason why `c-standard-font-lock-fontify-region-function'
is nil, when this makes just calling `(font-lock-fontify-buffer)' not
work?  All the other modes seem to work fine.

-- 
(domestic pets only, the antidote for overdose, milk.)
  http://lars.ingebrigtsen.no  *  Sent from my Rome



  reply	other threads:[~2012-02-11 15:56 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 [this message]
2012-02-11 18:07   ` Wolfgang Jenkner
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

  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=87pqdlbby2.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=acm@muc.de \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@gnu.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 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).