2020-07-17 17:50:57 +03:00
|
|
|
|
---
|
|
|
|
|
template: overrides/main.html
|
|
|
|
|
---
|
|
|
|
|
|
2020-07-20 16:18:09 +03:00
|
|
|
|
# Code blocks
|
2020-07-17 17:50:57 +03:00
|
|
|
|
|
|
|
|
|
Code blocks and examples are an essential part of technical project
|
|
|
|
|
documentation. Material for MkDocs provides different ways to set up syntax
|
|
|
|
|
highlighting for code blocks, either during build time using [Pygments][1] or
|
|
|
|
|
during runtime using a JavaScript syntax highlighter.
|
|
|
|
|
|
|
|
|
|
[1]: https://pygments.org
|
|
|
|
|
|
|
|
|
|
## Configuration
|
|
|
|
|
|
|
|
|
|
### Highlight
|
|
|
|
|
|
2020-07-21 14:33:44 +03:00
|
|
|
|
[:octicons-file-code-24: Source][2] · [:octicons-workflow-24: Extension][3] ·
|
|
|
|
|
:octicons-zap-24: Supersedes: [CodeHilite][4]
|
2020-07-17 17:50:57 +03:00
|
|
|
|
|
2020-07-21 14:33:44 +03:00
|
|
|
|
The [Highlight][3] extension, which is part of [Python Markdown Extensions][5],
|
2020-07-17 17:50:57 +03:00
|
|
|
|
integrates with Material for MkDocs and provides several options for
|
|
|
|
|
configuring syntax highlighting of code blocks:
|
|
|
|
|
|
|
|
|
|
`use_pygments`
|
|
|
|
|
|
2020-07-21 17:01:22 +03:00
|
|
|
|
: :octicons-milestone-24: Default: `true` – This option allows to control
|
2020-07-20 16:18:09 +03:00
|
|
|
|
whether highlighting should be carried out during build time by
|
|
|
|
|
[Pygments][1] or runtime with a JavaScript highlighter. Remember to add the
|
2020-07-21 14:33:44 +03:00
|
|
|
|
necessary [additional stylesheets][6] and [JavaScript][7] if you want to
|
2020-07-20 16:18:09 +03:00
|
|
|
|
use the latter:
|
2020-07-17 17:50:57 +03:00
|
|
|
|
|
|
|
|
|
=== "Pygments"
|
|
|
|
|
|
|
|
|
|
``` yaml
|
|
|
|
|
markdown_extensions:
|
|
|
|
|
- pymdownx.highlight:
|
|
|
|
|
use_pygments: true
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
=== "JavaScript"
|
|
|
|
|
|
|
|
|
|
``` yaml
|
|
|
|
|
markdown_extensions:
|
|
|
|
|
- pymdownx.highlight:
|
|
|
|
|
use_pygments: false
|
|
|
|
|
```
|
|
|
|
|
|
2020-07-21 14:33:44 +03:00
|
|
|
|
??? example "Syntax highlighting with Highlight.js"
|
2020-07-17 17:50:57 +03:00
|
|
|
|
|
2020-07-21 14:33:44 +03:00
|
|
|
|
[Highlight.js][8] can be integrated by creating an [additional
|
|
|
|
|
JavaScript][7] file initializing the highlighter and including the
|
|
|
|
|
respective stylesheet and JavaScript from a [CDN][9] serving
|
|
|
|
|
Highlight.js in `mkdocs.yml`:
|
2020-07-17 17:50:57 +03:00
|
|
|
|
|
2020-07-19 23:23:26 +03:00
|
|
|
|
=== "docs/javascripts/extra.js"
|
2020-07-17 17:50:57 +03:00
|
|
|
|
|
2020-07-19 23:23:26 +03:00
|
|
|
|
``` js
|
|
|
|
|
hljs.initHighlighting()
|
|
|
|
|
```
|
2020-07-17 17:50:57 +03:00
|
|
|
|
|
2020-07-19 23:23:26 +03:00
|
|
|
|
=== "mkdocs.yml"
|
|
|
|
|
|
|
|
|
|
``` yaml
|
|
|
|
|
extra_javascript:
|
|
|
|
|
- https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.1.1/highlight.min.js
|
|
|
|
|
- javascripts/extra.js
|
|
|
|
|
extra_css:
|
|
|
|
|
- https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.1.1/styles/default.min.css
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Note that Highlight.js has no affiliation with the Highlight extension.
|
|
|
|
|
|
|
|
|
|
`linenums`
|
|
|
|
|
|
2020-07-21 17:01:22 +03:00
|
|
|
|
: :octicons-milestone-24: Default: `false` – This option will add line numbers
|
2020-07-20 16:18:09 +03:00
|
|
|
|
to _all_ code blocks. If you wish to add line numbers to _some_, but not all
|
2020-07-21 14:33:44 +03:00
|
|
|
|
code blocks, consult the section on [adding line numbers][10] later in this
|
2020-07-20 16:18:09 +03:00
|
|
|
|
document, which also contains some tips on working with line numbers:
|
2020-07-19 23:23:26 +03:00
|
|
|
|
|
|
|
|
|
``` yaml
|
|
|
|
|
markdown_extensions:
|
|
|
|
|
- pymdownx.highlight:
|
|
|
|
|
linenums: true
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
`linenums_style`
|
|
|
|
|
|
2020-07-21 17:01:22 +03:00
|
|
|
|
: :octicons-milestone-24: Default: `table` – The Highlight extension provides
|
2020-07-20 16:18:09 +03:00
|
|
|
|
three ways to add line numbers, all of which are supported by Material for
|
|
|
|
|
MkDocs. While `table` wraps a code block in a table, `inline` and
|
|
|
|
|
`pymdownx.inline` render line numbers as part of the line itself:
|
2020-07-19 23:23:26 +03:00
|
|
|
|
|
|
|
|
|
``` yaml
|
|
|
|
|
markdown_extensions:
|
|
|
|
|
- pymdownx.highlight:
|
|
|
|
|
linenums_style: pymdownx.inline
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Note that `inline` will put line numbers next to the actual code, which
|
|
|
|
|
means that they will be included when selecting text with the cursor or
|
|
|
|
|
copying a code block to the clipboard. Thus, the usage of `table` or
|
|
|
|
|
`pymdownx.inline` is recommended.
|
|
|
|
|
|
|
|
|
|
_Material for MkDocs doesn't provide official support for the other options of
|
|
|
|
|
this extension, so they may be supported but can also yield weird results. Use
|
|
|
|
|
them at your own risk._
|
2020-07-17 17:50:57 +03:00
|
|
|
|
|
|
|
|
|
[2]: https://github.com/squidfunk/mkdocs-material/blob/master/src/assets/stylesheets/extensions/pymdown/_highlight.scss
|
|
|
|
|
[3]: https://facelessuser.github.io/pymdown-extensions/extensions/highlight/
|
2020-07-21 14:33:44 +03:00
|
|
|
|
[4]: https://python-markdown.github.io/extensions/code_hilite/
|
|
|
|
|
[5]: https://facelessuser.github.io/pymdown-extensions/
|
|
|
|
|
[6]: ../customization.md#additional-stylesheets
|
|
|
|
|
[7]: ../customization.md#additional-javascript
|
|
|
|
|
[8]: https://highlightjs.org/
|
|
|
|
|
[9]: https://cdnjs.com/libraries/highlight.js/
|
|
|
|
|
[10]: #adding-line-numbers
|
2020-07-19 23:23:26 +03:00
|
|
|
|
|
|
|
|
|
### InlineHilite
|
|
|
|
|
|
2020-07-21 14:33:44 +03:00
|
|
|
|
[:octicons-file-code-24: Source][2] · [:octicons-workflow-24: Extension][11]
|
2020-07-19 23:23:26 +03:00
|
|
|
|
|
2020-07-21 14:33:44 +03:00
|
|
|
|
The [InlineHilite][11] extension, which is part of [Python Markdown
|
|
|
|
|
Extensions][5] also integrates with Material for MkDocs and adds support for
|
|
|
|
|
__syntax highlighting of inline code blocks__. It's built on top of the
|
2020-07-19 23:23:26 +03:00
|
|
|
|
[Highlight][3] extension and can be enabled from `mkdocs.yml`:
|
|
|
|
|
|
|
|
|
|
``` yaml
|
|
|
|
|
markdown_extensions:
|
|
|
|
|
- pymdownx.inlinehilite
|
|
|
|
|
```
|
|
|
|
|
|
2020-07-21 14:33:44 +03:00
|
|
|
|
See the section on [inline code blocks][12] for usage information.
|
2020-07-19 23:23:26 +03:00
|
|
|
|
|
2020-07-21 14:33:44 +03:00
|
|
|
|
[11]: https://facelessuser.github.io/pymdown-extensions/extensions/inlinehilite/
|
2020-07-22 12:57:41 +03:00
|
|
|
|
[12]: #highlighting-inline-code-blocks
|
2020-07-21 14:33:44 +03:00
|
|
|
|
|
|
|
|
|
### SuperFences
|
|
|
|
|
|
|
|
|
|
[:octicons-file-code-24: Source][13] · [:octicons-workflow-24: Extension][14]
|
|
|
|
|
|
|
|
|
|
The [SuperFences][14] extension, which is also part of [Python Markdown
|
|
|
|
|
Extensions][5], allows for the __nesting of code blocks inside other blocks__,
|
|
|
|
|
and is therefore strongly recommended:
|
|
|
|
|
|
|
|
|
|
``` yaml
|
|
|
|
|
markdown_extensions:
|
|
|
|
|
- pymdownx.superfences
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
[13]: https://github.com/squidfunk/mkdocs-material/blob/master/src/assets/stylesheets/base/_typeset.scss
|
|
|
|
|
[14]: https://facelessuser.github.io/pymdown-extensions/extensions/superfences/
|
2020-07-19 23:23:26 +03:00
|
|
|
|
|
2020-07-22 12:57:41 +03:00
|
|
|
|
### Keys
|
|
|
|
|
|
|
|
|
|
[:octicons-file-code-24: Source][15] · [:octicons-workflow-24: Extension][16]
|
|
|
|
|
|
|
|
|
|
The [Keys][16] extension, which is part of [Python Markdown Extensions][5],
|
|
|
|
|
allows for inserting __keyboard keys__, e.g. ++ctrl+alt+delete++ , and
|
|
|
|
|
can be enabled from `mkdocs.yml`:
|
|
|
|
|
|
|
|
|
|
``` yaml
|
|
|
|
|
markdown_extensions:
|
|
|
|
|
- pymdownx.keys
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
[15]: https://github.com/squidfunk/mkdocs-material/blob/master/src/assets/stylesheets/extensions/pymdown/_keys.scss
|
|
|
|
|
[16]: https://facelessuser.github.io/pymdown-extensions/extensions/keys/
|
|
|
|
|
|
2020-07-19 23:23:26 +03:00
|
|
|
|
## Usage
|
|
|
|
|
|
|
|
|
|
This section discusses how to use different syntax highlighting features with
|
|
|
|
|
[Pygments][1] – the default highlighter – so they don't apply when using
|
2020-07-20 18:40:48 +03:00
|
|
|
|
a JavaScript syntax highlighter.
|
2020-07-19 23:23:26 +03:00
|
|
|
|
|
|
|
|
|
### Specifying the language
|
|
|
|
|
|
|
|
|
|
Code blocks must be enclosed with two separate lines containing three backticks.
|
|
|
|
|
To add code highlighting to those blocks, add the language short name directly
|
2020-07-22 12:57:41 +03:00
|
|
|
|
after the opening block. See the [list of available lexers][17] to find the
|
2020-07-19 23:23:26 +03:00
|
|
|
|
short name for a given language.
|
|
|
|
|
|
|
|
|
|
_Example_:
|
|
|
|
|
|
|
|
|
|
```` markdown
|
|
|
|
|
``` python
|
|
|
|
|
import tensorflow as tf
|
|
|
|
|
```
|
|
|
|
|
````
|
|
|
|
|
|
|
|
|
|
_Result_:
|
|
|
|
|
|
|
|
|
|
``` python
|
|
|
|
|
import tensorflow as tf
|
|
|
|
|
```
|
|
|
|
|
|
2020-07-22 12:57:41 +03:00
|
|
|
|
[17]: https://pygments.org/docs/lexers/
|
2020-07-19 23:23:26 +03:00
|
|
|
|
|
|
|
|
|
### Adding line numbers
|
|
|
|
|
|
|
|
|
|
Line numbers can be added to a code block by using the `linenums="<start>"`
|
|
|
|
|
option directly after the short name, whereas `<start>` represents the starting
|
|
|
|
|
line number. A code block can start from a line number other than `1`, which
|
|
|
|
|
allows splitting large code blocks for readability.
|
|
|
|
|
|
|
|
|
|
_Example_:
|
|
|
|
|
|
|
|
|
|
```` markdown
|
|
|
|
|
``` python linenums="1"
|
|
|
|
|
def bubble_sort(items):
|
|
|
|
|
for i in range(len(items)):
|
|
|
|
|
for j in range(len(items) - 1 - i):
|
|
|
|
|
if items[j] > items[j + 1]:
|
|
|
|
|
items[j], items[j + 1] = items[j + 1], items[j]
|
|
|
|
|
```
|
|
|
|
|
````
|
|
|
|
|
|
|
|
|
|
_Result_:
|
|
|
|
|
|
|
|
|
|
``` python linenums="1"
|
|
|
|
|
def bubble_sort(items):
|
|
|
|
|
for i in range(len(items)):
|
|
|
|
|
for j in range(len(items) - 1 - i):
|
|
|
|
|
if items[j] > items[j + 1]:
|
|
|
|
|
items[j], items[j + 1] = items[j + 1], items[j]
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
### Highlighting specific lines
|
|
|
|
|
|
|
|
|
|
Specific lines can be highlighted by passing the line numbers to the `hl_lines`
|
|
|
|
|
argument placed right after the language short name. Note that line counts start
|
|
|
|
|
at `1`, regardless of the starting line number specified as part of `linenums`.
|
|
|
|
|
|
|
|
|
|
_Example_:
|
|
|
|
|
|
|
|
|
|
```` markdown
|
2020-07-20 18:40:48 +03:00
|
|
|
|
``` python hl_lines="2 3"
|
2020-07-19 23:23:26 +03:00
|
|
|
|
def bubble_sort(items):
|
|
|
|
|
for i in range(len(items)):
|
|
|
|
|
for j in range(len(items) - 1 - i):
|
|
|
|
|
if items[j] > items[j + 1]:
|
|
|
|
|
items[j], items[j + 1] = items[j + 1], items[j]
|
|
|
|
|
```
|
|
|
|
|
````
|
|
|
|
|
|
|
|
|
|
_Result_:
|
|
|
|
|
|
2020-07-20 20:28:13 +03:00
|
|
|
|
``` python hl_lines="2 3"
|
2020-07-19 23:23:26 +03:00
|
|
|
|
def bubble_sort(items):
|
|
|
|
|
for i in range(len(items)):
|
|
|
|
|
for j in range(len(items) - 1 - i):
|
|
|
|
|
if items[j] > items[j + 1]:
|
|
|
|
|
items[j], items[j + 1] = items[j + 1], items[j]
|
|
|
|
|
```
|
|
|
|
|
|
2020-07-22 12:57:41 +03:00
|
|
|
|
### Highlighting inline code blocks
|
2020-07-19 23:23:26 +03:00
|
|
|
|
|
2020-07-22 12:57:41 +03:00
|
|
|
|
When [InlineHilite][18] is enabled, inline code blocks can be highlighted by
|
2020-07-19 23:23:26 +03:00
|
|
|
|
prefixing them with a shebang-like sequence, i.e. `#!`, directly followed by
|
2020-07-22 12:57:41 +03:00
|
|
|
|
the [language short name][17].
|
2020-07-19 23:23:26 +03:00
|
|
|
|
|
|
|
|
|
_Example_:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
The `#!python range()` function is used to generate a sequence of numbers.
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
_Result_:
|
|
|
|
|
|
|
|
|
|
The `#!python range()` function is used to generate a sequence of numbers.
|
|
|
|
|
|
2020-07-22 12:57:41 +03:00
|
|
|
|
[18]: #inlinehilite
|
|
|
|
|
|
|
|
|
|
### Displaying keyboard keys
|
|
|
|
|
|
|
|
|
|
When [Keys][19] is enabled, keyboard keys can be inserted with a simple syntax.
|
|
|
|
|
See the [Python Markdown Extensions][16] documentation for a list of all
|
|
|
|
|
available keys.
|
|
|
|
|
|
|
|
|
|
_Example_:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
++ctrl+alt+del++
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
_Result_:
|
|
|
|
|
|
|
|
|
|
++ctrl+alt+del++
|
|
|
|
|
|
|
|
|
|
[19]: #keys
|