# Listing Extension

The listing extension provides a mechanism for creating source code listings. The system allows for the inclusion of local content as well as complete or partial snippets of the desired source code and includes the ability to parse MOOSE input files and separate out blocks. The main purpose is to avoid copying code or input syntax into the documentation to avoid out-of-date content.

The extension provides the !listing command (see Command Extension), which allows for numbered captions to be applied, the Float Extension provides additional details. The following table list the available configure options for the extension.

KeyDefaultDescription
activeTrueToggle for disabling the extension. This only changes the initial active state, use setActive to control at runtime.
prefixListingThe caption prefix (e.g., Fig.).

The !listing command has the capability to include text from local content and arbitrary files (such as source code). files. There is a wide range of settings that are available to specialize how the code is imported. The complete list of available of settings are provided in Table 2 and the sections below provide various examples of using some of these settings.

## Local Listing Content

It is possible to create a listing using local content. This is done by using the !listing command without any agruments with the desired content following the command, see Command Extension for details to how content is defined. The available settings for this command are given in Table 1.

Example 1: Example listing with content from local markdown.

!listing id=local caption=A function for adding 42. language=cpp
y += 42;
return y;


Listing 1: A function for adding 42.

double add_forty_two(const double y);
y += 42;
return y;

Table 1: Settings available when creating a listing from local content.

KeyDefaultDescription
strip-extra-newlinesTrueRemoves extraneous new lines from the text.
suffixText to include after each line of the included text.
footer-newlines1The number of newlines before the footer.
re-flagsre.M|re.S|re.UPython re flags.
headerNoneText to include prior to the included text.
prefixNoneText to include prior to each line of the included text.
include-endFalseWhen True the texted captured by the 'end' setting is included in the displayed text.
endNoneA portion of text that unique identifies the ending location for including text, if not provided the end of the file is used. By default this line is not included in the display.
lineNoneA portion of text that unique identifies a single line to include.
classThe class settings to be passed to rendered HTML tag.
max-height350pxThe default height for listing content.
styleThe style settings that are passed to rendered HTML tag.
indent0The level of indenting to apply to the included text.
languageNoneThe language to use for highlighting, if not supplied it will be inferred from the extension (if possible).
footerText to include after the included text.
idThe class settings to be passed to the rendered tag.
captionNoneThe caption text for the float object.
include-startTrueWhen False the texted captured by the 'start' setting is excluded in the displayed text.
fix-moose-headerTrueIn C/h files within MOOSE the '//*' is used for the header at the top. This breaks the higlighting, this option removes these and replaces them with '//'.
startNoneA portion of text that unique identifies the starting location for including text, if not provided the beginning of the file is utilized.
reNoneExtract content via a regex, if the 'content' group exists it is used as the desired content, otherwise group 0 is used.

## File Content

You can include complete files from the repository. For example, the following creates the code listing in Example 2.

Table 2: Settings available when capturing text from a file with the listing command.

KeyDefaultDescription
strip-extra-newlinesTrueRemoves extraneous new lines from the text.
suffixText to include after each line of the included text.
footer-newlines1The number of newlines before the footer.
re-flagsre.M|re.S|re.UPython re flags.
headerNoneText to include prior to the included text.
prefixNoneText to include prior to each line of the included text.
include-endFalseWhen True the texted captured by the 'end' setting is included in the displayed text.
endNoneA portion of text that unique identifies the ending location for including text, if not provided the end of the file is used. By default this line is not included in the display.
lineNoneA portion of text that unique identifies a single line to include.
classThe class settings to be passed to rendered HTML tag.
max-height350pxThe default height for listing content.
styleThe style settings that are passed to rendered HTML tag.
indent0The level of indenting to apply to the included text.
languageNoneThe language to use for highlighting, if not supplied it will be inferred from the extension (if possible).
footerText to include after the included text.
idThe class settings to be passed to the rendered tag.
captionNoneThe caption text for the float object.
include-startTrueWhen False the texted captured by the 'start' setting is excluded in the displayed text.
fix-moose-headerTrueIn C/h files within MOOSE the '//*' is used for the header at the top. This breaks the higlighting, this option removes these and replaces them with '//'.
startNoneA portion of text that unique identifies the starting location for including text, if not provided the beginning of the file is utilized.
reNoneExtract content via a regex, if the 'content' group exists it is used as the desired content, otherwise group 0 is used.

Example 2: Example for showing a complete file.

