From: Richard Stallman <rms@gnu.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: Mon, 28 Jun 2004 10:58:13 -0400 [thread overview]
Message-ID: <E1BexaH-0002bc-Mf@fencepost.gnu.org> (raw)
In-Reply-To: <ud63ruzdd.fsf@world.std.com> (message from Francis Litterio on Tue, 22 Jun 2004 15:26:28 -0400)
Juri Linkov responded:
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.
As long as the command is called `next-error', it is ok to call some
related thing `next-error-highlight'. Even the name
`compilation-highlight-duration' can't be objected to, given that the
function that would use it is called `compilation-goto-locus'.
We might consider a change in all these names, but that is a separate
issue. There is no need to hold up this little feature for that.
ISTR that we already discussed some other feature for highlighting
the source code line. What is actually installed now?
next prev parent reply other threads:[~2004-06-28 14:58 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
2004-06-23 4:50 ` Eli Zaretskii
2004-06-28 14:58 ` Richard Stallman [this message]
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=E1BexaH-0002bc-Mf@fencepost.gnu.org \
--to=rms@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).