File: example.md

package info (click to toggle)
md2term 0.0.7-2
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, forky, sid, trixie
  • size: 472 kB
  • sloc: sh: 202; makefile: 18
file content (50 lines) | stat: -rw-r--r-- 1,183 bytes parent folder | download
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
# PRESENTATION TITLE

This is a **test** of the `slides` in *markdown*. Here we have **bold** text, \
*italic* text, <u>sublining</u> or ~~cutting~~ text, plus a combination of \
***bold and italic*** and the simulation of a [link](url).


## HERE WE HAVE A SUBTITLE

We also interpret `inline code` and blocks of code:

```
for n in $teste; do
    echo $n
done
```

Code blocks can be used to demonstrate markings:

```
LINK: [label](url)
```

### NOW IT'S A SUB-TITLE!

Cool, isn't it? How about seeing an unordered list?

- The source text will render correctly on any platform \
  that interprets GitHub markdown-compatible markup. Items in lists can be \
  given **styles**! 

- Like **negrite**, *italic*, and <u>sublime</u>.

- Besides the `codes` and the [simulated links](url)!

What about an ordered list?

1. item one
1. item two
1. item three


## LOOK AT THE QUOTE RIGHT THERE!

> **Important:** There are limitations, after all, this parser is intended to \
display highlights and colors on the terminal. The main advantage, however, \
is that the source text will render correctly on any platform that interprets \
GitHub-compliant markdown.

***That's all, folks!***