[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
compilation error patterns, how to add new ones
From: |
Ian Zimmerman |
Subject: |
compilation error patterns, how to add new ones |
Date: |
Sun, 26 Jul 2015 16:51:49 -0700 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
What is the proper way for an external package (that is, one not
shipping with emacs) to add new error patterns? Adding patterns
directly to compilation-error-regexp-alist seems a no-no, not only
because it messes up the value to make it unreadable but also because
that variable is a customization item. So I tried to just add my
pattern to compilation-error-regexp-alist-alist unconditionally and
leave it to the user if she adds the symbol to the customizable list.
But now there is a new problem: if the symbol is in fact added and a
compilation runs before my package is loaded (compiling files in a
different language, for example), emacs throws up because it tries to
use the result of looking up the pattern in
compilation-error-regexp-alist-alist, and that is nil.
It seems like the only way is to give users a snippet of code to run at
init time, beyond just autoloading, and I was trying to avoid that.
--
Please *no* private copies of mailing list or newsgroup messages.
Rule 420: All persons more than eight miles high to leave the court.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- compilation error patterns, how to add new ones,
Ian Zimmerman <=