GNU bug report logs - #51444
One issue in NEWS

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 51444 in the body.
You can then email your comments to 51444 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: bug-gnu-emacs <at> gnu.org
Subject: One issue in NEWS
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:

diff --git a/doc/emacs/building.texi b/doc/emacs/building.texi
index 8de93867ba..2c694a5e39 100644
--- a/doc/emacs/building.texi
+++ b/doc/emacs/building.texi
@@ -213,7 +213,6 @@ Compilation Mode
 @kindex M-g n
 @kindex C-x `
 @findex next-error
-@findex next-error-message
 @vindex next-error-message-highlight
 @vindex next-error-highlight
 @vindex next-error-highlight-no-select
@@ -263,7 +262,9 @@ Compilation Mode
 highlights the relevant source line.  The duration of this highlight
 is determined by the variable @code{next-error-highlight} for the locus
 in the selected buffer, and @code{next-error-highlight-no-select} for
-the locus in non-selected buffers.
+the locus in non-selected buffers.  Also you can customize the variable
+@code{next-error-message-highlight} that defines how to highlight the
+current error message in the buffer that contains messages.
 
 @vindex compilation-context-lines
   If the @file{*compilation*} buffer is shown in a window with a left
-- 

Message #8 received at 51444 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juri Linkov <juri <at> linkov.net>
Cc: 51444 <at> debbugs.gnu.org
Subject: Re: bug#51444: One issue in NEWS
Date: Wed, 27 Oct 2021 21:30:10 +0300

> From: Juri Linkov <juri <at> 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.

Message #11 received at 51444 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 51444 <at> debbugs.gnu.org
Subject: Re: bug#51444: One issue in NEWS
Date: Wed, 27 Oct 2021 21:39:38 +0300

>>   ** 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.

It's on a par with next-error-highlight and next-error-highlight-no-select:

- next-error-highlight and next-error-highlight-no-select are applied
  to the buffer visited by next-error;

- next-error-message-highlight highlighting is applied to the buffer
  with error messages and matches.

Message #14 received at 51444 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juri Linkov <juri <at> linkov.net>
Cc: 51444 <at> debbugs.gnu.org
Subject: Re: bug#51444: One issue in NEWS
Date: Wed, 27 Oct 2021 21:46:58 +0300

> From: Juri Linkov <juri <at> linkov.net>
> Cc: 51444 <at> debbugs.gnu.org
> Date: Wed, 27 Oct 2021 21:39:38 +0300
> 
> >>   @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.
> 
> It's on a par with next-error-highlight and next-error-highlight-no-select:
> 
> - next-error-highlight and next-error-highlight-no-select are applied
>   to the buffer visited by next-error;
> 
> - next-error-message-highlight highlighting is applied to the buffer
>   with error messages and matches.

So maybe none of them needs to be in the manual.

Message #17 received at 51444 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 51444 <at> debbugs.gnu.org
Subject: Re: bug#51444: One issue in NEWS
Date: Wed, 27 Oct 2021 21:58:55 +0300

>> > Does that option need to be documented in the manual?  It sounds quite
>> > obscure to me.
>>
>> It's on a par with next-error-highlight and next-error-highlight-no-select:
>>
>> - next-error-highlight and next-error-highlight-no-select are applied
>>   to the buffer visited by next-error;
>>
>> - next-error-message-highlight highlighting is applied to the buffer
>>   with error messages and matches.
>
> So maybe none of them needs to be in the manual.

I don't know 🤷

Message #22 received at 51444 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 51444 <at> debbugs.gnu.org
Subject: Re: bug#51444: One issue in NEWS
Date: Wed, 03 Nov 2021 20:34:30 +0200

close 51444 28.0.60
quit

>>> > Does that option need to be documented in the manual?  It sounds quite
>>> > obscure to me.
>>>
>>> It's on a par with next-error-highlight and next-error-highlight-no-select:
>>>
>>> - next-error-highlight and next-error-highlight-no-select are applied
>>>   to the buffer visited by next-error;
>>>
>>> - next-error-message-highlight highlighting is applied to the buffer
>>>   with error messages and matches.
>>
>> So maybe none of them needs to be in the manual.
>
> I don't know 🤷

I have no opinion whether they need to be in the manual,
so just fixed the problem of missing text for the existing vindex.

Message #27 received at 51444 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 51444 <at> debbugs.gnu.org
Subject: Re: bug#51444: One issue in NEWS
Date: Thu, 04 Nov 2021 19:36:29 +0200

>>> So maybe none of them needs to be in the manual.
>>
>> I don't know 🤷
>
> I have no opinion whether they need to be in the manual,
> so just fixed the problem of missing text for the existing vindex.

I noticed this entry has neither +++ nor --- indication in NEWS.28:

  *** The tab bar now supports more mouse commands.
  Clicking 'mouse-2' closes the tab, 'mouse-3' displays the context menu
  with items that operate on the clicked tab.  Dragging the tab with
  'mouse-1' moves it to another position on the tab bar.  Mouse wheel
  scrolling switches to the previous/next tab, and holding the Shift key
  during scrolling moves the tab to the left/right.

Should it be documented in the manual?

Message #30 received at 51444 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Juri Linkov <juri <at> linkov.net>
Cc: 51444 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#51444: One issue in NEWS
Date: Thu, 04 Nov 2021 18:54:10 +0100

Juri Linkov <juri <at> linkov.net> writes:

> I noticed this entry has neither +++ nor --- indication in NEWS.28:
>
>   *** The tab bar now supports more mouse commands.
>   Clicking 'mouse-2' closes the tab, 'mouse-3' displays the context menu
>   with items that operate on the clicked tab.  Dragging the tab with
>   'mouse-1' moves it to another position on the tab bar.  Mouse wheel
>   scrolling switches to the previous/next tab, and holding the Shift key
>   during scrolling moves the tab to the left/right.
>
> Should it be documented in the manual?

The first few issues seem so self-evident that they don't need to be in
the manual.  But the mouse wheel and shift key thing perhaps should be?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #33 received at 51444 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juri Linkov <juri <at> linkov.net>
Cc: 51444 <at> debbugs.gnu.org
Subject: Re: bug#51444: One issue in NEWS
Date: Thu, 04 Nov 2021 20:47:51 +0200

> From: Juri Linkov <juri <at> linkov.net>
> Cc: 51444 <at> debbugs.gnu.org
> Date: Thu, 04 Nov 2021 19:36:29 +0200
> 
> I noticed this entry has neither +++ nor --- indication in NEWS.28:
> 
>   *** The tab bar now supports more mouse commands.
>   Clicking 'mouse-2' closes the tab, 'mouse-3' displays the context menu
>   with items that operate on the clicked tab.  Dragging the tab with
>   'mouse-1' moves it to another position on the tab bar.  Mouse wheel
>   scrolling switches to the previous/next tab, and holding the Shift key
>   during scrolling moves the tab to the left/right.
> 
> Should it be documented in the manual?

Yes, probably.

Thanks.

Message #36 received at 51444 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 51444 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#51444: One issue in NEWS
Date: Sun, 07 Nov 2021 20:01:10 +0200

>> I noticed this entry has neither +++ nor --- indication in NEWS.28:
>>
>>   *** The tab bar now supports more mouse commands.
>>   Clicking 'mouse-2' closes the tab, 'mouse-3' displays the context menu
>>   with items that operate on the clicked tab.  Dragging the tab with
>>   'mouse-1' moves it to another position on the tab bar.  Mouse wheel
>>   scrolling switches to the previous/next tab, and holding the Shift key
>>   during scrolling moves the tab to the left/right.
>>
>> Should it be documented in the manual?
>
> The first few issues seem so self-evident that they don't need to be in
> the manual.  But the mouse wheel and shift key thing perhaps should be?

I added the description as short as possible, without tables and indexes,
so maybe this is ok.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.