From: Juri Linkov <juri@jurta.org>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Overlay arrow in *compilation* and *grep* buffers
Date: Mon, 09 May 2005 23:55:34 +0300 [thread overview]
Message-ID: <87oebkw22l.fsf@jurta.org> (raw)
In-Reply-To: <17009.62951.957607.360268@farnswood.snap.net.nz> (Nick Roberts's message of "Fri, 29 Apr 2005 20:52:55 +1200")
> Currently simple.el has:
>
> (put 'next-error-overlay-arrow-position 'overlay-arrow-string "=>")
>
> but this could be removed as it is the default now anyway (I think Juri
> disappeared again before 2005-04-08).
Sorry. I traveled to my friend. She lives 1000km from me.
> I suggest this latter change until Juri (or maybe Stefan) comes up with a
> better solution that will work with "=>".
I suggest adding a new option defining how to highlight lines
in compilation/grep buffers, similar to `next-error-highlight'
which defines highlighting in source buffers. It will replace
`compilation-context-lines':
(defcustom compilation-message-highlight 0
"*Highlighting of locations in the compilation buffer.
If number, display this many lines of leading context before message.
If t, use persistent overlays fontified in next-error face.
If nil, don't highlight the locus in the compilation buffer.
If `fringe-arrow', indicate the locus by the fringe arrow."
:type '(choice (number :tag "Context lines")
(const :tag "Persistent overlay" t)
(const :tag "No highlighting" nil)
(const :tag "Fringe arrow" 'fringe-arrow))
:group 'compilation
:version "22.1")
Since the number of context lines and fringe arrow are mutually exclusive
values, there will be no problem with an arrow overlapping a file name
in the compilation buffer, because by default there will be no arrow at all.
Users wishing to use arrows can set `compilation-message-highlight' to
`fringe-arrow' in .emacs conditionally depending on the presence of fringes.
BTW, I don't understand the reason of adding `(defvar next-error-highlight-timer)'
to compile.el on 2005-04-23. There is already the same defvar in simple.el.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-05-09 20:55 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 10:45 Overlay arrow in *compilation* and *grep* buffers Eli Zaretskii
2005-04-24 18:42 ` Kim F. Storm
2005-04-24 20:04 ` Eli Zaretskii
2005-04-27 13:10 ` Kim F. Storm
2005-04-27 14:39 ` Eli Zaretskii
2005-04-28 11:01 ` Richard Stallman
2005-04-28 19:51 ` Eli Zaretskii
2005-04-28 20:54 ` Nick Roberts
2005-04-29 7:08 ` Eli Zaretskii
2005-04-29 8:52 ` Nick Roberts
2005-05-09 20:55 ` Juri Linkov [this message]
2005-05-10 6:40 ` David Kastrup
2005-05-12 11:38 ` Nick Roberts
2005-05-13 1:34 ` Richard Stallman
2005-05-13 5:03 ` Juri Linkov
2005-05-13 6:08 ` Eli Zaretskii
2005-05-13 7:18 ` Nick Roberts
2005-05-13 13:28 ` Eli Zaretskii
2005-05-14 0:26 ` Richard Stallman
2005-05-14 7:17 ` Eli Zaretskii
2005-05-14 22:20 ` Kim F. Storm
2005-05-15 15:58 ` Richard Stallman
2005-05-13 13:02 ` Nick Roberts
2005-05-14 0:25 ` Richard Stallman
2005-05-15 2:44 ` Nick Roberts
2005-05-15 4:12 ` Eli Zaretskii
2005-05-15 4:21 ` Eli Zaretskii
2005-05-15 22:39 ` Richard Stallman
2005-05-16 1:20 ` Nick Roberts
2005-05-16 19:28 ` Richard Stallman
2005-05-16 19:28 ` Richard Stallman
2005-05-16 22:16 ` Nick Roberts
2005-05-17 13:23 ` Richard Stallman
2005-04-29 10:49 ` Nick Roberts
2005-05-07 16:20 ` Eli Zaretskii
2005-05-07 21:10 ` Kim F. Storm
2005-05-08 0:41 ` Nick Roberts
2005-05-08 4:21 ` Eli Zaretskii
2005-05-08 5:49 ` Nick Roberts
2005-05-08 16:12 ` Richard Stallman
2005-05-08 19:37 ` Eli Zaretskii
2005-04-25 16:05 ` Richard Stallman
2005-04-25 16:46 ` Eli Zaretskii
2005-04-26 14:33 ` Richard Stallman
2005-04-28 11:34 ` Nick Roberts
2005-04-28 19:50 ` Eli Zaretskii
2005-04-28 21:16 ` Nick Roberts
2005-04-29 10:15 ` Richard Stallman
2005-04-29 12:19 ` Nick Roberts
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=87oebkw22l.fsf@jurta.org \
--to=juri@jurta.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).