From: Junio C Hamano <gitster@pobox.com>
To: Matt Gardner <four712@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: macOS git grep change in required character classes
Date: Sat, 01 Apr 2023 09:27:10 -0700 [thread overview]
Message-ID: <xmqqa5zrbmap.fsf@gitster.g> (raw)
In-Reply-To: <CA+MNPvgceR3s30LaCS716NGw+8S47CQZTqFno=vE2XAuiBA7Kw@mail.gmail.com> (Matt Gardner's message of "Sat, 1 Apr 2023 11:50:28 -0400")
Matt Gardner <four712@gmail.com> writes:
> My best guess is that
> https://github.com/git/git/commit/1819ad327b7a1f19540a819813b70a0e8a7f798f
> is causing git grep -E to require BSD style regular expression
> character classes. I don't know if this is a bug or an unadvertised
> change in behavior.
I think you diagnosed it correctly. The story is "Once upon a time,
we declared that the regex library of macOS is so broken and
unusable. We used a fallback definition to work it around, but
unfortunately the fallback library did not support multi-byte
matching correctly, which made some folks on macOS unhappy. So we
let Git built with the regex library shipped with macOS starting
that commit, with one side effect that patterns you would feed Git
on that platform would behave more like patterns you give to other
tools on the platform."
So, it is not a bug in Git, it is a deliberate change in behaviour
with unintended consequences X-<.
next prev parent reply other threads:[~2023-04-01 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 15:50 macOS git grep change in required character classes Matt Gardner
2023-04-01 16:27 ` Junio C Hamano [this message]
2023-04-01 17:17 ` Matt Gardner
2023-04-01 17:56 ` Junio C Hamano
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=xmqqa5zrbmap.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=four712@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.