From: Jeff King Date: Tue, 19 Jun 2018 19:11:56 GMT Subject: Re: [PATCH 0/7] grep.c: teach --column to 'git-grep(1)' Message-ID: <20180619191156.GA21641@sigill.intra.peff.net> In-Reply-To: <6ab94453-84ef-e269-c320-e102b02d6f3b@web.de> On Tue, Jun 19, 2018 at 08:50:16PM +0200, René Scharfe wrote: > Negation causes the whole non-matching line to match, with --column > reporting 1 or nothing in such a case, right? Or I think doing the > same when the operator is applied a second time is explainable. Yes to your first question. Regarding the final sentence, yes, I agree it's explainable. But I thought that handling negation like this was one of the main complaints of earlier iterations? > When ORing multiple expressions I don't pay attention to their order > as that operator is commutative. Having results depend on that > order would at least surprise me. OK. Let's just disable the short-circuit for --column then (i.e., what Taylor posted earlier). That's explainable, and I doubt the performance implications are going to be all that noticeable. -Peff