* opening makefile with error message.
@ 2007-05-09 16:44 bpatton
2007-05-09 22:06 ` Maciej Katafiasz
0 siblings, 1 reply; 2+ messages in thread
From: bpatton @ 2007-05-09 16:44 UTC (permalink / raw)
To: help-gnu-emacs
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: opening makefile with error message.
2007-05-09 16:44 opening makefile with error message bpatton
@ 2007-05-09 22:06 ` Maciej Katafiasz
0 siblings, 0 replies; 2+ messages in thread
From: Maciej Katafiasz @ 2007-05-09 22:06 UTC (permalink / raw)
To: help-gnu-emacs
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-05-09 22:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-09 16:44 opening makefile with error message bpatton
2007-05-09 22:06 ` Maciej Katafiasz
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.