unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: an0 <an00na@gmail.com>
To: "Alan Mackenzie" <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: font-lock-extend-region-multiline: Args out of range: 0, 0
Date: Tue, 8 Apr 2008 21:10:28 +0800	[thread overview]
Message-ID: <98e737510804080610t554aa26bwf0896d692b9a3580@mail.gmail.com> (raw)
In-Reply-To: <20080408131112.GD2937@muc.de>

Yes, it occurs in trunk head.
And it seems you've figure out the cause so that I'm not giving any
more detailed information here.
Hope you and Stefan could fix this asap.
Thanks.

On Tue, Apr 8, 2008 at 9:11 PM, Alan Mackenzie <acm@muc.de> wrote:
> Hi, Stefan and Emacs!
>
>
>  > On Tue, Apr 08, 2008 at 10:35:57AM +0800, an0 wrote:
>  >> I met this error [font-lock-extend-region-multiline: Args out of
>  >> range: 0, 0] when I use `smart-compile' on a cpp file.
>
>  This error happens in very recent CVS Emacsen because CC Mode has just
>  started using font-lock-after-change-extend-region-function.  This
>  variable is not buffer local, and it thus fouled up the compilation log
>  buffer.
>
>  Stefan, this variable was originally buffer local.  When you moved it
>  from font-core.el V1.41 to font-lock.el V1.299 on 2006-08-01, you
>  removed the buffer locality (modifying the doc string to indicate this).
>  Can you remember why?
>
>  I can't see any reason why it would ever be useful for
>  font-lock-after-change-extend-region-function not to be buffer local.  I
>  think it would be best to make it buffer local in font-lock.el.
>
>  --
>  Alan Mackenzie (Nuremberg, Germany).
>




  reply	other threads:[~2008-04-08 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08  2:35 font-lock-extend-region-multiline: Args out of range: 0, 0 an0
2008-04-08  6:04 ` David Hansen
2008-04-08  9:29 ` Alan Mackenzie
2008-04-08  9:36   ` David Hansen
2008-04-08 13:11     ` Alan Mackenzie
2008-04-08 13:10       ` an0 [this message]
2008-04-08 22:12       ` Johan Bockgård

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=98e737510804080610t554aa26bwf0896d692b9a3580@mail.gmail.com \
    --to=an00na@gmail.com \
    --cc=acm@muc.de \
    --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).