From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 51444@debbugs.gnu.org
Subject: bug#51444: One issue in NEWS
Date: Wed, 27 Oct 2021 21:30:10 +0300 [thread overview]
Message-ID: <83ee86uxql.fsf@gnu.org> (raw)
In-Reply-To: <87sfwm5qil.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 27 Oct 2021 20:27:22 +0300)
> From: Juri Linkov <juri@linkov.net>
> Date: Wed, 27 Oct 2021 20:27:22 +0300
>
> Currently I'm reading NEWS.28 and noticed this section marked by
> +++ as documented in the manual:
>
> +++
> ** New user option 'next-error-message-highlight'.
> In addition to a fringe arrow, 'next-error' error may now optionally
> highlight the current error message in the 'next-error' buffer.
> This user option can be also customized to keep highlighting on all
> visited errors, so you can have an overview what errors were already visited.
>
> But the source of the manual has only these two lines:
>
> @findex next-error-message
> @vindex next-error-message-highlight
>
> 'next-error-message' is a face and can be removed from the index.
> But 'next-error-message-highlight' is a user option, and when
> the reader selects it from the Info index, its page says nothing
> about this option. This patch fills the gap:
Does that option need to be documented in the manual? It sounds quite
obscure to me.
next prev parent reply other threads:[~2021-10-27 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 17:27 bug#51444: One issue in NEWS Juri Linkov
2021-10-27 18:30 ` Eli Zaretskii [this message]
2021-10-27 18:39 ` Juri Linkov
2021-10-27 18:46 ` Eli Zaretskii
2021-10-27 18:58 ` Juri Linkov
2021-11-03 18:34 ` Juri Linkov
2021-11-04 17:36 ` Juri Linkov
2021-11-04 17:54 ` Lars Ingebrigtsen
2021-11-07 18:01 ` Juri Linkov
2021-11-04 18:47 ` Eli Zaretskii
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=83ee86uxql.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51444@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).