all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maciej Katafiasz <mathrick@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: opening makefile with error message.
Date: Wed, 9 May 2007 22:06:45 +0000 (UTC)	[thread overview]
Message-ID: <f1tgll$u3n$2@sea.gmane.org> (raw)
In-Reply-To: 1178729045.216843.133720@h2g2000hsg.googlegroups.com

Den Wed, 09 May 2007 09:44:05 -0700 skrev bpatton:

> Fontifying region...(error No match 2 in highlight (2 font-lock-
> variable-name-face))
> 
> I have a makefile that I originally created with gvim.  I've since
> switched to GNU emacs.
> I kept getting the error above, so I commented out every line in the
> file.  Thinking I could uncomment a few lines at a time to find the
> problem.
> First line brought the problem
> include makefile.definitions
> 
> I don't understand the error message

It seems that some part of font-lock is requesting the second submatch (in
a regex, ie. the match for the second parenthesised part), which wasn't
found. Hard to say why exactly that is, might be that some regex there is
malformed, or maybe someone forgot to catch errors somewhere. The best
starting point is to make a minimal file that triggers that, then turn on
debugger on error, and see where exactly it dies and figure out why.
Reading elisp manual to see how exactly font-lock does its thing will
probably help, I myself never needed that, so I have no idea.

Cheers,
Maciej

PS. That's kinda obvious, but you really want to have source (ie. the .el
files, not just compiled .elc) before you start poking at it, otherwise
any debugging is kinda pointless and impossible. This is important if you
use a distro-packaged emacs, since they split out source .el into a
separate package.

      reply	other threads:[~2007-05-09 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09 16:44 opening makefile with error message bpatton
2007-05-09 22:06 ` Maciej Katafiasz [this message]

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='f1tgll$u3n$2@sea.gmane.org' \
    --to=mathrick@gmail.com \
    --cc=help-gnu-emacs@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 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.