kmx.io/prism.js

diff --git a/examples/prism-clike.html b/examples/prism-clike.html
new file mode 100644
index 0000000..a1ec32f
--- /dev/null
+++ b/examples/prism-clike.html
@@ -0,0 +1,39 @@
+<h1>C-like</h1>
+<p>The C-like component is not really a language on its own,
+	it is the basis of many other components. To use it directly, however,
+	use the class "language-clike".</p>
+
+<h2>Comments</h2>
+<pre><code>// Single line comment
+/* Multi-line
+comment */</code></pre>
+
+<h2>Strings</h2>
+<pre><code>"foo \"bar\" baz";
+'foo \'bar\' baz';</code></pre>
+
+<h2>Numbers</h2>
+<pre><code>123
+123.456
+-123.456
+1e-23
+123.456E789
+0xaf
+0xAF
+</code></pre>
+
+<h2>Functions</h2>
+<pre><code>foo();
+Bar();
+_456();
+</code></pre>
+
+<h2>Known failures</h2>
+<p>There are certain edge cases where Prism will fail.
+	There are always such cases in every regex-based syntax highlighter.
+	However, Prism dares to be open and honest about them.
+	If a failure is listed here, it doesn’t mean it will never be fixed. This is more of a “known bugs” list, just with a certain type of bug.
+</p>
+
+<h3>Comment-like substrings</h3>
+<pre><code>"foo /* bar */ baz"; "foo // bar";</code></pre>
\ No newline at end of file
diff --git a/examples/prism-csharp.html b/examples/prism-csharp.html
new file mode 100644
index 0000000..84d760f
--- /dev/null
+++ b/examples/prism-csharp.html
@@ -0,0 +1,69 @@
+<h1>C#</h1>
+<p>To use this language, use the class "language-csharp".</p>
+
+<h2>Comments</h2>
+<pre><code>// Single line comment
+/* Multi-line
+comment */</code></pre>
+
+<h2>Strings</h2>
+<pre><code>"foo \"bar\" baz"
+'foo \'bar\' baz'
+@"Verbatim strings"
+</code></pre>
+
+<h2>Full example</h2>
+<pre><code>using System.Windows.Forms;
+using System.Drawing;
+
+public static DialogResult InputBox(string title, string promptText, ref string value)
+{
+  Form form = new Form();
+  Label label = new Label();
+  TextBox textBox = new TextBox();
+  Button buttonOk = new Button();
+  Button buttonCancel = new Button();
+
+  form.Text = title;
+  label.Text = promptText;
+  textBox.Text = value;
+
+  buttonOk.Text = "OK";
+  buttonCancel.Text = "Cancel";
+  buttonOk.DialogResult = DialogResult.OK;
+  buttonCancel.DialogResult = DialogResult.Cancel;
+
+  label.SetBounds(9, 20, 372, 13);
+  textBox.SetBounds(12, 36, 372, 20);
+  buttonOk.SetBounds(228, 72, 75, 23);
+  buttonCancel.SetBounds(309, 72, 75, 23);
+
+  label.AutoSize = true;
+  textBox.Anchor = textBox.Anchor | AnchorStyles.Right;
+  buttonOk.Anchor = AnchorStyles.Bottom | AnchorStyles.Right;
+  buttonCancel.Anchor = AnchorStyles.Bottom | AnchorStyles.Right;
+
+  form.ClientSize = new Size(396, 107);
+  form.Controls.AddRange(new Control[] { label, textBox, buttonOk, buttonCancel });
+  form.ClientSize = new Size(Math.Max(300, label.Right + 10), form.ClientSize.Height);
+  form.FormBorderStyle = FormBorderStyle.FixedDialog;
+  form.StartPosition = FormStartPosition.CenterScreen;
+  form.MinimizeBox = false;
+  form.MaximizeBox = false;
+  form.AcceptButton = buttonOk;
+  form.CancelButton = buttonCancel;
+
+  DialogResult dialogResult = form.ShowDialog();
+  value = textBox.Text;
+  return dialogResult;
+}</code></pre>
+
+<h2>Known failures</h2>
+<p>There are certain edge cases where Prism will fail.
+	There are always such cases in every regex-based syntax highlighter.
+	However, Prism dares to be open and honest about them.
+	If a failure is listed here, it doesn’t mean it will never be fixed. This is more of a “known bugs” list, just with a certain type of bug.
+</p>
+
+<h3>Comment-like substrings</h3>
+<pre><code>"foo /* bar */ baz"; "foo // bar";</code></pre>
\ No newline at end of file
diff --git a/examples/prism-gherkin.html b/examples/prism-gherkin.html
new file mode 100644
index 0000000..bc76f8c
--- /dev/null
+++ b/examples/prism-gherkin.html
@@ -0,0 +1,31 @@
+<h1>Gherkin</h1>
+<p>To use this language, use the class "language-gherkin".</p>
+
+<h2>Comments</h2>
+<pre><code>// Single line comment
+/* Multi-line
+comment */</code></pre>
+
+<h2>Strings</h2>
+<pre><code>"foo \"bar\" baz"
+'foo \'bar\' baz'</code></pre>
+
+<h2>Keywords</h2>
+<pre><code>Feature: Some terse yet descriptive text of what is desired
+  In order to realize a named business value
+  As an explicit system actor
+  I want to gain some beneficial outcome which furthers the goal
+
+  Additional text...
+
+  Scenario: Some determinable business situation
+    Given some precondition
+    And some other precondition
+    When some action by the actor
+    And some other action
+    And yet another action
+    Then some testable outcome is achieved
+    And something else we can check happens too
+
+  Scenario: A different situation
+    ...</code></pre>
diff --git a/examples/prism-groovy.html b/examples/prism-groovy.html
new file mode 100644
index 0000000..d4f0f8f
--- /dev/null
+++ b/examples/prism-groovy.html
@@ -0,0 +1,96 @@
+<h1>Groovy</h1>
+<p>To use this language, use the class "language-groovy".</p>
+
+<h2>Comments</h2>
+<pre><code>// Single line comment
+/* Multi-line
+comment */</code></pre>
+
+<h2>Strings</h2>
+<pre><code>"foo 'bar' baz"
+'foo "bar" baz'
+"""Multi-line
+string"""
+'''Multi-line
+string'''
+"String /containing/ slashes"
+</code></pre>
+
+<h2>Slashy strings (regex)</h2>
+<pre><code>/.*foo.*/
+/regex"containing quotes"/
+$/.*"(.*)".*/(.*)/$</code></pre>
+
+<h2>Interpolation inside GStrings and regex</h2>
+<pre><code>"The answer is ${21*2}"
+"The $foxtype ${foxcolor.join()} fox"
+/foo${21*2}baz/
+'No interpolation here : ${21*2}'</code></pre>
+
+<h2>Full example</h2>
+<pre><code>/*
+    The input string to parse is from...
+    <...the rest of the header comment from above...>
+*/
+boolean debugging = true
+
+if (debugging) {
+    // Test data
+    dfkOutput = '''
+Filesystem           1K-blocks      Used Available Use% Mounted on
+/dev/sda1              4185956   1206996   2762888  31% /
+/dev/sda11            30679784  28324040    772140  98% /extra
+fas3050c-1-2.b:/vol/canis
+                      10485760   6599936   3885824  63% /nfs/data_d2/dog_data
+fas6070-1-1.b:/vol/felis
+                     314572800  54889600 259683200  18% /nfs/DATA-1/cat_data
+'''
+} else {
+    // Real data
+    dfkOutput = 'df -k'.execute().text
+}
+
+long kbAvail = 0
+
+regex =  '''(?ix)      # enable case-insensitive matches, extended patterns
+            (\\d+)     # 1: The disk space we want
+            \\s+       # some whitespace
+            \\d+%      # a number followed by??%
+            \\s+       # some more whitespace
+            (/nfs/data.*)  # 2: partition name'''
+
+pattern = ~regex
+matcher = pattern.matcher(dfkOutput)
+
+if (debugging) {
+    println """matcher pattern:
+/---------------------------------\\
+${matcher.pattern()}
+\\---------------------------------/"""
+
+    println "match count=${matcher.getCount()}"
+}
+
+for (i=0; i < matcher.getCount(); i++) {
+    if (debugging) {
+        println "    text matched in matcher[${i}]: '" + matcher[i][0] + "'"
+        println "        free space in  (group 1): '" + matcher[i][1] + "'"
+        println "        partition name (group 2): '" + matcher[i][2] + "'"
+    }
+    kbAvail += matcher[i][1].toLong()
+}
+
+println "KB available=${kbAvail}"</code></pre>
+
+<h2>Known failures</h2>
+<p>There are certain edge cases where Prism will fail.
+	There are always such cases in every regex-based syntax highlighter.
+	However, Prism dares to be open and honest about them.
+	If a failure is listed here, it doesn’t mean it will never be fixed. This is more of a “known bugs” list, just with a certain type of bug.
+</p>
+
+<h3>Comment-like substrings</h3>
+<pre><code>"foo /* bar */ baz"; "foo // bar";</code></pre>
+
+<h3>Slashy strings containing (escaped) slashes</h3>
+<pre><code>/foo\/bar/</code></pre>
\ No newline at end of file
diff --git a/examples/prism-java.html b/examples/prism-java.html
new file mode 100644
index 0000000..14e0a19
--- /dev/null
+++ b/examples/prism-java.html
@@ -0,0 +1,76 @@
+<h1>Java</h1>
+<p>To use this language, use the class "language-java".</p>
+
+<h2>Comments</h2>
+<pre><code>// Single line comment
+/* Multi-line
+comment */</code></pre>
+
+<h2>Strings</h2>
+<pre><code>"foo \"bar\" baz";
+'foo \'bar\' baz';</code></pre>
+
+<h2>Numbers</h2>
+<pre><code>123
+123.456
+-123.456
+.3f
+1.3e9d
+0xaf
+0xAF
+0xFF.AEP-4
+</code></pre>
+
+<h2>Full example</h2>
+<pre><code>import java.util.Scanner;
+
+public class Life {
+    public static void show(boolean[][] grid){
+        String s = "";
+        for(boolean[] row : grid){
+            for(boolean val : row)
+                if(val)
+                    s += "*";
+                else
+                    s += ".";
+            s += "\n";
+        }
+        System.out.println(s);
+    }
+
+    public static boolean[][] gen(){
+        boolean[][] grid = new boolean[10][10];
+        for(int r = 0; r < 10; r++)
+            for(int c = 0; c < 10; c++)
+                if( Math.random() > 0.7 )
+                    grid[r][c] = true;
+        return grid;
+    }
+
+    public static void main(String[] args){
+        boolean[][] world = gen();
+        show(world);
+        System.out.println();
+        world = nextGen(world);
+        show(world);
+        Scanner s = new Scanner(System.in);
+        while(s.nextLine().length() == 0){
+            System.out.println();
+            world = nextGen(world);
+            show(world);
+
+        }
+    }
+
+	// [...]
+}</code></pre>
+
+<h2>Known failures</h2>
+<p>There are certain edge cases where Prism will fail.
+	There are always such cases in every regex-based syntax highlighter.
+	However, Prism dares to be open and honest about them.
+	If a failure is listed here, it doesn’t mean it will never be fixed. This is more of a “known bugs” list, just with a certain type of bug.
+</p>
+
+<h3>Comment-like substrings</h3>
+<pre><code>"foo /* bar */ baz"; "foo // bar";</code></pre>
\ No newline at end of file
diff --git a/examples/prism-nsis.html b/examples/prism-nsis.html
new file mode 100644
index 0000000..d8cb73c
--- /dev/null
+++ b/examples/prism-nsis.html
@@ -0,0 +1,32 @@
+<h1>NSIS</h1>
+<p>To use this language, use the class "language-nsis".</p>
+
+<h2>Comments</h2>
+<pre><code>; Single line comment
+# Single line comment
+/* Multi-line
+comment */</code></pre>
+
+<h2>Strings</h2>
+<pre><code>"foo \"bar\" baz"
+'foo \'bar\' baz'</code></pre>
+
+<h2>Variables</h2>
+<pre><code>LicenseLangString myLicenseData ${LANG_ENGLISH} "bigtest.nsi"
+LicenseData $(myLicenseData)
+StrCmp $LANGUAGE ${LANG_ENGLISH} 0 +2</code></pre>
+
+<h2>Compiler commands</h2>
+<pre><code>!define VERSION "1.0.3"
+!insertmacro MyFunc ""</code></pre>
+
+<h2>Known failures</h2>
+<p>There are certain edge cases where Prism will fail.
+	There are always such cases in every regex-based syntax highlighter.
+	However, Prism dares to be open and honest about them.
+	If a failure is listed here, it doesn’t mean it will never be fixed. This is more of a “known bugs” list, just with a certain type of bug.
+</p>
+
+<h3>Comment-like substrings</h3>
+<pre><code>"foo /* bar */ baz"
+"foo ; bar";</code></pre>
\ No newline at end of file
diff --git a/examples/prism-rip.html b/examples/prism-rip.html
new file mode 100644
index 0000000..5d19279
--- /dev/null
+++ b/examples/prism-rip.html
@@ -0,0 +1,15 @@
+<h1>Rip</h1>
+<p>To use this language, use the class "language-rip".</p>
+
+<h2>Comments</h2>
+<pre><code># This is a comment</code></pre>
+
+<h2>Strings</h2>
+<pre><code>"foo \"bar\" baz"
+'foo \'bar\' baz'</code></pre>
+
+<h2>Regex</h2>
+<pre><code>regular_expression = /abc/</code></pre>
+
+<h2>Symbols</h2>
+<pre><code>string_symbol = :rip </code></pre>
\ No newline at end of file
diff --git a/examples/prism-scss.html b/examples/prism-scss.html
new file mode 100644
index 0000000..bc42e66
--- /dev/null
+++ b/examples/prism-scss.html
@@ -0,0 +1,44 @@
+<h1>Sass (Scss)</h1>
+<p>To use this language, use the class "language-scss".</p>
+
+<h2>Comments</h2>
+<pre><code>// Single line comment
+/* Multi-line
+comment */</code></pre>
+
+<h2>At-rules</h2>
+<pre><code>@import "foo.scss";
+@media (min-width: 600px) {}
+.seriousError {
+    @extend .error;
+}
+@for $i from 1 through 3 {}
+</code></pre>
+
+<h2>Compass URLs</h2>
+<pre><code>@font-face {
+	font-family: "opensans";
+	src: font-url("opensans.ttf");
+}</code></pre>
+
+<h2>Variables</h2>
+<pre><code>$width: 5em;
+#main {
+    width: $width;
+}</code></pre>
+
+<h2>Interpolations are highlighted in property names</h2>
+<pre><code>p.#{$name} {
+    #{$attr}-color: blue;
+}
+</code></pre>
+
+<h2>Known failures</h2>
+<p>There are certain edge cases where Prism will fail.
+    There are always such cases in every regex-based syntax highlighter.
+    However, Prism dares to be open and honest about them.
+    If a failure is listed here, it doesn’t mean it will never be fixed. This is more of a “known bugs” list, just with a certain type of bug.
+</p>
+
+<h3>Media queries are not highlighted properly when not starting with a parenthesis.</h3>
+<pre><code>@media screen {}</code></pre>
\ No newline at end of file