Yet another way:
my $start_pattern = qr/.... $date/; my $end_pattern = qr/.... $date/; my $send_pattern = qr/.... whatever/; while (<LOG>) { if (my $status = /$start_pattern/..1) { print "$. : $_" if $status == 1 or /$end_pattern/ or /$send_pattern/; } }
Update: That should probably be (the first version only prints the start pattern once, this version will print it every time it occurs):
while (<LOG>) { if (/$start_pattern/..1) { print "$. : $_" if /$start_pattern/ or /$end_pattern/ or /$send_pattern/; } }
Another update: After dropping the status, I'd go with an answer with a 'next unless' like dpuu's answer below.

In reply to Re: skipping lines in a file until regexp matches by runrig
in thread skipping lines in a file until regexp matches by blueflashlight

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.