Re: git grep -P is multiline for negative lookahead/behind

Michael Giuffrida [off-list ref] writes:

Is this expected behavior, and if so, why/where is this documented?

I do not think "git grep" was designed to do multi-line anything,
with or without lookahead.  If you imagine that the implementation
attempts its matches line-by-line, does that explain the observed
symptom?

On Mon, Aug 1, 2016 at 2:35 PM, Junio C Hamano [off-list ref] wrote:

Michael Giuffrida [off-list ref] writes:

quoted

Is this expected behavior, and if so, why/where is this documented?

I do not think "git grep" was designed to do multi-line anything,
with or without lookahead.  If you imagine that the implementation
attempts its matches line-by-line, does that explain the observed
symptom?

No. If it worked line-by-line, it would produce more results. It is
not producing the expected matches because it *is* considering the
previous line in negative lookbehind, when I don't want or expect it
to. Thus it throws out results that should match.

On Thu, Aug 4, 2016 at 11:54 AM, Michael Giuffrida
[off-list ref] wrote:

On Mon, Aug 1, 2016 at 2:35 PM, Junio C Hamano [off-list ref] wrote:

quoted

I do not think "git grep" was designed to do multi-line anything,
with or without lookahead.  If you imagine that the implementation
attempts its matches line-by-line, does that explain the observed
symptom?

No. If it worked line-by-line, it would produce more results. It is
not producing the expected matches because it *is* considering the
previous line in negative lookbehind, when I don't want or expect it
to. Thus it throws out results that should match.

If that is the case I do not know what is going on; perhaps
somebody more familiar with the pcre codepath can help.

Sorry.