Syntax highlighting?
Also, it’d be helpful if the patch for checking for closed tags were implemented on here: http://trac.buddypress.org/ticket/2359
`function really () {
echo “so it would seem”;
}`
Yup, tag closing should be next 
something doesn’t seem right – everything is now in italics!
Very cool. I guess we can’t be ticked anymore.
`function i_am_ticked() {
global $bp, $whose_ticked;
if( $whose_ticked == ‘you’ && $bp->backticks != false ) {
echo “We’re sorry, you can no longer be ticked”;
} else {
echo “Yep! You’re ticked!”;
}
}`
This is an important improvement. Thanks, Ninjas!
The backticks are back; all hail the Boone, prince amongst men
@djpaul – Decided to go with the straightforward backtick before worrying about syntax highlighting, as the most popular option (Syntax Highlighter) (a) requires you to specify the language in order for highlighting to work correctly, which is a bit onerous for first time users, and (b) requires an extra click to get the popup with copyable, plaintext code, which again might be confusing for some. Maybe it makes sense to enable Syntax Highlighter as an undocumented feature, with backticks in place as a fallback? Thoughts?
‘?php backtick_is_back(); ?’
Thank you @hnla, I shall add that in BP Codex
i typed ‘backticks’ but its not working. how am i gonna use this?
