/usr/share/doc/python-markdown-doc/docs/extensions/code_hilite.txt is in python-markdown-doc 2.6.9-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 | title: CodeHilite Extension
prev_title: Admonition Extension
prev_url: admonition.html
next_title: HeaderId Extension
next_url: header_id.html
CodeHilite
==========
Summary
-------
The CodeHilite extension adds code/syntax highlighting to standard
Python-Markdown code blocks using [Pygments][].
[Pygments]: http://pygments.org/
This extension is included in the standard Markdown library.
Setup
-----
### Step 1: Download and Install Pygments ###
You will also need to [download][dl] and install the Pygments package on your
`PYTHONPATH`. The CodeHilite extension will produce HTML output without
Pygments, but it won't highlight anything (same behavior as setting
`use_pygments` to `False`).
[dl]: http://pygments.org/download/
### Step 2: Add CSS Classes ###
You will need to define the appropriate CSS classes with appropriate rules.
The CSS rules either need to be defined in or linked from the header of your
HTML templates. Pygments can generate CSS rules for you. Just run the following
command from the command line:
pygmentize -S default -f html -a .codehilite > styles.css
If you are using a different `css_class` (default: `codehilite`), then
set the value of the `-a` option to that class name. The CSS rules will be
written to the `styles.css` file which you can copy to your site and link from
your HTML templates.
If you would like to use a different theme, swap out `default` for the desired
theme. For a list of themes installed on your system (additional themes can be
installed via Pygments plugins), run the following command:
pygmentize -L style
!!! see also
GitHub user [richeland] has provided a number of different [CSS style
sheets][rich] which work with Pygments along with a [preview] of each theme.
The `css_class` used is the same as the default value for that option
(`codehilite`). However, the Python-Markdown project makes no guarantee that
richeland's CSS styles will work with the version of Pygments you are using.
To ensure complete compatibility, you should generate the CSS rules from
your own installation of Pygments.
See Pygments' excellent [documentation] for more details. If no language is
defined, Pygments will attempt to guess the language. When that fails, the code
block will not be highlighted.
[richeland]: https://github.com/richleland
[rich]: https://github.com/richleland/pygments-css
[previews]: http://richleland.github.io/pygments-css/
[documentation]: http://pygments.org/docs/
Syntax
------
The CodeHilite extension follows the same [syntax][] as regular Markdown code
blocks, with one exception. The highlighter needs to know what language to use for
the code block. There are three ways to tell the highlighter what language the
code block contains and each one has a different result.
!!! Note
The format of the language identifier only effects the display of line numbers
if `linenums` is set to `None` (the default). If set to `True` or `False`
(see [Usage](#usage) below) the format of the identifier has no effect on the
display of line numbers -- it only serves as a means to define the language
of the code block.
[syntax]: http://daringfireball.net/projects/markdown/syntax#precode
### Shebang (with path) ###
If the first line of the code block contains a shebang, the language is derived
from that and line numbers are used.
#!/usr/bin/python
# Code goes here ...
Will result in:
#!/usr/bin/python
# Code goes here ...
### Shebang (no path) ###
If the first line contains a shebang, but the shebang line does not contain a
path (a single `/` or even a space), then that line is removed from the code
block before processing. Line numbers are used.
#!python
# Code goes here ...
Will result in:
# Code goes here ...
### Colons ###
If the first line begins with three or more colons, the text following the
colons identifies the language. The first line is removed from the code block
before processing and line numbers are not used.
:::python
# Code goes here ...
Will result in:
# Code goes here ...
Certain lines can be selected for emphasis with the colon syntax. When
using Pygments' default CSS styles, emphasized lines have a yellow background.
This is useful to direct the reader's attention to specific lines.
:::python hl_lines="1 3"
# This line is emphasized
# This line isn't
# This line is emphasized
!!! Note
`hl_lines` is named for Pygments' option meaning "highlighted lines".
### When No Language is Defined ###
CodeHilite is completely backwards compatible so that if a code block is
encountered that does not define a language, the block is simply wrapped in
`<pre>` tags and output.
# Code goes here ...
Will result in:
# Code goes here ...
Lets see the source for that:
<div class="codehilite"><pre><code># Code goes here ...
</code></pre></div>
!!! Note
When no language is defined, the Pygments highlighting engine will try to guess
the language (unless `guess_lang` is set to `False`). Upon failure, the same
behavior will happen as described above.
Usage
-----
See [Extensions](index.html) for general extension usage, specify
`markdown.extensions.codehilite` as the name of the extension.
See the [Library Reference](../reference.html#extensions) for information about
configuring extensions.
The following options are provided to configure the output:
* **`linenums`**:
Use line numbers. Possible values are `True` for yes, `False` for no and
`None` for auto. Defaults to `None`.
Using `True` will force every code block to have line numbers, even when
using colons (`:::`) for language identification.
Using `False` will turn off all line numbers, even when using shebangs
(`#!`) for language identification.
* **`guess_lang`**:
Automatic language detection. Defaults to `True`.
Using `False` will prevent Pygments from guessing the language, and thus
highlighting blocks only when you explicitly set the language.
* **`css_class`**:
Set CSS class name for the wrapper `<div>` tag. Defaults to
`codehilite`.
* **`pygments_style`**:
Pygments HTML Formatter Style (`ColorScheme`). Defaults to `default`.
!!! Note
This is useful only when `noclasses` is set to `True`, otherwise the
CSS styles must be provided by the end user.
* **`noclasses`**:
Use inline styles instead of CSS classes. Defaults to `False`.
* **`use_pygments`**:
Defaults to `True`. Set to `False` to disable the use of Pygments.
If a language is defined for a code block, it will be assigned to the
`<code>` tag as a class in the manner suggested by the [HTML5 spec][spec]
(alternate output will not be entertained) and might be used by a JavaScript
library in the browser to highlight the code block.
[spec]: http://www.w3.org/TR/html5/text-level-semantics.html#the-code-element
|