GNU bug report logs - #43715
28.0.50; Duplicate results in project-find-regexp

Previous Next

Full log

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: Pankaj Jangid <pankaj <at> codeisgreat.org>, 43715 <at> debbugs.gnu.org
Subject: Re: bug#43715: 28.0.50; Duplicate results in project-find-regexp
Date: Thu, 01 Oct 2020 23:38:50 +0200

Dmitry Gutov <dgutov <at> yandex.ru> writes:

> On 01.10.2020 23:39, Lars Ingebrigtsen wrote:
>>>> Right.  I know next to nothing about xref internals...  but...
>>>> couldn't
>>>> this function just squash the multiple-matches-on-a-single-line into one
>>>> line?  Preserving the text props from the multiple lines and whatnot?
>>>> So a post-processing step?
>>> Which function?
>> `project-find-regexp'
>
> Then I'm not sure which eventual behavior you envision. Among other
> things, it doesn't answer the question I asked in the second paragraph
> of my previous email.

This one?

> Going back to xref buffers, if two matches are rendered on one line,
> that leads to a question of how 'n' and 'p' should behave (whether
> they would also jump between the matches on the same line).

I have no idea; I've never used those commands.

I'd just expect project-find-regexp to work as M-x grep, and have
`next-error' work (which works based on lines).

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

Previous Next

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