capynet

Server side syntax highlighter based on Pygments highlighter software.
<h3>Installation:</h3>
To use this plugin you need pygments in your server:
<pre><code>sudo apt-get install python-setuptools
easy_install Pygments
</code></pre>
That’s all. Now you can download the plugin and install it in your WordPress.
<h3>Usage</h3>
Once you get installed the plugin the usage is straightforward. just enclose your code between tokens named with the corresponding lang:
<pre><code>[javascript]....[/javascript]
[php]....[/php]
</code></pre>
See “Languages and filetypes supported” section to know available languages.
<h4>Parameters</h4>
Tokens support a few parameters (all optionals):
<pre><code>[php **style**="manni" **linenumbers**="table"]....[/php]

style="manni" defines code styling. Currently are 22 available styles. 
</code></pre>
Default styling is <code>default</code> wich is very nice, but maybe you like other styles. see “Color styles” section.
If you set “linenumbers” to <code>inline</code> or <code>table</code>, the line numbers will be added as independent table column or as part of the line.
<h4>Examples</h4>
<pre><code>`
</code></pre>
[javascript] 
//comment line 
var foo = “foo”; 
var bar = function(){ 
 var baz; 
} 
[/javascript] 
 `
Outputs highlighted js with default style, and no line numbers.
<pre><code>`
</code></pre>
[javascript style=”monokai” linenumbers=”inline”] 
//comment line 
var foo = “foo”; 
var bar = function(){ 
 var baz; 
} 
[/javascript] 
 ` 
Outputs highlighted js with monokai style with line numbers (as part of the line).
<pre><code>`
</code></pre>
[javascript style=”monokai” linenumbers=”table”] 
//comment line 
var foo = “foo”; 
var bar = function(){ 
 var baz; 
} 
[/javascript] 
 ` 
Outputs highlighted js with monokai style with line numbers (as new column).
<h3>Color styles</h3>
These are supported color styles:
<ul>
<li><code>monokai</code></li>
<li><code>manni</code></li>
<li><code>rrt</code></li>
<li><code>perldoc</code></li>
<li><code>borland</code></li>
<li><code>colorful</code></li>
<li><code>default</code></li>
<li><code>murphy</code></li>
<li><code>vs</code></li>
<li><code>trac</code></li>
<li><code>tango</code></li>
<li><code>fruity</code></li>
<li><code>autumn</code></li>
<li><code>bw</code></li>
<li><code>emacs</code></li>
<li><code>vim</code></li>
<li><code>pastie</code></li>
<li><code>friendly</code></li>
<li><code>native</code></li>
</ul>
<h3>Languages and filetypes supported</h3>
Pygments not only highlights languages. also highlights filetypes like .conf Nginx configuration file, Apache (filenames .htaccess, apache.conf, apache2.conf), etc.
NOTE: to use see “Usage” section
important sdsd;
General
<ul>
<li><code>apacheconf</code>: (.htaccess, apache.conf, apache2.conf)</li>
<li><code>bash</code>, <code>sh</code>, <code>ksh</code>: 
(*.sh, *.ksh, *.bash, *.ebuild, *.eclass, .bashrc, bashrc)</li>
<li><code>ini</code>, <code>cfg</code>: (*.ini, *.cfg)</li>
<li><code>makefile</code>: 
(.mak, Makefile, makefile, Makefile., GNUmakefile)</li>
<li><code>nginx</code>: 
Nginx configuration file </li>
<li><code>yaml</code>: 
(*.yaml, *.yml)</li>
<li><code>perl</code>: 
Perl (*.pl, *.pm)</li>
<li><code>vb.net</code>: 
VB.net (*.vb, *.bas)</li>
<li><code>console</code>: 
Bash Session (*.sh-session)</li>
</ul>
Javascript
<ul>
<li><code>javascript</code>: Pure Javascript</li>
<li><code>coffeescript</code>: Pure CoffeeScript</li>
<li><code>json</code>: Pure JSON</li>
</ul>
PHP
<ul>
<li><code>cssphp</code>: PHP embedded in CSS</li>
<li><code>htmlphp</code>: PHP embedded in HTML</li>
<li><code>jsphp</code>: PHP embedded in JS</li>
<li><code>php</code>: Pure PHP</li>
<li><code>xmlphp</code>: PHP embedded in XML</li>
</ul>
Ruby
<ul>
<li><code>ruby</code>, <code>duby</code>: Ruby (*.rb, *.rbw, *.rake, *.gemspec, *.rbx, *.duby)</li>
<li><code>csserb</code>, <code>cssruby</code>: Ruby embedded in CSS</li>
<li><code>xmlerb</code>, <code>xmlruby</code>: Ruby embedded in XML</li>
</ul>
CSS and CSS compilers
<ul>
<li><code>css</code>: 
CSS (*.css)</li>
<li><code>sass</code>: 
Sass (*.sass)</li>
<li><code>scss</code>: 
SCSS (*.scss)</li>
</ul>
HTML and HTML template systems
<ul>
<li><code>html</code>: 
HTML (*.html, *.htm, *.xhtml, *.xslt)</li>
<li><code>haml</code>: 
Haml (*.haml)</li>
<li><code>jade</code>: 
Jade (*.jade)</li>
</ul>
SQL
<ul>
<li><code>sql</code>: 
SQL (*.sql)</li>
<li><code>sqlite3</code>: 
sqlite3con (*.sqlite3-console)</li>
<li><code>mysql</code>: 
MySQL </li>
</ul>
Python, jinja & Django
<ul>
<li><code>python</code>: Pure Python</li>
<li><code>python3</code>: Pure Python 3 </li>
<li><code>xmldjango</code>, <code>xmljinja</code>: Django/Jinja embedded in XML</li>
<li><code>cssdjango</code>, <code>cssjinja</code>: Django/Jinja embedded in CSS</li>
<li><code>django</code>, <code>jinja</code>: Pure Django/Jinja </li>
<li><code>htmldjango</code>, <code>htmljinja</code>: Django/Jinja embedded in HTML</li>
<li><code>jsdjango</code>, <code>jsjinja</code>: Django/Jinja embedded in Javascript</li>
</ul>
Java && family
<ul>
<li><code>java</code>: 
Java (*.java)</li>
<li><code>clojure</code>: 
clojure (*.clj)</li>
<li><code>groovy</code>: 
Groovy (*.groovy)</li>
<li><code>jsp</code>: 
Java Server Page (*.jsp)</li>
</ul>
C, C++, Objetive-c, C Sharp
<ul>
<li><code>cobjdump</code>: c-objdump (*.c-objdump)</li>
<li><code>c</code>: C (*.c, *.h, *.idc)</li>
<li><code>cpp</code>: C++ (*.cpp, *.hpp, *.c++, *.h++, *.cc, *.hh, *.cxx, *.hxx)</li>
<li><code>csharp</code>: C# (*.cs)</li>
<li><code>objectivec</code>: (*.m)</li>
</ul>
XML
<ul>
<li><code>xml</code>: (*.xml, *.xsl, *.rss, *.xslt, *.xsd, *.wsdl)</li>
<li><code>xslt</code>: (*.xsl, *.xslt)</li>
</ul>

