From: Thomas Volpini <tvolpini@gmx.net>
To: git@vger.kernel.org
Subject: git grep and word boundaries
Date: Tue, 27 May 2008 10:35:46 +0200 [thread overview]
Message-ID: <483BC7E2.6090804@gmx.net> (raw)
Hello,
it seems that git grep doesn't do word boundaries as described:
$ cat bar
foo bar baz
$ grep "\<bar\>" *
foo bar baz
$ git grep "\<bar\>" *
$ git grep -w "\<bar\>" *
$ git grep -w "bar" *
bar:foo bar baz
$ git grep -E "\<bar\>" *
$ git grep -E "\bbar\b" *
$
thanks,
Thomas
next reply other threads:[~2008-05-27 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 8:35 Thomas Volpini [this message]
2008-05-27 8:56 ` git grep and word boundaries Luciano Rocha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=483BC7E2.6090804@gmx.net \
--to=tvolpini@gmx.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).