From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 02 May 2011 16:46:27 GMT
Subject: Re: [PATCH/RFC 0/4] grep: support to match by line number
Message-ID: <7v7ha9oxss.fsf@alter.siamese.dyndns.org>
In-Reply-To: <BANLkTikvYLKKj_Wd0EOxZh+vANxju4CV6Q@mail.gmail.com>

Bert Wesarg <bert.wesarg@googlemail.com> writes:

>> Can you give a concrete example of how you'd use this? I'm not sure I
>> understand the described use case.
>
> I parse the output of compiling a file, there may be warnings or even
> errors, I collect the given line numbers, and then call 'git grep -p
> -C -n (-@ <lno>)+ -- <path>' to show me what these warnings are about.

What would you do next after doing that?  Open the file in your editor and
jump to the line found by the grep?  Oh, wait, that's the same line as
your compiler already found for you.

And when you open the file in your editor, doesn't it show offending line
in the middle of the screen?  You can even fix it up right there.  Isn't
your editor wonderful?

The extra "grep -@" step in-between looks like a totally made-up use case
that is not interesting nor convincing.