unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ernesto Alfonso <erjoalgo@gmail.com>
To: 32676@debbugs.gnu.org
Subject: bug#32676: Feature request
Date: Thu, 13 Sep 2018 09:14:41 -0700	[thread overview]
Message-ID: <CAOckuXCJ1pfsDe-i9Ro8TkBAvGiQQuVowFnT-FgQCqq8ysESNw@mail.gmail.com> (raw)
In-Reply-To: <CAOckuXD4--GF0E=eMWf-T74rEjrjt4CWfx97OWWszRay3P-ujQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2455 bytes --]

Replied all to the wrong thread -- removing emacs-devel

On Thu, Sep 13, 2018 at 9:10 AM Ernesto Alfonso <erjoalgo@gmail.com> wrote:

> Another problem with hl-line is what the original poster pointed out in
> the screenshot below: hl-line only highlights on the current buffer's
> window, so if the user were to switch to the source code buffer (or if he
> wasn't there in the first place, e.g. by having invokied next-error form
> the source code buffer via a key binding) then highlighting of error
> messages is either lost or never happens.
>
>
> [image: 13-Sep-2018-08:41:46.png]
>
>
> global hl line: no highlighting on next-error buffer if it is not current:
>
> [image: global-hl-line.gif]
>
> hl-line with next-buffer as current: highlighting not preserved after
> movement commands
> [image: hl-line-scrolling-on-next-buffer.gif]
>
> Thanks,
>
> Ernesto
>
> On Thu, Sep 13, 2018 at 12:10 AM Ernesto Alfonso <erjoalgo@gmail.com>
> wrote:
>
>> Dear maintainers,
>>
>> I recently made feature request along with a patch and sent it to
>> gnu-emacs@gnu.org based on the contributor guidelends.
>>
>> I wanted to provide a bit more context on the motivation behind this
>> patch.
>>
>> When scrolling through compilation errors, for some users the small
>> fringe arrow indicator that appears next to the current error in the
>> next-error buffer next to the error message can be hard to find quickly
>> without without strain. I personally often find myself reading the wrong
>> error message when fixing compilation errors.
>>
>> This enhancement adds a customizable option to highlight the current
>> error message in the next-error buffer in addition to the fringe arrow
>> indicator. This makes for a visually more pleasing experience when locating
>> the next-error current error message.
>>
>> I include a demo below where I'm scrolling through several errors in a
>> small c++ program.
>>
>> For the implementation, I used the suggestion in Drew's answer
>> <https://emacs.stackexchange.com/a/13137/2846> on emacs stackexchange
>> where another user raised the same concern about 2 years ago.
>>
>> The new behavior is off by default, and the font used to highlight the
>> errors may also be customized.
>>
>> Please let me know if the patch can be improved or what are the next
>> steps in this review, and I look forward to this enhancement being part of
>> the next emacs release.
>>
>> [image: demo.gif]
>>
>> Thanks,
>>
>> Ernesto
>>
>

[-- Attachment #1.2: Type: text/html, Size: 3739 bytes --]

[-- Attachment #2: global-hl-line.gif --]
[-- Type: image/gif, Size: 488685 bytes --]

[-- Attachment #3: hl-line-scrolling-on-next-buffer.gif --]
[-- Type: image/gif, Size: 449293 bytes --]

[-- Attachment #4: 13-Sep-2018-08:41:46.png --]
[-- Type: image/png, Size: 30270 bytes --]

      parent reply	other threads:[~2018-09-13 16:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10  5:08 bug#32676: [PATCH] Add option to highlight the 'next-error' error message Ernesto Alfonso
2018-09-13  7:10 ` bug#32676: Feature request Ernesto Alfonso
2018-09-13 13:59   ` Eli Zaretskii
2018-09-13 14:14     ` Robert Pluim
2018-09-13 15:02       ` Ernesto Alfonso
2018-09-13 16:44         ` Eli Zaretskii
2018-09-13 18:18           ` Ernesto Alfonso
2018-09-14 16:40             ` Ernesto Alfonso
2018-09-15 23:05               ` Juri Linkov
2018-09-16  0:37                 ` Ernesto Alfonso
2018-09-16 23:27                   ` Juri Linkov
2018-09-18  8:51                     ` Ernesto Alfonso
2019-04-07 21:56                       ` Ernesto Alfonso
2019-04-08 19:36                         ` bug#32676: [PATCH] Add option to highlight the 'next-error' error message Juri Linkov
2019-04-09  5:48                           ` Eli Zaretskii
2020-02-29 15:40                             ` Stefan Kangas
2020-08-10 12:38                               ` Lars Ingebrigtsen
2020-08-10 14:00                                 ` Ernesto Alfonso
2020-09-03  5:00                                   ` Ernesto Alfonso
2020-09-03 10:40                                     ` Stefan Kangas
2020-10-14  5:47                           ` Lars Ingebrigtsen
2020-10-14 19:30                             ` Juri Linkov
2020-10-15  7:19                               ` Lars Ingebrigtsen
2020-10-16  8:13                                 ` Juri Linkov
2020-10-16 14:48                                   ` Lars Ingebrigtsen
2020-10-17 20:24                                     ` Juri Linkov
2020-10-18  8:34                                       ` Lars Ingebrigtsen
2020-11-05 20:20                                   ` Juri Linkov
2020-11-05 22:05                                     ` Kévin Le Gouguec
2020-11-06  8:43                                       ` Juri Linkov
2020-11-06 22:06                                         ` bug#32676: Updating Org for 27.2 (was: bug#32676: [PATCH] Add option to highlight the 'next-error' error message) Kévin Le Gouguec
2020-11-09  9:03                                           ` bug#32676: Updating Org for 27.2 Juri Linkov
2020-11-09 12:17                                             ` Kévin Le Gouguec
2020-11-10  4:10                                               ` Kyle Meyer
2020-11-10 19:30                                               ` Juri Linkov
2020-11-10 20:02                                                 ` Glenn Morris
     [not found]   ` <CAOckuXD4--GF0E=eMWf-T74rEjrjt4CWfx97OWWszRay3P-ujQ@mail.gmail.com>
2018-09-13 16:14     ` Ernesto Alfonso [this message]

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=CAOckuXCJ1pfsDe-i9Ro8TkBAvGiQQuVowFnT-FgQCqq8ysESNw@mail.gmail.com \
    --to=erjoalgo@gmail.com \
    --cc=32676@debbugs.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).