diff --git a/dev/.documenter-siteinfo.json b/dev/.documenter-siteinfo.json index 56731ced..21e3a4bd 100644 --- a/dev/.documenter-siteinfo.json +++ b/dev/.documenter-siteinfo.json @@ -1 +1 @@ -{"documenter":{"julia_version":"1.9.3","generation_timestamp":"2023-11-08T09:29:36","documenter_version":"1.1.2"}} \ No newline at end of file +{"documenter":{"julia_version":"1.10.0","generation_timestamp":"2024-01-03T22:56:14","documenter_version":"1.1.2"}} \ No newline at end of file diff --git a/dev/customprocessing/index.html b/dev/customprocessing/index.html index 6d49b53e..6b6e9987 100644 --- a/dev/customprocessing/index.html +++ b/dev/customprocessing/index.html @@ -26,4 +26,4 @@ end return str end

(of course replace included with your respective files)

Finally, you simply pass this function to e.g. Literate.markdown as

Literate.markdown("examples.jl", "path/to/save/markdown";
-                  name = "markdown_file_name", preprocess = replace_includes)

and you will see that in the final output file (here markdown_file_name.md) the include statements are replaced with the actual code to be included!

This approach is used for generating the examples in the documentation of the TimeseriesPrediction.jl package. The example files, included together in the stexamples.jl file, are processed by literate via this make.jl file to generate the markdown and code cells of the documentation.

+ name = "markdown_file_name", preprocess = replace_includes)

and you will see that in the final output file (here markdown_file_name.md) the include statements are replaced with the actual code to be included!

This approach is used for generating the examples in the documentation of the TimeseriesPrediction.jl package. The example files, included together in the stexamples.jl file, are processed by literate via this make.jl file to generate the markdown and code cells of the documentation.

diff --git a/dev/documenter/index.html b/dev/documenter/index.html index 02300d94..912de063 100644 --- a/dev/documenter/index.html +++ b/dev/documenter/index.html @@ -11,4 +11,4 @@ \int f dx $$
  • Whereas Documenter requires HTML blocks to be escaped
    ```@raw html
 <tag>...</tag>
-```
    the output to a notebook markdown cell will be raw HTML
    <tag>...</tag>

    • Literate.script:

    +```the output to a notebook markdown cell will be raw HTML
    <tag>...</tag>

    Literate.script:

    diff --git a/dev/fileformat/index.html b/dev/fileformat/index.html index 9f4732dc..76d492cc 100644 --- a/dev/fileformat/index.html +++ b/dev/fileformat/index.html @@ -29,4 +29,4 @@ #md # Literate.notebook #md # Literate.script #md # ```

    The lines in the example above would be filtered out in the preprocessing step, unless we are generating a markdown file. When generating a markdown file we would simply remove the leading #md from the lines. Beware that the space after the tag is also removed.

    The #src token can also be placed at the end of a line. This is to make it possible to have code lines exclusive to the source code, and not just comment lines. For example, if the source file is included in the test suite we might want to add a @test at the end without this showing up in the outputs:

    using Test                      #src
-@test result == expected_result #src

    2.3. Default replacements

    The following convenience "macros"/source placeholders are always expanded:

    +@test result == expected_result #src

    2.3. Default replacements

    The following convenience "macros"/source placeholders are always expanded:

    diff --git a/dev/generated/example.ipynb b/dev/generated/example.ipynb index fdf44d37..d4f88cfa 100644 --- a/dev/generated/example.ipynb +++ b/dev/generated/example.ipynb @@ -278,97 +278,97 @@ "\n", "\n", "\n", - " \n", + " \n", " \n", " \n", "\n", - "\n", + "\n", "\n", - " \n", + " \n", " \n", " \n", "\n", - "\n", + "\n", "\n", - " \n", + " \n", " \n", " \n", "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n" + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n" ], "image/svg+xml": [ "\n", "\n", "\n", - " \n", + " \n", " \n", " \n", "\n", - "\n", + "\n", "\n", - " \n", + " \n", " \n", " \n", "\n", - "\n", + "\n", "\n", - " \n", + " \n", " \n", " \n", "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n", - "\n" + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n" ] }, "metadata": {}, @@ -529,11 +529,11 @@ "file_extension": ".jl", "mimetype": "application/julia", "name": "julia", - "version": "1.9.3" + "version": "1.10.0" }, "kernelspec": { - "name": "julia-1.9", - "display_name": "Julia 1.9.3", + "name": "julia-1.10", + "display_name": "Julia 1.10.0", "language": "julia" } }, diff --git a/dev/generated/example/7c0da5d9.svg b/dev/generated/example/4a8ed0d7.svg similarity index 92% rename from dev/generated/example/7c0da5d9.svg rename to dev/generated/example/4a8ed0d7.svg index 140f02b2..60a28d2c 100644 --- a/dev/generated/example/7c0da5d9.svg +++ b/dev/generated/example/4a8ed0d7.svg @@ -1,46 +1,46 @@ - + - + - + - + - + - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/dev/generated/example/index.html b/dev/generated/example/index.html index 4959e76b..38b6e158 100644 --- a/dev/generated/example/index.html +++ b/dev/generated/example/index.html @@ -13,7 +13,7 @@ x = range(0, stop=6π, length=1000) y1 = sin.(x) y2 = cos.(x) -plot(x, [y1, y2])Example block output

    Custom processing

    It is possible to give Literate custom pre- and post-processing functions. For example, here we insert a placeholder value y = 321 in the source, and use a preprocessing function that replaces it with y = 321 in the rendered output.

    x = 123
    123

    In this case the preprocessing function is defined by

    function pre(s::String)
