unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Allow compilation-next-error-function to leave code line highlighted until next command is typed
Date: Wed, 23 Jun 2004 02:19:16 +0300	[thread overview]
Message-ID: <873c4nyydn.fsf@mail.jurta.org> (raw)
In-Reply-To: <ud63ruzdd.fsf@world.std.com> (Francis Litterio's message of "Tue, 22 Jun 2004 15:26:28 -0400")

Francis Litterio <franl@world.std.com> writes:
> This patch to lisp/progmodes/compile.el in the CVS Emacs sources allows
> compilation-next-error-function to either highlight the displayed line
> of code for a configurable amount of time (it used to be hard-coded at
> 0.5 seconds) or to leave it highlighted until the next command is
> entered.
>
> I hope this change is of value.

A similar change was discussed recently but was stuck with naming
of this option: it should be used by packages other than compile
(grep, diff, occur, ...), but neither `compilation-highlight' nor
`next-error-highlight' seems right when applied to non-compilation
buffers.  Perhaps `locus-highlight' or `match-highlight' are better
names.

-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2004-06-22 23:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 19:26 [PATCH] Allow compilation-next-error-function to leave code line highlighted until next command is typed Francis Litterio
2004-06-22 23:19 ` Juri Linkov [this message]
2004-06-23  4:50 ` Eli Zaretskii
2004-06-28 14:58 ` Richard Stallman
2004-06-29  1:32   ` Juri Linkov
2004-06-30  3:02     ` Richard Stallman
2004-07-01  5:46       ` Juri Linkov
2004-07-02 10:12         ` Richard Stallman
2004-07-10 22:41         ` Richard Stallman
2004-07-12 16:13           ` Ted Zlatanov
2004-07-14  0:16             ` Richard Stallman
2004-09-13 17:58               ` Ted Zlatanov
2004-09-17  9:36                 ` Richard Stallman

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=873c4nyydn.fsf@mail.jurta.org \
    --to=juri@jurta.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).