Adjacent replaced multiline matches result in wrong line numbers about ripgrep HOT 4 OPEN

Using a multiline regexp, when the regexp matches strings that come immediately one after another, it bungles the line numbers of all of them.

This is an incomplete description of the problem you're reporting. It isn't just when a regex matches strings that are adjacent, it's also required that you use the -r/--replace flag to replace matches with something else. This can be easily demonstrated by omitting the -r/--replace flag and observing that the line numbers are correct:

$ rg -nU '^:properties:\n:id: (.*)\n:end:' test.txt
1::properties:
2::id: fnord
3::end:
4::properties:
5::id: boccob
6::end:
7::properties:
8::id: d321fdddffff
9::end:
10::properties:
11::id: clowns
12::end:

Indeed though, the adjacency part of this seems important. If instead I use the following haystack as test2.txt:

:properties:
:id: fnord
:end:
ZZZ
:properties:
:id: boccob
:end:
ZZZ
:properties:
:id: d321fdddffff
:end:
ZZZ
:properties:
:id: clowns
:end:

Then the line numbers change:

$ rg -nU '^:properties:\n:id: (.*)\n:end:' -r '$1' test2.txt
1:fnord
5:boccob
9:d321fdddffff
13:clowns

from ripgrep.

As you say, I forgot to mertion the --replace. Changed the title.

from ripgrep.

I'm not proficient with Rust, but I could try to look for the problem. Any pointers on where to look?

from ripgrep.

Likely in grep-printer. Look at the "standard" printer.

That's where I would start anyway.

from ripgrep.