From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Richard Soderberg <rsoderberg@gmail.com>, git@vger.kernel.org
Subject: Re: git-prompt.sh incompatible with non-basic global grep.patternType
Date: Wed, 20 Jul 2016 14:52:07 -0600 [thread overview]
Message-ID: <20160720205207.GA578@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqwpkgcbp9.fsf@gitster.mtv.corp.google.com>
On Wed, Jul 20, 2016 at 01:10:42PM -0700, Junio C Hamano wrote:
> This may fix it. I think the root cause is that logic to smear
> "pattern type" into various broken-down fields in grep_opt for the
> short-hands like --basic-regexp option needs to leave "I am setting
> this short-hand" mark to allow the grep_commit_pattern_type() that
> is done as the final step of the set-up sequence before we call
> compile_grep_patterns() can take notice. The calls currently made
> to grep_set_pattern_type_option() when we parse "--basic-regexp" and
> friends forgets to override the "source of truth" field and only
> updates the broken-down fields.
>
> An alternative may be to update places that parse "--basic-regexp"
> and friends to just write to .pattern_type_option without calling
> grep_set_pattern_type_option(); that might be a cleaner, but I am
> not feeling well today so I won't be able to do a deeper analysis
> right now.
I gave a very cursory look when I wrote the other email, and your
alternative solution is what looked like the most elegant fix to me.
I suspect this bug has been there quite a while, so no rush. :)
-Peff
next prev parent reply other threads:[~2016-07-20 20:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 22:56 git-prompt.sh incompatible with non-basic global grep.patternType Richard Soderberg
2016-07-19 11:24 ` Johannes Schindelin
2016-07-19 14:14 ` Richard Soderberg
2016-07-19 14:35 ` Johannes Schindelin
2016-07-20 13:42 ` Jeff King
2016-07-20 20:10 ` Junio C Hamano
2016-07-20 20:52 ` Jeff King [this message]
2016-07-22 19:21 ` Junio C Hamano
2016-07-22 19:28 ` Jeff King
2016-07-22 19:51 ` Junio C Hamano
2016-07-22 20:05 ` Jeff King
2016-07-22 20:33 ` Junio C Hamano
2016-07-22 23:28 ` Eric Sunshine
2016-07-25 16:16 ` 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=20160720205207.GA578@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rsoderberg@gmail.com \
/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).