+plot(x, [y1, y2])
    Example block output

    Custom processing

    It is possible to give Literate custom pre- and post-processing functions. For example, here we insert a placeholder value y = 321 in the source, and use a preprocessing function that replaces it with y = 321 in the rendered output.

    x = 123
    123

    In this case the preprocessing function is defined by

    function pre(s::String)
     s = replace(s, "x = 123" => "y = 321")
     return s
-end
    pre (generic function with 1 method)

    Documenter.jl interaction

    In the source file it is possible to use Documenter.jl style references, such as @ref and @id. These will be filtered out in the notebook output. For example, here is a link, but it is only visible as a link if you are reading the markdown output. We can also use equations:

    \[\int_\Omega \nabla v \cdot \nabla u\ \mathrm{d}\Omega = \int_\Omega v f\ \mathrm{d}\Omega\]

    using Documenters math syntax. Documenters syntax is automatically changed to \begin{equation} ... \end{equation} in the notebook output to display correctly.

    This page was generated using Literate.jl.

    +end
    pre (generic function with 1 method)

    Documenter.jl interaction

    In the source file it is possible to use Documenter.jl style references, such as @ref and @id. These will be filtered out in the notebook output. For example, here is a link, but it is only visible as a link if you are reading the markdown output. We can also use equations:

    \[\int_\Omega \nabla v \cdot \nabla u\ \mathrm{d}\Omega = \int_\Omega v f\ \mathrm{d}\Omega\]

    using Documenters math syntax. Documenters syntax is automatically changed to \begin{equation} ... \end{equation} in the notebook output to display correctly.

    This page was generated using Literate.jl.

    diff --git a/dev/generated/name/index.html b/dev/generated/name/index.html index 73f402c7..4c01ba2b 100644 --- a/dev/generated/name/index.html +++ b/dev/generated/name/index.html @@ -1,2 +1,2 @@ -Rational numbers · Literate.jl
    GitHub

    Rational numbers

    In julia rational numbers can be constructed with the // operator. Lets define two rational numbers, x and y:

    x = 1//3
    1//3
    y = 2//5
    2//5

    When adding x and y together we obtain a new rational number:

    z = x + y
    11//15
    +Rational numbers · Literate.jl
    GitHub

    Rational numbers

    In julia rational numbers can be constructed with the // operator. Lets define two rational numbers, x and y:

    x = 1//3
    1//3
    y = 2//5
    2//5

    When adding x and y together we obtain a new rational number:

    z = x + y
    11//15
    diff --git a/dev/generated/notebook.ipynb b/dev/generated/notebook.ipynb index 5590effc..12be45b1 100644 --- a/dev/generated/notebook.ipynb +++ b/dev/generated/notebook.ipynb @@ -87,11 +87,11 @@ "file_extension": ".jl", "mimetype": "application/julia", "name": "julia", - "version": "1.9.3" + "version": "1.10.0" }, "kernelspec": { - "name": "julia-1.9", - "display_name": "Julia 1.9.3", + "name": "julia-1.10", + "display_name": "Julia 1.10.0", "language": "julia" } }, diff --git a/dev/index.html b/dev/index.html index 15a9d5c6..de707a5d 100644 --- a/dev/index.html +++ b/dev/index.html @@ -1,2 +1,2 @@ -1. Introduction · Literate.jl
    GitHub

    1. Introduction

    Welcome to the documentation for Literate – a simplistic package for Literate Programming.

    What?

    Literate is a package that generates markdown pages (for e.g. Documenter.jl), and Jupyter notebooks, from the same source file. There is also an option to "clean" the source from all metadata, and produce a pure Julia script.

    The main design goal is simplicity. It should be simple to use, and the syntax should be simple. In short, all you have to do is to write a commented julia script!

    The public interface consists of three functions, all of which take the same script file as input, but generate different output:

    • Literate.markdown generates a markdown file. Code snippets can be executed and the results included in the output.
    • Literate.notebook generates a notebook. Code snippets can be executed and the results included in the output.
    • Literate.script generates a plain script file scrubbed from all metadata and special syntax.

    Why?

    Examples are (probably) the best way to showcase your awesome package, and examples are often the best way for a new user to learn how to use it. It is therefore important that the documentation of your package contains examples for users to read and study. However, people are different, and we all prefer different ways of trying out a new package. Some people want to RTFM, others want to explore the package interactively in, for example, a notebook, and some people want to study the source code. The aim of Literate is to make it easy to give the user all of these options, while still keeping maintenance to a minimum.

    It is quite common that packages have "example notebooks" to showcase the package. Notebooks are great for showcasing a package, but they are not so great with version control, like git. The reason being that a notebook is a very "rich" format since it contains output and other metadata. Changes to the notebook thus result in large diffs, which makes it harder to review the actual changes.

    It is also common that packages include examples in the documentation, for example by using Documenter.jl @example-blocks. This is also great, but it is not quite as interactive as a notebook, for the users who prefer that.

    Literate tries to solve the problems above by creating the output as a part of the doc build. Literate generates the output based on a single source file which makes it easier to maintain, test, and keep the manual and your example notebooks in sync.

    +1. Introduction · Literate.jl
    GitHub

    1. Introduction

    Welcome to the documentation for Literate – a simplistic package for Literate Programming.

    What?

    Literate is a package that generates markdown pages (for e.g. Documenter.jl), and Jupyter notebooks, from the same source file. There is also an option to "clean" the source from all metadata, and produce a pure Julia script.

    The main design goal is simplicity. It should be simple to use, and the syntax should be simple. In short, all you have to do is to write a commented julia script!

    The public interface consists of three functions, all of which take the same script file as input, but generate different output:

    • Literate.markdown generates a markdown file. Code snippets can be executed and the results included in the output.
    • Literate.notebook generates a notebook. Code snippets can be executed and the results included in the output.
    • Literate.script generates a plain script file scrubbed from all metadata and special syntax.

    Why?

    Examples are (probably) the best way to showcase your awesome package, and examples are often the best way for a new user to learn how to use it. It is therefore important that the documentation of your package contains examples for users to read and study. However, people are different, and we all prefer different ways of trying out a new package. Some people want to RTFM, others want to explore the package interactively in, for example, a notebook, and some people want to study the source code. The aim of Literate is to make it easy to give the user all of these options, while still keeping maintenance to a minimum.

    It is quite common that packages have "example notebooks" to showcase the package. Notebooks are great for showcasing a package, but they are not so great with version control, like git. The reason being that a notebook is a very "rich" format since it contains output and other metadata. Changes to the notebook thus result in large diffs, which makes it harder to review the actual changes.

    It is also common that packages include examples in the documentation, for example by using Documenter.jl @example-blocks. This is also great, but it is not quite as interactive as a notebook, for the users who prefer that.

    Literate tries to solve the problems above by creating the output as a part of the doc build. Literate generates the output based on a single source file which makes it easier to maintain, test, and keep the manual and your example notebooks in sync.

    diff --git a/dev/outputformats/index.html b/dev/outputformats/index.html index 71e06c15..72e73c07 100644 --- a/dev/outputformats/index.html +++ b/dev/outputformats/index.html @@ -42,7 +42,7 @@ ```` ```` 1//3 -````

    In this example the output is just plain text. However, if the resulting value of the code block can be displayed as an image (image/png or image/jpeg), HTML (text/html) or markdown (text/markdown) Literate will include the richest representation of the output.

    Note

    Since Documenter executes and captures results of @example block it is not necessary to use execute=true for markdown output that is meant to be used as input to Documenter.

    See the section about Configuration for more information about how to configure the behavior and resulting output of Literate.markdown.

    Literate.markdown — Function
    Literate.markdown(inputfile, outputdir=pwd(); config::AbstractDict=Dict(), kwargs...)

    Generate a markdown file from inputfile and write the result to the directory outputdir.

    See the manual section on Configuration for documentation of possible configuration with config and other keyword arguments.

    source

    Markdown flavors

    Literate can output markdown in different flavors. The flavor is specified using the flavor keyword argument. The following flavors are currently supported:

    • flavor = Literate.DocumenterFlavor(): this is the default flavor and the output is meant to be used as input to Documenter.jl.
    • flavor = Literate.CommonMarkFlavor(): this outputs markdown that has the flavor of the CommonMark specification.
    • flavor = Literate.FranklinFlavor(): this outputs markdown meant to be used as input to Franklin.jl.

    4.2. Notebook output

    Notebook output is generated by Literate.notebook. The (default) notebook output of the source snippet can be seen here: notebook.ipynb.

    We note that lines starting with # are placed in markdown cells, and the code lines have been placed in code cells. By default the notebook is also executed and output cells populated. The current working directory is set to the specified output directory the notebook is executed.

    See the section about Configuration for how to configure the behavior and resulting output of Literate.notebook.

    Literate.notebook — Function
    Literate.notebook(inputfile, outputdir=pwd(); config::AbstractDict=Dict(), kwargs...)

    Generate a notebook from inputfile and write the result to outputdir.

    See the manual section on Configuration for documentation of possible configuration with config and other keyword arguments.

    source

    Notebook metadata

    Jupyter notebook cells (both code cells and markdown cells) can contain metadata. This is enabled in Literate by the %% token, similar to Jupytext. The format is as follows

    %% optional ignored text [type] {optional metadata JSON}

    Cell metadata can, for example, be used for nbgrader and the reveal.js notebook extension RISE.

    The following would create a 3 slide deck with RISE:

    #nb # %% A slide [markdown] {"slideshow": {"slide_type": "slide"}}
