Each H4 section is converted into a test case by build.rs script. Each section
in spec.clear.md must correspond to the same section in spec.processed.md.
spec.processed.md is a version of this file after one mdsh pass.
spec.processed.md must be idempotent, i.e. any next passes result in the same content.
mdsh --clean pass on spec.processed.md must result in spec.clear.md.
- Producing raw markdown
- Executing shell commands
- Executing command in inline code and producing raw markdown
- Executing command in code blocks with data line and producing raw markdown
- Executing command in code blocks and producing raw markdown
- Executing command in one-line comments and producing raw markdown
- Executing command in multiline comments with data line and producing raw markdown
- Executing command in multiline comments and producing raw markdown
- Executing command in markdown link and producing raw markdown
- Code block with transition producing raw markdown
- Inline code with transition as a comment producing raw markdown
- Reading files contents
- Using inlined values
- Executing shell commands
- Producing code blocks
- Executing shell commands
- Executing command in inline code and producing code block
- Executing command in code blocks with data line and producing code block
- Executing command in code blocks and producing code block
- Executing command in one-line comments and producing code block
- Executing command in multiline comments with data line and producing code block
- Executing command in multiline comments and producing code block
- Executing command in markdown link and producing code block
- Code block with transition producing code block
- Reading files contents
- Using inlined values
- Using inlined data in inline code and producing code block
- Using inlined data in code blocks and producing code block
- Using inlined data in one-line comments and producing code block
- Using inlined data in multiline comments and producing code block
- Using inlined data in markdown link and producing code block
- Executing shell commands
- Sourcing environment variables
- Executing shell commands
- Executing command in inline code and sourcing env variable(s)
- Executing command in code blocks with data line and sourcing env variable(s)
- Executing command in code blocks and sourcing env variable(s)
- Executing command in one-line comments and sourcing env variable(s)
- Executing command in multiline comments with data line and sourcing env variable(s)
- Executing command in multiline comments and sourcing env variable(s)
- Executing command in markdown link and sourcing env variable(s)
- Reading files contents
- Using inlined values
- Executing shell commands
> $ echo 'I am *markdown*'
I am *markdown*echo 'I am *markdown*'echo 'hello world'> $ echo 'hello world'
> < ./samples/example.md
./samples/example.md
> yaml $ echo 'foo: true'
foo: trueecho 'foo: true'echo 'hello world'> yaml < ./samples/example.yml
./samples/example.yml
> yaml foo: true
foo: true! $ echo 'foo=bar'
> $ echo "\`\$foo\` is $foo"
foo=bar> $ echo "\`\$foo\` is $foo"
echo 'foo=bar'> $ echo "\`\$foo\` is $foo"
> $ echo "\`\$foo\` is $foo"
> $ echo "\`\$foo\` is $foo"
> $ echo "\`\$foo\` is $foo"
> $ echo "\`\$foo\` is $foo"
! < ./samples/example.env
> $ echo "\`\$foo\` is $foo"
./samples/example.env
> $ echo "\`\$foo\` is $foo"
> $ echo "\`\$foo\` is $foo"
> $ echo "\`\$foo\` is $foo"
> $ echo "\`\$foo\` is $foo"
! foo=bar
> $ echo "\`\$foo\` is $foo"
foo=bar> $ echo "\`\$foo\` is $foo"
> $ echo "\`\$foo\` is $foo"
> $ echo "\`\$foo\` is $foo"
The end!