I went with that recommendation:
- like($@, qr/Cannot find directory\(ies\): $bad_gitdir/, + like($@, qr/\QCannot find directory(ies): $bad_gitdir\E/,
Although in a couple of places I had to use the \Q ... \E syntax twice within one pattern:
- like($@, qr/Cannot find file\(s\) to be tested:.*$bad_target_args +->[1]/, + like($@, qr/\QCannot find file(s) to be tested:\E.*\Q$bad_target_ +args->[1]\E/,
Thanks to all who responded. The revised code is available at Devel-Git-MultiBisect-0.07.tar.gz and should be available on CPAN within the hour. If anyone on Windows could give that a smoke test, that would be great.

Thank you very much.

Jim Keenan

In reply to Re^3: Unterminated \g... pattern in regex behaving badly on Windows by jkeenan1
in thread Unterminated \g... pattern in regex behaving badly on Windows by jkeenan1

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.