!listing framework/src/kernels/Diffusion.C



#include "Diffusion.h"

registerMooseObject("MooseApp", Diffusion);

template <>
InputParameters
validParams<Diffusion>()
{
InputParameters params = validParams<Kernel>();
params.addClassDescription("The Laplacian operator ($-\\nabla \\cdot \\nabla u$), with the weak "
"form of $(\\nabla \\phi_i, \\nabla u_h)$.");
return params;
}

Diffusion::Diffusion(const InputParameters & parameters) : Kernel(parameters) {}

Real
Diffusion::computeQpResidual()
{
}

Real
Diffusion::computeQpJacobian()
{
}

(framework/src/kernels/Diffusion.C)

### Regular Expression Match

Regular expressions can be utilized to extract specific content from files. Example 3 uses a regular expression to extract the content of a class method.

Example 3: Example listing using the "re" setting.

!listing framework/src/kernels/Diffusion.C
re=Real\sDiffusion::computeQpResidual.*?^}

Real
Diffusion::computeQpResidual()
{
}

(framework/src/kernels/Diffusion.C)

### Single Line Match

It is possible to show a single line of a file by including a snippet that allows the line to be located within the file. If multiple matches occur only the first match will be shown. For example, the call to addClassDescription can be shown by adding the following.

Example 4: Example for displaying a single line from a file.

!listing framework/src/kernels/Diffusion.C line=computeQp

Diffusion::computeQpJacobian()

(framework/src/kernels/Diffusion.C)

### Range Line Match

Code starting and ending on lines containing a string is also possible by using the 'start' and 'end' options. If 'start' is omitted then the snippet will start at the beginning of the file. Similarly, if 'end' is omitted the snippet will include the remainder of the file content.

Example 5: Example listing using the "start" and "end" settings.

!listing moose/test/tests/kernels/simple_diffusion/simple_diffusion.i
start=Kernels
end=Executioner

[Kernels]
[./diff]
type = Diffusion
variable = u
[../]
[]

[BCs]
[./left]
type = DirichletBC
variable = u
boundary = left
value = 0
[../]
[./right]
type = DirichletBC
variable = u
boundary = right
value = 1
[../]
[]

(test/tests/kernels/simple_diffusion/simple_diffusion.i)

## Input File Content

Like for C++ files, MOOSE input files also have additional capability, mainly the "block" setting (see Example 6 for a complete list). Including the block name the included content will be limited to the content matching the supplied name. Notice that the supplied name may be approximate; however, if it is not unique only the first match will appear.

Example 6: Example use of "block" setting for input files.

!listing moose/test/tests/kernels/simple_diffusion/simple_diffusion.i
block=Kernels
id=input
caption=Code listing of [MOOSE] input file block.


Listing 2: Code listing of MOOSE input file block.

[Kernels]
[./diff]
type = Diffusion
variable = u
[../]
[]

(test/tests/kernels/simple_diffusion/simple_diffusion.i)
KeyDefaultDescription
blockNoneSpace separated list of input file block names to include.
strip-extra-newlinesTrueRemoves extraneous new lines from the text.
suffixText to include after each line of the included text.
footer-newlines1The number of newlines before the footer.
re-flagsre.M|re.S|re.UPython re flags.
headerNoneText to include prior to the included text.
prefixNoneText to include prior to each line of the included text.
include-endFalseWhen True the texted captured by the 'end' setting is included in the displayed text.
endNoneA portion of text that unique identifies the ending location for including text, if not provided the end of the file is used. By default this line is not included in the display.
lineNoneA portion of text that unique identifies a single line to include.
classThe class settings to be passed to rendered HTML tag.
max-height350pxThe default height for listing content.
styleThe style settings that are passed to rendered HTML tag.
indent0The level of indenting to apply to the included text.
languageNoneThe language to use for highlighting, if not supplied it will be inferred from the extension (if possible).
footerText to include after the included text.
idThe class settings to be passed to the rendered tag.
captionNoneThe caption text for the float object.
include-startTrueWhen False the texted captured by the 'start' setting is excluded in the displayed text.
fix-moose-headerTrueIn C/h files within MOOSE the '//*' is used for the header at the top. This breaks the higlighting, this option removes these and replaces them with '//'.
startNoneA portion of text that unique identifies the starting location for including text, if not provided the beginning of the file is utilized.
reNoneExtract content via a regex, if the 'content' group exists it is used as the desired content, otherwise group 0 is used.