• View
• Edit
• History
• Attach
• Print
• Backlinks

SourceBlock-Talk

back to SourceBlock

Please leave the latest message at the top.

Change Request (to make code work with Precode):

  Any other similar options for setting 
    $geshi->set_header_type(GESHI_HEADER_??); 
 should work.
 
165c165,167
<     $geshi->set_header_type(GESHI_HEADER_DIV);
---
>     if(@$opt['headw']==='0')
>       $geshi->set_header_type(GESHI_HEADER_NONE);
>     else $geshi->set_header_type(GESHI_HEADER_DIV);

VKrishn July 23, 2012, at 02:27 AM

Change Request:
I propose a change in sourceblock.php to make the supported languages listing more usable by sorting it. Here is the diff output: (Note this is against version 2009-01-27.)

• instead of building only an array, use $out to hold the strings generated.

        243c243
        <   $infos = array("Geshi Version: " . GESHI_VERSION);
        ---
        >   $out = "Geshi Version: " . GESHI_VERSION;
        245c245
        <     $infos[] = "\n||border=1\n||! lang ||! full name ||";
        ---
        >     $out .= "\n||border=1\n||! lang ||! full name ||\n";

• use $lang as the index into the $infos array so it can later be sorted

        253c253
        <           $infos[] = "|| " . $lang . " ||" . $language_data['LANG_NAME'] . " ||";
        ---
        >           $infos[$lang] = "|| " . $lang . " ||" . $language_data['LANG_NAME'] . " ||";
        255c255
        <           $infos[] = "* " . $lang . "";
        ---
        >           $infos[$lang] = "* " . $lang . "";

• sorts $infos by it's keys, and implode into $out

        260c260,261
        <   $out = implode("\n", $infos) . "\n";
        ---
        >   ksort($infos);
        >   $out .= implode("\n", $infos) . "\n";

As you can see, it builds the precursors to the actual language list in the $out variable, and $infos just contains the rows of the table, using $lang as the index into the $infos array. Before joining into $out, the $infos array is key sorted. In addition, if there are wiki words in the language list, they are not enabled. --tamouse November 09, 2011, at 08:13 AM

Question: I found a bug, not sure where else to put it, but this will highlight the problem, if placed on a wiki with the SourceBlock recipe installed.

(:source lang=XML highlight='1,2' :) [=
    <!--This
        Should be highlighted -->
=]
(:source lang=XML :) [=
    <!--This
        Should NOT be highlighted -->
=]

(:source lang=Java highlight='1' :) [=
System.out.println("highlighted");
=]
(:source lang=Java :) [=
System.out.println("not highlighted");
=]

Question: how can I place ~~~~ (4 times the ~) in a codebox? Astrid May 31, 2011, at 10:15 AM

Question: Anyone got SourceBlock to work with GeSHI 1.0.8.10? I just get a blank trying to use the new version, but 1.0.8.8 works fine. Daniel Andersson 2011-04-24 08:54:47 UTC

Hi I've just done a fresh install, apart from some apache rewrites its all pretty standard so far. I'm having the strange issue that when I attempt to post a script the GetCode link has the wrong num=X, should start at 1 but they're starting at 2. Even in Site/Side bar... interestingly though num=1 works on Main/HomePage..

I encountered the problem that the Link GetCode is no longer written as GetCode but now with [$[Get Code]] ... -Markus October 12 2009

Question: Is there an easy way to add a little expand/collapse button to expand or collapse the source code block. I have code that has 100s of line of code and will be helpful. Thanks. -Shah April 23, 2009 at 02:18 PM

Nevermind - It was quite easy to implement, I just used Toggle - Shah

Regarding leading whitespace trimming: for many languages, the whitespace is significant and the first line might contain leading whitespace. If I change line 147 to restrict the trim characters:

  if(!@in_array('trim', (array)$opt['-'])) $block = trim($block, "\n\r");

it behaves as I'd like - it still trims line breaks so you don't have to cram the first line after the [@, so the wikisource is more readable. How about adding a variable in config.php to control this? Maxim? April 03, 2009, at 05:15 AM

SourceBlock is very nice and works well but I find that some of the colors really hard to read. I assume that id=ID, class=CLASS can be used in some way to modify the colors ... but how should they be used, I couldn't find an example of how to use it. j 2009-04-01

<div class='sourceblock MYCLASS' id='...'>
  <div class='sourceblocktext'>COLORIZED SOURCE CODE HERE</div>
  <div class='sourceblocklink'>...</div>
</div>

.MYCLASS .LANG .kw1 { ... }

Leading whitespace on the first line is lost.

What is the recommended way of changing colors?

I like SourceBlock very much and without external files it works for me like a charm. But I just can't get external files running.

I installed LinkedResourceExtras and as an "enduser" didn't configure anything else - although this feels a little wrong because the receipe for LinkedResourceExtras says to include_once('cookbook/extlinkedres.php'); which I couldn't find in sourceblock.php. Could you please give a complete example for an external file, e.g. http://www.gnu.org/licenses/fdl.txt?

I tried [EDIT: deleted the wrong ones]

(:source http://www.gnu.org/licenses/fdl.txt :)

and only get empty code blocks. Thanks for any help! Frank - October 12, 2007, 7:20 PM

I get an error when I try to use lang=html for some reason. If I just sub lang=php, it will highlight html, but I'm confused, since html is in the list of languages at geshi. As an example, here http://baldwinsoftware.com/wiki/pmwiki.php?n=Public.Penwell1 I am now using lang=php, because when I try to use lang=html, I get

 
GeSHi Error: GeSHi could not find the language html (using path /home/content/29/5132729/html/wiki/cookbook/geshi/geshi/) (code 2)

tonybaldwin June 03, 2011, at 08:15 AM

(:source lang=html4strict:)
<html></html>
(:sourceend:)