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

Re: How to supply "raw" bytes to git grep?

From
Jakub Narebski <jnareb@gmail.com>
Date
Sep 18, 2008, 16:31 UTC
Message-ID
<gatvp0$kl0$1@ger.gmane.org>
In-Reply-To
<200809181728.18597.johan@herland.net>
Johan Herland wrote:
Show 8 quoted lines
> I wanted to list all text files in my repo which contain carriage 
> returns, so I tried the following command-line:
> 
>       git grep --cached -I -l -e <CR>
> 
> where <CR> is some magic incantation that I've yet to figure out. I've 
> tried all the obvious cases (\r, 0x0d, \015, etc.), but none of them 
> seem to DWIM...

Why not use _literal_ CR; of course protecting it by piockung it by shell as end of command by quites, for example

  $ git grep --cached -I -l -e '
  '
It works for me (bash).
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Kalle Olavi Niemitalo
Message 5 of 5 in “How to supply "raw" bytes to git grep?”
  1. Johan HerlandSep 18, 2008
  2. Jacob HelwigSep 18, 2008
  3. Johan HerlandSep 18, 2008
  4. Kalle Olavi NiemitaloSep 18, 2008
  5. Jakub NarebskiSep 18, 2008

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.