+````

    In this example the output is just plain text. However, if the resulting value of the code block can be displayed as an image (image/png or image/jpeg), HTML (text/html) or markdown (text/markdown) Literate will include the richest representation of the output.

    Note

    Since Documenter executes and captures results of @example block it is not necessary to use execute=true for markdown output that is meant to be used as input to Documenter.

    See the section about Configuration for more information about how to configure the behavior and resulting output of Literate.markdown.

    Literate.markdown — Function
    Literate.markdown(inputfile, outputdir=pwd(); config::AbstractDict=Dict(), kwargs...)

    Generate a markdown file from inputfile and write the result to the directory outputdir.

    See the manual section on Configuration for documentation of possible configuration with config and other keyword arguments.

    source

    Markdown flavors

    Literate can output markdown in different flavors. The flavor is specified using the flavor keyword argument. The following flavors are currently supported:

    • flavor = Literate.DocumenterFlavor(): this is the default flavor and the output is meant to be used as input to Documenter.jl.
    • flavor = Literate.CommonMarkFlavor(): this outputs markdown that has the flavor of the CommonMark specification.
    • flavor = Literate.FranklinFlavor(): this outputs markdown meant to be used as input to Franklin.jl.

    4.2. Notebook output

    Notebook output is generated by Literate.notebook. The (default) notebook output of the source snippet can be seen here: notebook.ipynb.

    We note that lines starting with # are placed in markdown cells, and the code lines have been placed in code cells. By default the notebook is also executed and output cells populated. The current working directory is set to the specified output directory the notebook is executed.

    See the section about Configuration for how to configure the behavior and resulting output of Literate.notebook.

    Literate.notebook — Function
    Literate.notebook(inputfile, outputdir=pwd(); config::AbstractDict=Dict(), kwargs...)

    Generate a notebook from inputfile and write the result to outputdir.

    See the manual section on Configuration for documentation of possible configuration with config and other keyword arguments.

    source

    Notebook metadata

    Jupyter notebook cells (both code cells and markdown cells) can contain metadata. This is enabled in Literate by the %% token, similar to Jupytext. The format is as follows

    %% optional ignored text [type] {optional metadata JSON}

    Cell metadata can, for example, be used for nbgrader and the reveal.js notebook extension RISE.

    The following would create a 3 slide deck with RISE:

    #nb # %% A slide [markdown] {"slideshow": {"slide_type": "slide"}}
 # # Some title
 #
 # We're using `#nb` so the metadata is only included in notebook output
