On Mon, Aug 1, 2016 at 2:35 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Michael Giuffrida <michaelpg@xxxxxxxxxxxx> 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? 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html