git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 1, 2016, 21:35 UTC
Message-ID
<xmqqr3a8goka.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CACi5S_0QGEgnijGyaBeZxOSobdwfA+d-wa-jrHs64Va097mnRQ@mail.gmail.com>
Michael Giuffrida <michaelpg@chromium.org> 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?

Previous: Michael GiuffridaNext: Michael Giuffrida
Message 2 of 4 in “git grep -P is multiline for negative lookahead/behind”
  1. Michael GiuffridaAug 1, 2016
  2. Junio C HamanoAug 1, 2016
  3. Michael GiuffridaAug 4, 2016
  4. Junio C HamanoAug 4, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.