SyntaxHighlighter Evolved

In Reply To Gabriel Mariani:

Thanks, but since this code is so widely used, I’d prefer to use only code that has been validated/reviewed by Alex himself. I’ll wait until he okays it.

In Reply To rsjs:

No idea about the VB.

Some documentation is available at the bottom of the settings page as well as here: http://en.support.wordpress.com/code/posting-source-code/

In Reply To Kevin S:

See the second question: http://wordpress.org/extend/plugins/syntaxhighlighter/faq/

In Reply To Jimmy Burnett:

Your theme is likely missing the required footer hook: http://wordpress.org/extend/plugins/syntaxhighlighter/faq/

Jean-Pierre de la Croix on January 26th, 2010 at 10:38 PM2010-01-27T06:38:58ZF jS, Y \a\t g:i A wrote:

Would it be possible to modify the plugin, such that the line numbers and code are separate? It’d be great if the line numbers were not included when one tries to highlight a portion of the code for a copy&paste (else, you have to manually delete the line numbers after the paste).

Currently, one has to copy the code to the clipboard and then pick out the lines, but it’d be better if that could be done directly on the site instead of on the clipboard.

P.S.: Great work on this plugin!

Use the toolbar in the upper-right of the code box. It’s there for a reason and allows you to see the raw code as well as one-click directly to your clipboard.

In Reply To TokkonoPaPa:

I did not write the highlighter, just the WordPress implementation of it. You’d need to take that up with the author of the Javascript package.

In Reply To TokkonoPaPa:

Ah, I was unaware that it would work without semi-colons. Thanks.

In Reply To Reuben:

Are you using an editor other than the one in your WordPress admin area by chance? You could also have other plugins that are breaking it. Works fine for me:

#!/bin/bash
FROM=1
NUM=44
DEV=/dev/powerfilecd1
function log {
    echo `date` $1
}
function cleanup {
    pkill abcde
    rm -fr abcde*
    echo Rip of cd $1 failed >> error.log
}
function monitorrip {
    {
        while read line
            do
                log "$line"
                # cdparanoia keeps chundering forward even if there's a scsi_read error
                # this slows things down unacceptably, so we'll just kill the job and move forward
                echo "$line" | grep "scsi_read error" && cleanup $1 && break
            done
    } | tee
}
function ripcd {
    # look for scsi read errors
    abcde -d $DEV -NV 2>&1 | monitorrip $1
}
function loadcd {
    date
    # load the cd into the drive, and send the sdparm eject command to make udev notice
    mtx load $1
    sdparm -C eject $DEV
}
function unloadcd {
    date
    # send sdparm and eject to flush the cd devices
    sdparm -C stop $DEV
    # not strictly necessary, but your desktop environment might be automounting,
    # so this will force a umount if applicable
    eject $DEV
    sleep 7
    mtx unload $1
}
function rip {
   for n in `seq $FROM $NUM`
   do
        echo ____________________________________________________________
        echo RIPPING CD $n
        echo ____________________________________________________________
        date
        loadcd $n
        ripcd $n
        unloadcd $n
   done
}
function reset {
    echo Resetting jukebox position
    # this shouldn't be necessary but seems to fix an error condition
    mtx first
    mtx unload 1
}
reset
rip | tee output.txt

In Reply To Reuben:

Interesting. I’ll see if I can reproduce/debug/fix.

In Reply To Fernando:

Visit the settings page. You can control the clickable URLs option there.

In Reply To Fernando:

Oh, I see — another plugin is causing the issue. It should be modified to not touch anything inside of <pre> tags. My plugin is not at fault.

In Reply To Fernando:

Exactly. This “SEO smart links” plugin is at fault.

Fernando on February 4th, 2010 at 12:13 AM2010-02-04T08:13:42ZF jS, Y \a\t g:i A wrote:

And any clues about how to fix it?

That is something you’d need to take up with the plugin’s author (tell them not to touch anything inside of pre tags).

In Reply To Fernando:

Then how would someone post the source code of a link? I’m sorry, but there’s nothing that can be done on my end.

In Reply To Kristoffer:

http://wordpress.org/extend/plugins/syntaxhighlighter/faq/

In Reply To Federico:

wp_footer() is a required WordPress theme hook. All themes need to have it. It doesn’t really matter where it is (it could be in your sidebar if you wanted), but it needs to be somewhere.

In Reply To BdF:

Try switching to HTML view if you’re using TinyMCE. TinyMCE can be buggy.

In Reply To Mitko:

Sounds like another plugin is causing the issue as pages are literally just a type of post. My plugin doesn’t know the difference.