git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: `git grep` is too picky about option parsing

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 7, 2020, 19:35 UTC
Message-ID
<xmqqtusx9zpn.fsf@gitster.c.googlers.com>
In-Reply-To
<X856rSHziQcmr/zX@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> would be sad to lose it. (I don't use it with grep, but my standard perl
> invocation is "perl -lpe 'some script'"; another common one is "tar xvf
> foo.tar").

Heh, "tar" is a different breed, isn't it? It can have a clump of single letter options among which more than one take parameter.

> And it works now (obviously not in the case we're discussing, but in
> other cases that don't run afoul of the typo fix), so I think people
> would see that as a regression.
Sure.
Previous: Jeff King
Message 5 of 5 in “`git grep` is too picky about option parsing”
  1. Jan EngelhardtDec 6, 2020
  2. Jeff KingDec 7, 2020
  3. Junio C HamanoDec 7, 2020
  4. Jeff KingDec 7, 2020
  5. Junio C HamanoDec 7, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.