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

Re: [PATCH] built-in "git grep" (git grip).

From
Jakub Narebski <jnareb@gmail.com>
Date
May 1, 2006, 07:12 UTC
Message-ID
<e34cb4$is1$1@sea.gmane.org>
In-Reply-To
<7vhd4as00i.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
Jakub Narebski <jnareb@gmail.com> writes:
> Wouldn't "git ggrep" (from git-aware grep) or "git bgrep" (from built-in
> grep), similar to the egrep and fgrep from the grep package?

Yes, I understand, but I just don't like using 'grip'. And it would be nice to have some convention for further not-ready-yet built-in replacements for script versions of commands, for example adding letter 'b' as 'built-in' at the beginning of command name: 'bgrep', 'bdiff'. Or use postfix 'n' or '-ng' to denote transitionary not-ready-yet new version of command: 'grepn', 'diffn' or 'grep-ng', 'diff-ng'.

By the way, [my] grep is linked against libpcre - would it mean that git would also need to use pcre library, or at least have an option to use it?

I also wonder if anyone would be interested to _force_ using external grep (probably enhanced)... just a thought.

-- 
Jakub Narebski
Warsaw, Poland
Previous: Junio C HamanoNext: Andreas Ericsson
Message 4 of 21 in “built-in "git grep" (git grip).”
  1. built-in "git grep" (git grip).Junio C Hamano, May 1, 2006
  2. Jakub NarebskiMay 1, 2006
  3. Junio C HamanoMay 1, 2006
  4. Jakub NarebskiMay 1, 2006
  5. Andreas EricssonMay 2, 2006
  6. Jakub NarebskiMay 2, 2006
  7. Junio C HamanoMay 2, 2006
  8. Jakub NarebskiMay 2, 2006
  9. Andreas EricssonMay 2, 2006
  10. Junio C HamanoMay 2, 2006
  11. Linus TorvaldsMay 2, 2006
  12. Junio C HamanoMay 2, 2006
  13. Linus TorvaldsMay 2, 2006
  14. Junio C HamanoMay 3, 2006
  15. built-in "git grep" (git grip) - quickfixJunio C Hamano, May 1, 2006
  16. Sam RavnborgMay 1, 2006
  17. Sam RavnborgMay 1, 2006
  18. Sam RavnborgMay 1, 2006
  19. Linus TorvaldsMay 1, 2006
  20. builtin-grep: wildcard pathspec fixesJunio C Hamano, May 1, 2006
  21. builtin-grep: do not use setup_revisions()Junio C Hamano, May 1, 2006

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.