WPygments

Server side syntax highlighter based on Pygments highlighter software.

Weston Ruter

Vladimir Jimenez

This plugin extends the Code block in WordPress core to add syntax highlighting which is rendered on the server. Pre-existing Code blocks on a site are automatically extended to include syntax highlighting. Doing server-side syntax highlighting eliminates the need to enqueue any JavaScript on the frontend (e.g. Highlight.js or Prism.js) and this ensures there is no flash of unhighlighted code (FOUC?). Reducing script on the frontend improves frontend performance, and it also allows for the syntax highlighted code to appear properly in AMP pages as rendered by the <a href="https://amp-wp.org" rel="nofollow ugc">official AMP plugin</a> (see also <a href="https://github.com/ampproject/amp-wp/issues/972" rel="nofollow ugc">ampproject/amp-wp#972</a>) or when JavaScript is turned off in the browser.
This extended Code block uses language auto-detection to add syntax highlighting, but you can override the language in the block’s settings sidebar. (There is currently no syntax highlighting of the Code block in the editor, but see <a href="https://github.com/westonruter/syntax-highlighting-code-block/issues/8" rel="nofollow ugc">#8</a>.) The plugin supports all <a href="https://highlightjs.org/static/demo/" rel="nofollow ugc">programming languages</a> that <a href="https://github.com/scrivo/highlight.php" rel="nofollow ugc">highlight.php</a> supports (being a port of <a href="https://highlightjs.org/" rel="nofollow ugc">highlight.js</a>). The Code block also is extended to support specifying lines to highlight which get marked up with <code>mark</code> elements (including in RSS feeds). There is also a checkbox for whether to show line numbers on the frontend (with the numbers being non-selectable). Lastly, given inconsistencies across themes regarding whether lines in a Code block should be wrapped, this plugin adds styling to force them to no-wrap by default, with a checkbox to opt in to wrapping when desired.
For advanced usage, please see the <a href="https://github.com/westonruter/syntax-highlighting-code-block/wiki" rel="nofollow ugc">plugin wiki</a>.
This plugin is <a href="https://github.com/westonruter/syntax-highlighting-code-block" rel="nofollow ugc">developed on GitHub</a>. See <a href="https://github.com/westonruter/syntax-highlighting-code-block/issues" rel="nofollow ugc">list of current issues</a> with the plugin. Please feel free to file any additional issues or requests that you may come across. <a href="https://github.com/westonruter/syntax-highlighting-code-block/pulls" rel="nofollow ugc">Pull requests</a> are welcome. See <a href="https://github.com/westonruter/syntax-highlighting-code-block/wiki/Contributing" rel="nofollow ugc">contributing information</a>.
<h4>Credits</h4>
This is a fork of <a href="https://github.com/mkaz/code-syntax-block" rel="nofollow ugc">Code Syntax Block</a> by <a href="https://mkaz.blog/" rel="nofollow ugc">Marcus Kazmierczak</a> (mkaz), which is also <a href="https://wordpress.org/plugins/code-syntax-block/" rel="ugc">available on WordPress.org</a>. Copyright (c) 2018 Marcus Kazmierczak. Licensed under GPL 2.0 or later.
<a href="https://github.com/scrivo/highlight.php" rel="nofollow ugc">highlight.php</a> is released under the BSD 3-Clause License. Copyright © 2006-2013, Ivan Sagalaev (maniac@softwaremaniacs.org), highlight.js (original author). Copyright © 2013, Geert Bergman (geert@scrivo.nl), highlight.php

Syntax-highlighting Code Block (with Server-side Rendering)

I love that this is baked into the core code block without having to resort to a third-party integration that may or may not work.

Well done on this one.

Just a heads up though, which may require more testing. The latest Gutenberg release and this plugin do not appear to play well together. I had to disable the Gutenberg plugin, which invalidated the code blocks, and I had to recover each one.

One feature request: Please add a rel attribute so I can display the language.

Thanks again,

Ronald Huereca

This Plugin is Amazing

This plugin is the best syntax highlighting plugin that I have used, thanks for all the hard work in developing it. One recommendation though...

I just stumbled upon the ability to change the color scheme in the Customizer. This is an awesome feature, but not one that is highlighted in the description of the plugin or in the screenshots. Of course it is mentioned in the Advanced Usage wiki, but I have been using the plugin for months and definitely overlooked that 😉. A brief mention in the main description and a screenshot of the different theme options would definitely help unobservant users like myself.

Thanks again!

Awesome plugin

Excelente plugin

Just found this gem of a plugin when looking for code syntax highlighting plugins. No hassle at all to get working, just install and activate and it formats and styles existing code blocks in posts.

Could not be happier with this plugin. Wlldone!

Great plugin with no setup needed

I confess, I've been a happy user of Code Syntax Block for quite a while — a plugin which the author, Weston Router, clearly states that Syntax Highlighting (Code Block) is based upon.

Alas, however, all the pages I had with the older plugin would suffer from an inevitable rendering slowdown — there is so much Javascript on web pages these days that such a slowdown is inevitable, and this is especially true to those scripts that attempt to recognise the language automatically — something that will consume plenty of CPU cycles on the browser. Parsing the language is also no mean feature by itself (I know, I've been doing some experiments for some code editors, and, believe me, it's tough!).

So why force the end-user to bear the burden of all that work? It makes much more sense to pre-render everything on the server, and then let the web server send the already-parsed HTML from its cache. That way, the end-user will already have everything on their browser, no need to wait for parsing!

Also, if you 'forget' to set the language that your code is in (it happens...), the auto-detecting feature will only run on the server, and just once, when you save the post you're writing. Even if it takes a fraction of a second more to save, think of how much time all those users will save when they get the already-rendered page!

So, this plugin is definitely recommended. As a bonus: if you are already using some sort of code block on your WP setup, once you turn off whatever plugin you were using, Syntax Highlighting (Code Block) will immediately pick it up and start its magic (you might need to open and save all the pages you've got code on, though — I'm not quite sure if that's really the case). That means zero effort (beyond saving) — what you already had will continue to work. And, naturally enough, when you disable this plugin, your code block will just revert to the internal WP code block instead — nothing will be 'lost' that way!

If you're still hesitant and reading this to the end... while you wasted your time here, think of how many of your users would have saved their time if you already had this plugin installed :)

It's time to switch to get more performance!

Nice plugin, thank you !

This works nicely.


missed just a download and/or copy button.



also for theme, maybe is best to update "usage instruction"! only after some search I understood can be changed via customized menu.



anyway, looks so good.



ty.


Very good job!


no one wants to conduct a real study to see how many of use hate the code block.


code block is not 100% of wp users bro

Extending the Code block with syntax highlighting rendered on the server, thus being AMP-compatible and having faster frontend performance.

WPygments vs Syntax-highlighting Code Block (with Server-side Rendering)