@@ -56,4 +56,4 @@
 
 y = 2//5
 
-z = x + y

    We note that lines starting with # are removed and only the code lines have been kept.

    See the section about Configuration for how to configure the behavior and resulting output of Literate.script.

    Literate.script — Function
    Literate.script(inputfile, outputdir=pwd(); config::AbstractDict=Dict(), kwargs...)

    Generate a plain script file from inputfile and write the result to outputdir.

    See the manual section on Configuration for documentation of possible configuration with config and other keyword arguments.

    source

    4.4. Configuration

    The behavior of Literate.markdown, Literate.notebook and Literate.script can be configured by keyword arguments. There are two ways to do this; pass config::Dict as a keyword argument, or pass individual keyword arguments.

    Configuration precedence

    Individual keyword arguments take precedence over the config dictionary, so for e.g. Literate.markdown(...; config = Dict("name" => "hello"), name = "world") the resulting configuration for name will be "world". Both individual keyword arguments and the config dictionary take precedence over the default.

    Available configurations with description and default values are given in the reference for Literate.DEFAULT_CONFIGURATION just below.

    Literate.DEFAULT_CONFIGURATION — Constant
    DEFAULT_CONFIGURATION

    Default configuration for Literate.markdown, Literate.notebook and Literate.script which is used for everything not specified by the user. Configuration can be passed as individual keyword arguments or as a dictionary passed with the config keyword argument. See the manual section about Configuration for more information.

    Available options:

    • name (default: filename(inputfile)): Name of the output file (excluding the file extension).
    • preprocess (default: identity): Custom preprocessing function mapping a String to a String. See Custom pre- and post-processing.
    • postprocess (default: identity): Custom preprocessing function mapping a String to a String. See Custom pre- and post-processing.
    • credit (default: true): Boolean for controlling the addition of This file was generated with Literate.jl ... to the bottom of the page. If you find Literate.jl useful then feel free to keep this.
    • keep_comments (default: false): When true, keeps markdown lines as comments in the output script. Only applicable for Literate.script.
    • execute (default: true for notebook, false for markdown): Whether to execute and capture the output. Only applicable for Literate.notebook and Literate.markdown.
    • codefence (default: "````@example $(name)" => "````" for DocumenterFlavor() and "````julia" => "````" otherwise): Pair containing opening and closing code fence for wrapping code blocks.
    • flavor (default: Literate.DocumenterFlavor()) Output flavor for markdown, see Markdown flavors. Only applicable for Literate.markdown.
    • devurl (default: "dev"): URL for "in-development" docs, see Documenter docs. Unused if repo_root_url/ nbviewer_root_url/binder_root_url are set.
    • softscope (default: true for Jupyter notebooks, false otherwise): enable/disable "soft" scoping rules when executing, see e.g. https://github.com/JuliaLang/SoftGlobalScope.jl.
    • repo_root_url: URL to the root of the repository. Determined automatically on Travis CI, GitHub Actions and GitLab CI. Used for @__REPO_ROOT_URL__.
    • nbviewer_root_url: URL to the root of the repository as seen on nbviewer. Determined automatically on Travis CI, GitHub Actions and GitLab CI. Used for @__NBVIEWER_ROOT_URL__.
    • binder_root_url: URL to the root of the repository as seen on mybinder. Determined automatically on Travis CI, GitHub Actions and GitLab CI. Used for @__BINDER_ROOT_URL__.
    • image_formats: A vector of (mime, ext) tuples, with the default Tuple{MIME, String}[(MIME type image/svg+xml, ".svg"), (MIME type image/png, ".png"), (MIME type image/jpeg, ".jpeg")]. Results which are showable with a MIME type are saved with the first match, with the corresponding extension.
    source
    +z = x + y

    We note that lines starting with # are removed and only the code lines have been kept.

    See the section about Configuration for how to configure the behavior and resulting output of Literate.script.

    Literate.script — Function
    Literate.script(inputfile, outputdir=pwd(); config::AbstractDict=Dict(), kwargs...)

    Generate a plain script file from inputfile and write the result to outputdir.

    See the manual section on Configuration for documentation of possible configuration with config and other keyword arguments.

    source

    4.4. Configuration

    The behavior of Literate.markdown, Literate.notebook and Literate.script can be configured by keyword arguments. There are two ways to do this; pass config::Dict as a keyword argument, or pass individual keyword arguments.

    Configuration precedence

    Individual keyword arguments take precedence over the config dictionary, so for e.g. Literate.markdown(...; config = Dict("name" => "hello"), name = "world") the resulting configuration for name will be "world". Both individual keyword arguments and the config dictionary take precedence over the default.

    Available configurations with description and default values are given in the reference for Literate.DEFAULT_CONFIGURATION just below.

    Literate.DEFAULT_CONFIGURATION — Constant
    DEFAULT_CONFIGURATION

    Default configuration for Literate.markdown, Literate.notebook and Literate.script which is used for everything not specified by the user. Configuration can be passed as individual keyword arguments or as a dictionary passed with the config keyword argument. See the manual section about Configuration for more information.

    Available options:

    • name (default: filename(inputfile)): Name of the output file (excluding the file extension).
    • preprocess (default: identity): Custom preprocessing function mapping a String to a String. See Custom pre- and post-processing.
    • postprocess (default: identity): Custom preprocessing function mapping a String to a String. See Custom pre- and post-processing.
    • credit (default: true): Boolean for controlling the addition of This file was generated with Literate.jl ... to the bottom of the page. If you find Literate.jl useful then feel free to keep this.
    • keep_comments (default: false): When true, keeps markdown lines as comments in the output script. Only applicable for Literate.script.
    • execute (default: true for notebook, false for markdown): Whether to execute and capture the output. Only applicable for Literate.notebook and Literate.markdown.
    • codefence (default: "````@example $(name)" => "````" for DocumenterFlavor() and "````julia" => "````" otherwise): Pair containing opening and closing code fence for wrapping code blocks.
    • flavor (default: Literate.DocumenterFlavor()) Output flavor for markdown, see Markdown flavors. Only applicable for Literate.markdown.
    • devurl (default: "dev"): URL for "in-development" docs, see Documenter docs. Unused if repo_root_url/ nbviewer_root_url/binder_root_url are set.
    • softscope (default: true for Jupyter notebooks, false otherwise): enable/disable "soft" scoping rules when executing, see e.g. https://github.com/JuliaLang/SoftGlobalScope.jl.
    • repo_root_url: URL to the root of the repository. Determined automatically on Travis CI, GitHub Actions and GitLab CI. Used for @__REPO_ROOT_URL__.
    • nbviewer_root_url: URL to the root of the repository as seen on nbviewer. Determined automatically on Travis CI, GitHub Actions and GitLab CI. Used for @__NBVIEWER_ROOT_URL__.
    • binder_root_url: URL to the root of the repository as seen on mybinder. Determined automatically on Travis CI, GitHub Actions and GitLab CI. Used for @__BINDER_ROOT_URL__.
    • image_formats: A vector of (mime, ext) tuples, with the default Tuple{MIME, String}[(MIME type image/svg+xml, ".svg"), (MIME type image/png, ".png"), (MIME type image/jpeg, ".jpeg")]. Results which are showable with a MIME type are saved with the first match, with the corresponding extension.
    source
    diff --git a/dev/pipeline/index.html b/dev/pipeline/index.html index 45a0e24e..3f54f8fd 100644 --- a/dev/pipeline/index.html +++ b/dev/pipeline/index.html @@ -29,4 +29,4 @@ y = 2 // 5

    Chunk #3:

    When adding `x` and `y` together we obtain a new rational number:

    Chunk #4:

    z = x + y

    It is then up to the Document generation step to decide how these chunks should be treated.

    Custom control over chunk splits

    Sometimes it is convenient to be able to manually control how the chunks are split. For example, if you want to split a block of code into two, such that they end up in two different @example blocks or notebook cells. The #- token can be used for this purpose. All lines starting with #- are used as "chunk-splitters":

    x = 1 // 3
 y = 2 // 5
 #-
