Hi Peff, On Wed, 14 May 2014, Jeff King wrote:
> On Wed, May 14, 2014 at 11:26:54AM -0700, Jonathan Nieder wrote: > > > "git grep" has other options that affect interpretation of the pattern > > which this patch does not help with: > > > > * -v / --ignore-match: probably should disable this feature of -O. > > * -E / --extended-regexp > > * -P / --perl-regexp > > * -F / --fixed-strings: ideally would auto-escape regex specials. > > * -e<pattern1> --or -e<pattern2> > > > > And git grep -Ovi has a similar bug, for which the fix is to add > > \c to the pattern instead of passing an -I option. > > We've already found the lines of interest to the user. It would be nice > if we could somehow point the pager at them by number, rather than > repeating the (slightly incompatible) search. FWIW it is exactly that type of "I want your patch to do more than you do" type of comments that makes it impossible for myself to contribute patches anymore. It just does not fit inside my Git time budget anymore. Besides, it breaks exactly the intended usage. My intent is not just to see the matching lines in the pager, but to be able to adjust the search pattern further if needed. Your suggestion completely breaks that usage. Ciao, Johannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
