From: Oleksandr Gavenko <gavenko@bifit.com.ua>
To: help-gnu-emacs@gnu.org
Subject: Re: reading compile.el, modifying settings
Date: Thu, 12 May 2011 15:49:10 +0300 [thread overview]
Message-ID: <iqgkvl$e4o$1@dough.gmane.org> (raw)
In-Reply-To: <87wri5jukr.fsf@member.fsf.org>
On 05.05.2011 13:44, Tassilo Horn wrote:
> Paul Graham<pgraham@oasys-ds.com> writes:
>
> Hi Paul,
>
>> I use compile mode, but I have my own set of compiler
>> message regexps. I try to set them up as follows:
>>
>> .emacs:
>>
>> (load "compile")
>> (load-file "~/emacs/compile-settings.el")
>>
>> compile-settings.el:
>>
>> (setq compilation-error-regexp-alist ... )
>
> That looks good, except one would normally do (require 'compile), but
> that shouldn't be any different here.
>
I use such code (as example):
(eval-after-load 'compile
'(progn
;; My funny error messages.
(add-to-list 'compilation-error-regexp-alist '("^\\( +\\[csc\\]
\\|\\)\\(.*\\)(\\([0-9]*\\),\\([0-9]*\\)):" 2 3 4))
(add-to-list 'compilation-error-regexp-alist '("^
*\\(.*\\)(\\([0-9]*\\)) +:" 1 2))
(add-to-list 'compilation-error-regexp-alist
'("^\"?\\([^\"]*\\)\"?,\\([0-9]*\\) .*\\[.*\\]: " 1 2)) ; KEIL compiler
(when (boundp 'compilation-mode-font-lock-keywords)
(add-to-list 'compilation-mode-font-lock-keywords
'("\\(/[Oo][Uu][Tt]:[^[:blank:]]+\\)" . 1))
(add-to-list 'compilation-mode-font-lock-keywords
'("[[:blank:]]\\(/F[oe][^[:blank:]]+\\)" . 1))
)
))
next prev parent reply other threads:[~2011-05-12 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 14:03 reading compile.el, modifying settings Paul Graham
2011-05-05 10:44 ` Tassilo Horn
2011-05-12 12:49 ` Oleksandr Gavenko [this message]
2011-05-05 16:31 ` Sam Steingold
2011-05-05 18:15 ` Tassilo Horn
2011-05-05 18:34 ` Sam Steingold
2011-05-05 19:09 ` Tassilo Horn
2011-05-05 21:08 ` Sam Steingold
2011-05-06 7:13 ` Tassilo Horn
2011-05-05 19:48 ` Tassilo Horn
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='iqgkvl$e4o$1@dough.gmane.org' \
--to=gavenko@bifit.com.ua \
--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.
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).