From: "Drew Adams" <drew.adams@oracle.com>
To: 'Nordlöw' <per.nordlow@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: Compilation Message Presentation
Date: Wed, 2 Dec 2009 16:14:31 -0800 [thread overview]
Message-ID: <4211C26BC6AD434898D8B62B652DA01E@us.oracle.com> (raw)
In-Reply-To: <6d649a69-9a67-40d6-a6ff-c30f7cc66b5e@r5g2000yqb.googlegroups.com>
> Does anybody know of an extensions to grep()/complie() in compile.el
> that highlights messages/warning/errors/notes in the *source-buffer*
> using either *overlays* or *fringes*?
Isn't that what it does already (overlay, not fringe)?
It does for me, at least.
I use compile+.el and grep+.el, but I don't think that makes much difference
here.
Here is the code in `compilation-goto-locus':
(overlay-put compilation-highlight-overlay 'face 'next-error)
See also variable `compilation-highlight-regexp'.
Oh, I also use simple+.el - maybe that has something to do with it. I added
`until-move' as a possible value for option `next-error-highlight'. Otherwise,
the highlighting goes away too quickly for my taste.
(Since I use separate frames, if the value is `t' it goes away even when I just
switch to the source-buffer frame, because a frame switch is considered the next
command.)
next prev parent reply other threads:[~2009-12-03 0:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 22:36 Compilation Message Presentation Nordlöw
2009-12-03 0:14 ` Drew Adams [this message]
[not found] ` <mailman.12063.1259799543.2239.help-gnu-emacs@gnu.org>
2009-12-03 16:25 ` Nordlöw
2009-12-03 17:49 ` Pascal J. Bourguignon
2009-12-04 3:16 ` Stefan Monnier
2009-12-04 3:42 ` Lennart Borgman
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=4211C26BC6AD434898D8B62B652DA01E@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=per.nordlow@gmail.com \
/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).