emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#36967: closed (27.0.50; Duplicate lines in xref output)


From: GNU bug Tracking System
Subject: bug#36967: closed (27.0.50; Duplicate lines in xref output)
Date: Mon, 21 Dec 2020 01:43:01 +0000

Your message dated Mon, 21 Dec 2020 03:42:41 +0200
with message-id <53aad279-912c-9b47-e5c3-d4373b1556a2@yandex.ru>
and subject line Re: bug#36967: 27.0.50; Duplicate lines in xref output
has caused the debbugs.gnu.org bug report #36967,
regarding 27.0.50; Duplicate lines in xref output
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
36967: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36967
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 27.0.50; Duplicate lines in xref output Date: Thu, 08 Aug 2019 00:52:13 +0300 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu)
I tried to use project-find-regexp more often than rgrep,
but unfortunately xref still has a fundamental flaw:

0. emacs -Q
1. M-x project-find-regexp RET regexp RET
2. The output buffer *xref* contains duplicate lines
   when regexp is found on the same line several times,
   each duplicate output line has separate highlighting
   for every regexp occurrence.



--- End Message ---
--- Begin Message --- Subject: Re: bug#36967: 27.0.50; Duplicate lines in xref output Date: Mon, 21 Dec 2020 03:42:41 +0200 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
Version: 28.1

On 09.12.2020 15:57, Dmitry Gutov wrote:
On 09.12.2020 05:53, Dmitry Gutov wrote:
Using xref-file-location-column there kind of breaks the abstraction. I was thinking more along the lines of text-prop search for the column inside the summary string:

Although we'll probably make it an optional method, just like xref-location-line is already.

And now done.

I've pushed the slightly tweaked Juri's patch and the change described above.

With that, the bug should be fixed now. Please let me know if something is still amiss.

Thanks all!


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]