From: Juri Linkov <juri@jurta.org>
Cc: tzz@lifelogs.com, emacs-devel@gnu.org
Subject: Re: [PATCH] Allow compilation-next-error-function to leave code line highlighted until next command is typed
Date: Thu, 01 Jul 2004 08:46:42 +0300 [thread overview]
Message-ID: <87pt7gl1od.fsf@mail.jurta.org> (raw)
In-Reply-To: <E1BfVN0-0003Xw-Aw@fencepost.gnu.org> (Richard Stallman's message of "Tue, 29 Jun 2004 23:02:46 -0400")
Richard Stallman <rms@gnu.org> writes:
> As long as the command name on C-x ` is next-error, we may as well
> call the option next-error-highlight. If we change that binding
> before the release, we can rename the option at the same time.
>
> So please install this, as soon as you've written the changes for
> etc/NEWS and the Emacs Manual.
Mentioning the changes in etc/NEWS is ok, but I can't find a place in
the Emacs Manual where new options `next-error-highlight' and
`next-error-highlight-no-select' should be documented.
I recall that documentation rules disapprove adding every option
to the manual to not make it too big. And it seems these options are
not too significant for using `next-error' to justify their additions
to the manual.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-07-01 5:46 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
2004-06-29 1:32 ` Juri Linkov
2004-06-30 3:02 ` Richard Stallman
2004-07-01 5:46 ` Juri Linkov [this message]
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=87pt7gl1od.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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.
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).