Re: [PATCH] git-grep: --and to combine patterns with and instead of or

From: Jakub Narebski <jnareb@gmail.com>
Date: Jun 30, 2006, 19:11 UTC
Message-ID: <e83t0m$4s0$2@sea.gmane.org>
In-Reply-To: <7v1wt6ik4x.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:

Show 12 quoted lines

> The --near Matthias talk about is syntactically not like --and
> but more like --not.  It takes a condition for a line after
> that, and loosens it to cover nearby lines.  So "-e A"
> means "the line must have A on it" but "--near -e A" means "the
> line must be nearby a line that satisfies `-e A'".
> 
> Matthias's "--near EXP" is spelled as "-e '' --near EXP" (the
> first one is always true) with our syntax, in other words.
> 
> I do not think either of these semantics is invalid; they are
> just different.  The version by Matthias is more general and
> more expressive.

It also uses the fact that grep search for _lines_, the fact I have forgot about. But if we cannot search for multiline regexp using git-grep, Matthias version is truly more expressive, especially with context limiting extension.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git