Does anyone here who uses mason and vim know how to get around this "glitch" with syntax highlighting in vim:
% elsif (exists $ARGS{change_subj}) { % $db->do(<<"DONE"); % update docdirs set title='$ARGS{title}', subj_id='$ARGS{subjid +}', % pages='$ARGS{pages}' where id='$ARGS{change_dd}';"); %DONE
is all fine and works but vim runs fowl of %DONE and the highlighting is all screwed up after that. I looked thru perl.vim and found the section dealing with here docs, but I obviously cannot figure it out because inserting a few ".?" did not work for me. I tried taking it right out but -- surprise surprise, then the here doc syntax is an error to vim and the highlighting after that is affected.

If anyone has a quick fix for this I'd be oh so grateful...

In reply to vim syntax file w/ mason & "here documents" [SOLVED] by halfcountplus

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.