From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Ernesto Alfonso Newsgroups: gmane.emacs.bugs Subject: bug#32676: Feature request Date: Sat, 15 Sep 2018 17:37:12 -0700 Message-ID: References: <20180910050802.25922-1-erjoalgo@gmail.com> <83a7ollcq2.fsf@gnu.org> <874let1o3k.fsf@gmail.com> <831s9xl54b.fsf@gnu.org> <874leq1hw4.fsf@mail.linkov.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000a0b64f0575f242ed" X-Trace: blaine.gmane.org 1537058169 29896 195.159.176.226 (16 Sep 2018 00:36:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 16 Sep 2018 00:36:09 +0000 (UTC) Cc: Robert Pluim , 32676@debbugs.gnu.org To: juri@linkov.net Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Sep 16 02:36:04 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g1L2f-0007a7-0X for geb-bug-gnu-emacs@m.gmane.org; Sun, 16 Sep 2018 02:36:01 +0200 Original-Received: from localhost ([::1]:57249 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g1L4l-0005qx-GG for geb-bug-gnu-emacs@m.gmane.org; Sat, 15 Sep 2018 20:38:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46520) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g1L4f-0005qr-Ci for bug-gnu-emacs@gnu.org; Sat, 15 Sep 2018 20:38:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g1L4c-0004B3-56 for bug-gnu-emacs@gnu.org; Sat, 15 Sep 2018 20:38:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:37575) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g1L4c-0004Az-01 for bug-gnu-emacs@gnu.org; Sat, 15 Sep 2018 20:38:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g1L4b-0004Oj-QZ for bug-gnu-emacs@gnu.org; Sat, 15 Sep 2018 20:38:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Ernesto Alfonso Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 16 Sep 2018 00:38:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32676 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 32676-submit@debbugs.gnu.org id=B32676.153705825116862 (code B ref 32676); Sun, 16 Sep 2018 00:38:01 +0000 Original-Received: (at 32676) by debbugs.gnu.org; 16 Sep 2018 00:37:31 +0000 Original-Received: from localhost ([127.0.0.1]:41833 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g1L47-0004Nu-A7 for submit@debbugs.gnu.org; Sat, 15 Sep 2018 20:37:31 -0400 Original-Received: from mail-wm1-f47.google.com ([209.85.128.47]:53198) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g1L46-0004Nd-45 for 32676@debbugs.gnu.org; Sat, 15 Sep 2018 20:37:30 -0400 Original-Received: by mail-wm1-f47.google.com with SMTP id y139-v6so5627448wmc.2 for <32676@debbugs.gnu.org>; Sat, 15 Sep 2018 17:37:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0Hr06sTFJ3coLpDDMhDpQqGpsDvuurxmeKodP9fctU4=; b=HVXdKLix1iF4nCkiyKBfNutI+OxVwCh46bi4oq4lV6SeZ8F+1rOKoKGJJa9phUGeVS SRI6kjiDD/XAeOpRa3nJlgIb6Sqt+m/6et+lymi7gXjYiaRflyAuEJ+8XfQ8iws8K9R/ X/KSvEDltthMuWh74jqfssP0tTDL2rd8M73uvm5ZE3w3U4/2L2WIuzibejzrZ6xpwYIh uln1bbIZJmxvbMskPhVOonbQvinTjNr4eBlfRzCNU+K9ZpnDqJFhz+zSmWiUSBr8a7cl B+Pm53PpV2/TtmpltithGSAGVC/2iIs6Fiwmaufd0WfsgrIvFk/9L5Fawxp3xVeUZTSW A/Wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0Hr06sTFJ3coLpDDMhDpQqGpsDvuurxmeKodP9fctU4=; b=kTC7L/Jpcp8LKxud5wXSp1QQIycBQahXA8kArCxPQm4fkI7FykLQ/2S/f0N2JP77RA 2AnyC9mpy5frMR5mRsF/arfMp+bSIprpvyKwkAQPU8Z7ptX3fOlpvtc0tSpdQ/ElFNeS Y3uwip9xOf1gFvmXztbh4jd6SPud4Ah2lV1fw+YeQ8HQdwJZ4TYnaraXWoPaON5QETdY uPWiomv74XvqW+1/qWpzr6pKl4sv4sBwm1U4Jx95vLGiulRpX6smZqHHxu7IYaXZaGJh 7yYqmo2WPkdLldJYdDAJJgGXoci2yDf9bHOQJXga9a4P1IbE7iZkmoUW0PJfgKYUglxV hXyQ== X-Gm-Message-State: APzg51AX7/6vmkpTGaIYOsWxA13j72UH+nYPm2R8mD4jQQIYbk18GIbu 4ozLU5aiBNFytRIUgRoZ3jFrxe/OsKTI/DmW0NA= X-Google-Smtp-Source: ANB0Vda2LmZAMVIGcIkIPRsmLEua1hR3jJkTFWl/oGymMlgjJZYKSvVRtz4hcfxcv0HVLFLs9FaGDyXhiC3W9Lp5IbU= X-Received: by 2002:a1c:4007:: with SMTP id n7-v6mr6932409wma.108.1537058243915; Sat, 15 Sep 2018 17:37:23 -0700 (PDT) In-Reply-To: <874leq1hw4.fsf@mail.linkov.net> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:150345 Archived-At: --000000000000a0b64f0575f242ed Content-Type: text/plain; charset="UTF-8" > > > Do I understand correctly that your proposed feature is like > next-error-highlight, > but instead of highlighting the error locus, it highlights the error > message? Yes, although I don't think it's important to support a timer to turn off highlighting like next-error-highlight does since the error locus highlighting might get in the user's way in source buffers, but not in the next-error buffer. Then I don't understand how it relates to compilation-highlight-regexp and > compilation-highlight-overlay? I don't see a reference to compilation-highlight-regexp or compilation-highlight-overlay in my patch or in this thread. Although I did use compilation-current-error to find the mark at the error message location, which I think is not appropriate since that would be compilation-specific, and I think it should be (point) instead. Is this what you mean? Ernesto On Sat, Sep 15, 2018 at 4:49 PM Juri Linkov wrote: > > Attaching the last gif as an inline/attachment instead of an external > link. > > This was the attempt to use hl-line-range-function. It did not work for > me. > > Do I understand correctly that your proposed feature is like > next-error-highlight, > but instead of highlighting the error locus, it highlights the error > message? > Then I don't understand how it relates to compilation-highlight-regexp and > compilation-highlight-overlay? > --000000000000a0b64f0575f242ed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Do I understand correctly that your proposed feature is like next-error-hi= ghlight,
but instead of highlighting the error locus, it highlights the = error message?
Yes, although I don't think it's im= portant to support a timer to turn off highlighting like next-error-highlig= ht does since the error locus highlighting might get in the user's way = in source buffers, but not in the next-error buffer.

=C2=A0Then I don't unde= rstand how it relates to compilation-highlight-regexp and
compilation-hi= ghlight-overlay?
=C2=A0
I don't see a refere= nce to compilation-highlight-regexp or compilation-highlight-overlay in my = patch or in this thread. Although I did use=C2=A0compilation-current-error = to find the mark at the error message location, which I think is not approp= riate since that would be compilation-specific, and I think it should be (p= oint) instead. Is this what you mean?

Ernesto



On Sat, Sep 15, 2018 at 4:= 49 PM Juri Linkov <juri@linkov.net> wrote:
> Attaching the las= t gif as an inline/attachment instead of an external link.
> This was the attempt to use hl-line-range-function. It did not work fo= r me.

Do I understand correctly that your proposed feature is like next-error-hig= hlight,
but instead of highlighting the error locus, it highlights the error messag= e?
Then I don't understand how it relates to compilation-highlight-regexp = and
compilation-highlight-overlay?
--000000000000a0b64f0575f242ed--