Try this:
<div class="<?php post_class(); ?>" id="post-<?php the_ID(); ?>">
Pastebin also has trouble with the syntax as presented: <http://pastebin.com/t7V37aQJ>
Cheers!
Also, Steve, thanks for AppleScripts.
> --
> You received this message because you are subscribed to the
> "BBEdit Talk" discussion group on Google Groups.
> To post to this group, send email to bbe...@googlegroups.com
> To unsubscribe from this group, send email to
> bbedit+un...@googlegroups.com
> For more options, visit this group at
> <http://groups.google.com/group/bbedit?hl=en>
> If you have a feature request or would like to report a problem,
> please email "sup...@barebones.com" rather than posting to the group.
> Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
--
Lorin Rivers
Mosasaur: Killer Technical Marketing <http://www.mosasaur.com>
<mailto:lri...@mosasaur.com>
512/203.3198 (m)
> I think it's not so rare that php/html - code is mixed up in one
> document. I just switched from Coda because BBEdit does many things
> better than Coda - but i didn't even think about that highlighting issue.
> There is a document type / syntax mode for "Ruby in HTML" but what I
> really would appreciate is "PHP in HTML" or even better "Wordpress in
> HTML" : )
If you set the document type to HTML, then you get PHP (and CSS and
Javascript) syntax highlighting along for the ride automatically, and
the "clipping set" will also automatically change based on language as
you move through the document.
The case that BBEdit can't highlight correctly that Coda can in this
regard is in tag attributes:
<p><a href="<?php echo $url ?>">Click Here!</a></p>
Coda would correctly switch to the PHP scope in the HREF, while BBEdit
remains in HTML scope.
(Then again, with BBEdit I can use the "Close Tag" command to close the
</a> and </p> in that scenario, whereas Coda will be confused by the ?>
at that point, so everything's a bit of a tradeoff.)
--
Watts Martin <lay...@gmail.com>