unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Daniel Colascione <dancol@dancol.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-24 d69e9f1: CC Mode: Stop Font Lock forcing fontification from BOL. Fixes debbugs#19669.
Date: Thu, 19 Mar 2015 09:31:11 +0000	[thread overview]
Message-ID: <20150319093110.GA2753@acm.fritz.box> (raw)
In-Reply-To: <550A43BB.3070904@dancol.org>

Hello, Daniel.

On Wed, Mar 18, 2015 at 08:34:19PM -0700, Daniel Colascione wrote:
> On 03/18/2015 05:08 AM, Alan Mackenzie wrote:
> > On Mon, Mar 16, 2015 at 04:53:28PM -0700, Daniel Colascione wrote:
> >> On 02/01/2015 01:22 PM, Alan Mackenzie wrote:
> >>> branch: emacs-24
> >>> commit d69e9f1c24f37f36af33b0468c5a4e100dbb09b6
> >>> Author: Alan Mackenzie <acm@muc.de>
> >>> Commit: Alan Mackenzie <acm@muc.de>

> >>>     CC Mode: Stop Font Lock forcing fontification from BOL.  Fixes debbugs#19669.

> >>>     cc-mode.el (c-font-lock-init): Setq font-lock-extend-region-functions to
> >>>     nil.

> >> This change is driving me nuts.  Consider the following buffer, with @
> >> representing point:

> >> void foo() {
> >>   @
> >> }

> >> If I type [f o r SPC], then depending on timing, I see only the "or", or
> >> only the "r", fontified in font-lock-keyword-face. A moment later,
> >> jit-lock kicks in and refontifies the entire chunk properly.

> > Sorry about this.

> >> Can we please extend the start of the region back to at least the last `}'?

> > This could be a tricky one to solve.  For the sake of your sanity, please
> > consider applying the following temporary patch; it "solves" the current
> > problem, but unfortunately leaves bug #19669's symptoms apparent again.

> I've been doing the equivalent in a mode hook. I'm not sure that
> reverting to the previous behavior is the right thing either.
> Fundamentally, it just feels wrong that the solution to any
> fontification correctness bug should be to fontify less.

The problem in #19669 was that Font Lock's extension of the region to be
font locked to the beginning of the line was changing the syntactic
context, hence CC Mode's font locking didn't work in that case.  The
solution was to prevent that extension in the pertinent case.  However, I
got it wrong.

The solution I'm looking at at the moment is to allow Font Lock to extend
to BOL except where CC Mode itself has extended the region for syntactic
reasons.  As I said, it's tricky.

Fundamentally, the problem is that Font Lock doesn't distinguish between
the region which needs fontifying, and the region which supplies the
syntactic context.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2015-03-19  9:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150201212213.17840.3710@vcs.savannah.gnu.org>
     [not found] ` <E1YI1y9-0004eO-Re@vcs.savannah.gnu.org>
2015-02-02 18:50   ` [Emacs-diffs] emacs-24 d69e9f1: CC Mode: Stop Font Lock forcing fontification from BOL. Fixes debbugs#19669 Stefan Monnier
2015-02-02 19:27     ` Alan Mackenzie
2015-02-03  2:12       ` Stefan Monnier
2015-02-02 18:54   ` Stefan Monnier
2015-02-02 21:39     ` Alan Mackenzie
2015-02-03  2:26       ` Stefan Monnier
2015-02-07 12:27         ` Alan Mackenzie
2015-02-07 15:29           ` Stefan Monnier
2015-02-07 15:40             ` Alan Mackenzie
2015-03-16 23:53   ` Daniel Colascione
2015-03-18 12:08     ` Alan Mackenzie
2015-03-19  3:34       ` Daniel Colascione
2015-03-19  9:31         ` Alan Mackenzie [this message]
2015-03-19 13:49           ` Stefan Monnier
2015-03-19 20:37             ` Alan Mackenzie
2015-03-19 20:56               ` Stefan Monnier
2015-03-20 16:30                 ` Alan Mackenzie
2015-03-20 16:34                   ` Daniel Colascione
2015-03-20 17:29                     ` Alan Mackenzie
2015-03-20 21:25                       ` Daniel Colascione
2015-03-20 22:30                         ` Alan Mackenzie
2015-03-20 18:05                   ` Stefan Monnier
2015-03-20 21:12                     ` Alan Mackenzie
2015-03-20 22:01                       ` Stefan Monnier
2015-03-30 16:44     ` 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=20150319093110.GA2753@acm.fritz.box \
    --to=acm@muc.de \
    --cc=dancol@dancol.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).