I'm new to BBEdit, but have been using TextWrangler quite a while, and this is handled in TextWrangler just fine. My assumption is that TW is a subset of BBEdit. So shouldn't it work in BBE? Is my assumption wrong?
That being said, in TW, I would've put a space between "standard" and the php tag, plus used the full tag. Could that be what's throwing it off here? On 12/18/10, stephen taylor <[email protected]> wrote: > I would like to my voice to this and further add that, while I love BBEdit, > it does not handle php with or without HTML very well. I do a lot of Drupal > and have assigned both the .tpl.php and .module extensions to php. As with a > "pure" php script, the highlighting is flaky but actually is the least of my > issues: > > 1) no matter how I try I cannot get anything other than functions to fold. > To wit: suppose you have a set of detailed foreach statements within which > you execute some logic (very common in Drupal as there are many nested > associative arrays to deal with). Unlike other languages (such as > javascript), these cannot be folded and I must resort to manually selecting > and then folding. Very inconvenient. > > 2) in php with HTML, it is really, really a pain that elements do not > fold-unfold as in HTML. I have found it necessary to maintain 2 scripts, in > these cases to make sure that my HTML structures are balanced: 1 to debug in > a .html script (behaves as long as there is no php in there) and then the > "real script" where I have to paste the other script in. Painful and prone > to errors. > > I will try to find to the time to send my issue to BBEdit support with more > detail. > > But if anyone has ideas, I would really appreciate it. > > S > > On Fri, Dec 17, 2010 at 1:55 PM, eeerlend <[email protected]> wrote: > >> Hi! >> >> Im not sure this is the right place to post this, but I'll give it a >> try! >> >> When I'm coding php mixed with html, like this; >> >> <div class="span-14" id="content-standard<?=$style_variant?>"> >> >> the starting and closing php thing (<?/<?php and ?>) isn't displayed >> with color red, as it normally does. This is annoying, because it is >> in situations like this the syntax coloring is useful to quick find >> errors in the code. Seems like the php code inside is not colored as >> php either... This seem to happen each time the php code is inside an >> attribute of the html. >> >> Same result with >> >> <div class="span-14" id="content-standard<?php echo $style_variant; ? >> >"> >> >> Dreamweaver can do dis;) Hope this will be fixed in the next update, >> because I want to use BBEdit because of the lightweight. >> >> eeerlend >> >> -- >> 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 [email protected] >> To unsubscribe from this group, send email to >> [email protected]<bbedit%[email protected]> >> 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 "[email protected]" rather than posting to the group. >> Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> >> > > -- > 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 [email protected] > To unsubscribe from this group, send email to > [email protected] > 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 "[email protected]" rather than posting to the group. > Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> > -- 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 [email protected] To unsubscribe from this group, send email to [email protected] 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 "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
