On Thu, Sep 18, 2008 at 08:28, Johan Herland <johan@xxxxxxxxxxx> wrote: > Hi, > > 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... > > The only working solution I've found so far is to create a file > (named "cr") in a hex editor that contains exactly one CR byte, and > then use the -f option to 'git grep': > > git grep --cached -I -l -f cr > > Is there an easier way? And if not, should I try to create one (e.g. > teaching 'git grep' to grok backslash escapes)? > > > Have fun! > > ...Johan > > -- > Johan Herland, <johan@xxxxxxxxxxx> > www.herland.net > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Inserting a literal carriage return seems to do the trick for me, in bash. git grep --cached -I -l -e <Ctrl-V><Ctrl-M> -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
