From: Taylor Blau <me@ttaylorr.com>
To: David Gstir <david@sigma-star.at>
Cc: git@vger.kernel.org, "Richard Weinberger" <richard@sigma-star.at>,
"René Scharfe" <l.s.r@web.de>, "Jeff King" <peff@peff.net>
Subject: Re: git grep does not find all occurrences on macOS
Date: Mon, 14 Oct 2024 20:26:25 -0400 [thread overview]
Message-ID: <Zw22sTxyWCbczZy8@nand.local> (raw)
In-Reply-To: <771C9C4E-45F1-4F71-B3A9-4E8E4A9CAC1F@sigma-star.at>
On Mon, Oct 14, 2024 at 03:34:02PM +0200, David Gstir wrote:
> Hi!
>
> I encountered rather subtle issue on in git 2.47.0 on macOS 14.7 (installed from Homebrew):
>
> git grep will not find all occurrences of string patterns containing a “.” under some
> conditions. In my case I have an ISO-8859 encoded text file which contains umlauts.
> If the string I’m grepping for occurs after a non-ASCII character in this file, git grep
> will not find it.
>
> I’ve put up a reproducer here https://github.com/iokill/repro-git-grep-issue, but the gist
> of it is "git grep quz.baz" on the ISO-8859-encoded file below will not return anything,
> when it should return the line "quz.baz=3":
Interesting. I have a macOS system, but don't build Git on it regularly
enough to test.
I CC'd some other active contributors who have recently touched grep.c,
perhaps they may have a better insight into what is going on here.
Thanks,
Taylor
next prev parent reply other threads:[~2024-10-15 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 13:34 git grep does not find all occurrences on macOS David Gstir
2024-10-15 0:26 ` Taylor Blau [this message]
2024-10-15 20:15 ` René Scharfe
2024-10-20 11:02 ` [PATCH] grep: disable lookahead on error René Scharfe
2024-10-21 21:57 ` Taylor Blau
2024-10-22 5:58 ` David Gstir
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=Zw22sTxyWCbczZy8@nand.local \
--to=me@ttaylorr.com \
--cc=david@sigma-star.at \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=peff@peff.net \
--cc=richard@sigma-star.at \
/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).