Try using m#$dir# instead of /$dir/. Do not hold me to this, but I believe the slashes in the regex are confusing perl.

Perl first does double-quotish expansion ( how does this phrase seem to appear in all my posts? ) before passing anything to the regex engine. In this case, the regex engine is seeing something like /^\//acm\//. Which makes me think it is returning any line beginning with a '/'.

You could also try using the quotemeta modifiers \Q and\E which cause perl to protect all special characters with backslashes. To do this, your regex would look like /\Q$dir\E/. I had mixed luck with the quotemeta stuff a long time ago. It may work better now or your mileage may vary.

Mik
Mik Firestone ( perlus bigotus maximus )

In reply to Re: grepping for by mikfire
in thread grepping for by Anonymous Monk

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.