From: Junio C Hamano <gitster@pobox•com>
To: Noel Grandin <noelgrandin@gmail•com>
Cc: "git\@vger.kernel.org" <git@vger•kernel.org>
Subject: Re: bug: git grep -P and multiline mode
Date: Mon, 23 Jun 2014 10:42:18 -0700 [thread overview]
Message-ID: <xmqqa993cykl.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <53A7CF25.7060508@gmail.com> (Noel Grandin's message of "Mon, 23 Jun 2014 08:54:29 +0200")
Noel Grandin <noelgrandin@gmail•com> writes:
> It looks like the perl regular expression multiline mode does not work with 'git grep'
Yes, and deliberately so, to avoid having to think about things like
"how would a multi-line match interact with 'grep -n'?"
We behave as if we feed each line of the contents one line at a time
to the matching engine that is chosen by the -P/-E/-G/-F optoins, so
this limitation is unlikely to change.
next prev parent reply other threads:[~2014-06-23 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 6:54 bug: git grep -P and multiline mode Noel Grandin
2014-06-23 17:42 ` Junio C Hamano [this message]
2014-06-24 7:34 ` Noel Grandin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqa993cykl.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=noelgrandin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox