From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.bugs Subject: bug#14325: 24.3; cc-mode does not initialize correctly w/ -batch Date: Wed, 01 May 2013 13:59:49 -0400 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1367431243 21430 80.91.229.3 (1 May 2013 18:00:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 1 May 2013 18:00:43 +0000 (UTC) Cc: 14325@debbugs.gnu.org To: Alan Mackenzie Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed May 01 20:00:41 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UXbKa-0001mm-Nn for geb-bug-gnu-emacs@m.gmane.org; Wed, 01 May 2013 20:00:40 +0200 Original-Received: from localhost ([::1]:39002 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UXbKa-0003vu-DY for geb-bug-gnu-emacs@m.gmane.org; Wed, 01 May 2013 14:00:40 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:41224) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UXbKW-0003vj-Ud for bug-gnu-emacs@gnu.org; Wed, 01 May 2013 14:00:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UXbKV-0002ga-72 for bug-gnu-emacs@gnu.org; Wed, 01 May 2013 14:00:36 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:50030) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UXbKT-0002fy-Iw; Wed, 01 May 2013 14:00:33 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1UXbKw-0004Cm-1Z; Wed, 01 May 2013 14:01:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Glenn Morris Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org, bug-cc-mode@gnu.org Resent-Date: Wed, 01 May 2013 18:01:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 14325 X-GNU-PR-Package: emacs,cc-mode X-GNU-PR-Keywords: Original-Received: via spool by 14325-submit@debbugs.gnu.org id=B14325.136743122316100 (code B ref 14325); Wed, 01 May 2013 18:01:02 +0000 Original-Received: (at 14325) by debbugs.gnu.org; 1 May 2013 18:00:23 +0000 Original-Received: from localhost ([127.0.0.1]:54139 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1UXbKI-0004Bc-Fl for submit@debbugs.gnu.org; Wed, 01 May 2013 14:00:22 -0400 Original-Received: from fencepost.gnu.org ([208.118.235.10]:49293) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1UXbKG-0004BT-Pb for 14325@debbugs.gnu.org; Wed, 01 May 2013 14:00:21 -0400 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1UXbJl-0003w7-Pc; Wed, 01 May 2013 13:59:49 -0400 X-Spook: [Hello to all my friends and fans in domestic X-Ran: CS20Z:t03a%W@ITdYd7mA({.o.WPB;xm9>HA3~_?|D3MnKh;lQd|:(+Js^cZs;?^.@#j<7 X-Hue: blue X-Attribution: GM In-Reply-To: (Alan Mackenzie's message of "Wed, 1 May 2013 12:53:28 +0000 (UTC)") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:73874 Archived-At: Alan Mackenzie wrote: > However, you'll probably prefer to carry on with using Font Lock Mode > uninitialised. ;-) I think Glenn's patch achieves this painlessly. That patch seems like TRT to me anyway. What problem is c-standard-font-lock-fontify-region-function supposed to solve? Someone changing the default value of font-lock-fontify-region-function in between font-lock-mode-hook being run and font-lock-fontify-region being called? That shouldn't happen, only the buffer-local value should ever be changed. It's not a user-variable. (I actually think you could safely just call font-lock-default-fontify-region .)