-z = x + y

    The example above would result in two consecutive code-chunks.

    Tip

    The rest of the line, after #-, is discarded, so it is possible to use e.g. #------------- as a chunk splitter, which may make the source code more readable.

    It is also possible to use #+ as a chunk splitter. The difference between #+ and #- is that #+ enables Documenter's "continued"-blocks, see the Documenter manual.

    3.3. Document generation

    After the parsing it is time to generate the output. What is done in this step is very different depending on the output target, and it is described in more detail in the Output format sections: Markdown output, Notebook output and Script output. Using the default settings, the following is happening:

    • Markdown output: markdown chunks are printed as-is, code chunks are put inside a code fence (defaults to @example-blocks),
    • Notebook output: markdown chunks are printed in markdown cells, code chunks are put in code cells,
    • Script output: markdown chunks are discarded, code chunks are printed as-is.

    3.4. Post-processing

    When the document is generated the user, again, has the option to hook-into the generation with a custom post-processing function. The reason is that one might want to change things that are only visible in the rendered document. See Custom pre- and post-processing.

    3.5. Writing to file

    The last step of the generation is writing to file. The result is written to $(outputdir)/$(name)(.md|.ipynb|.jl) where outputdir is the output directory supplied by the user (for example docs/generated), and name is a user supplied filename. It is recommended to add the output directory to .gitignore since the idea is that the generated documents will be generated as part of the build process rather than being files in the repo.

    +z = x + y

    The example above would result in two consecutive code-chunks.

    Tip

    The rest of the line, after #-, is discarded, so it is possible to use e.g. #------------- as a chunk splitter, which may make the source code more readable.

    It is also possible to use #+ as a chunk splitter. The difference between #+ and #- is that #+ enables Documenter's "continued"-blocks, see the Documenter manual.

    3.3. Document generation

    After the parsing it is time to generate the output. What is done in this step is very different depending on the output target, and it is described in more detail in the Output format sections: Markdown output, Notebook output and Script output. Using the default settings, the following is happening:

    • Markdown output: markdown chunks are printed as-is, code chunks are put inside a code fence (defaults to @example-blocks),
    • Notebook output: markdown chunks are printed in markdown cells, code chunks are put in code cells,
    • Script output: markdown chunks are discarded, code chunks are printed as-is.

    3.4. Post-processing

    When the document is generated the user, again, has the option to hook-into the generation with a custom post-processing function. The reason is that one might want to change things that are only visible in the rendered document. See Custom pre- and post-processing.

    3.5. Writing to file

    The last step of the generation is writing to file. The result is written to $(outputdir)/$(name)(.md|.ipynb|.jl) where outputdir is the output directory supplied by the user (for example docs/generated), and name is a user supplied filename. It is recommended to add the output directory to .gitignore since the idea is that the generated documents will be generated as part of the build process rather than being files in the repo.

    diff --git a/dev/reference/index.html b/dev/reference/index.html index 9fa3bee4..e0738b5b 100644 --- a/dev/reference/index.html +++ b/dev/reference/index.html @@ -1,2 +1,2 @@ -Reference · Literate.jl
    GitHub

    Reference

    Literate — Module
    Literate

    Julia package for Literate Programming. See https://fredrikekre.github.io/Literate.jl/ for documentation.

    source
    +Reference · Literate.jl
    GitHub

    Reference

    Literate — Module
    Literate

    Julia package for Literate Programming. See https://fredrikekre.github.io/Literate.jl/ for documentation.

    source
    diff --git a/dev/tips/index.html b/dev/tips/index.html index b812f6ae..f390533d 100644 --- a/dev/tips/index.html +++ b/dev/tips/index.html @@ -27,4 +27,4 @@ This is a useful note.

    and a quotation style formatting in the generated notebook cell:

    > *Note*
 > This is a useful note.

    which, in an actual notebook cell, will look similar to:

    Note
    This is a useful note.

    Debugging code execution

    When Literate is executing code (i.e. when execute = true is set), it does so quietly. All the output gets captured and nothing gets printed into the terminal. This can make it tricky to know where things go wrong, e.g. when the execution stalls due to an infinite loop.

    To help debug this, Literate has an @debug statement that prints out each code block that is being executed. In general, to enable the printing of Literate's @debug statements, you can set the JULIA_DEBUG environment variable to "Literate".

    The easiest way to do that is to set the variable in the Julia session before running Literate by doing

    ENV["JULIA_DEBUG"]="Literate"

    Alternatively, you can also set the environment variable before starting the Julia session, e.g.

    $ JULIA_DEBUG=Literate julia

    or by wrapping the Literate calls in an withenv block

    withenv("JULIA_DEBUG" => "Literate") do
     Literate.notebook("myscript.jl"; execute=true)
-end
    +end