Good job describing your input and output and showing what you've tried!

I see a couple of things in your attempt that may be the problem. First, if the line actually starts ".header", you want to start your regex with m/^\.header; otherwise, you'll get false matches on "\npheader", etc., since the . will match any character. Second, your .* may match many lines worth of data. To limit it to the remainder of the .header line, say ([^\n]*\n) instead, or remove the //s flag and say (.*)\n.

Since both of these changes will cause it to match fewer inputs instead of more, if your problem is that it isn't matching at all, this won't help. Do you have your entire input in $_? If you only read one line at a time, a regex that is supposed to match across lines isn't going to do what you want.

In reply to Re: please help multiple lines parsing by ysth
in thread please help multiple lines parsing by member2004

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.