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
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
# Strikethrough
~~This text should be parsed as _strikethroughed_.~~
~~There may be __bold__ or _italic_ text inside strikethroughed text.~~
~~There may be a keyboard shortcut like <kbd>Enter</kbd> inside strikethroughed text.~~
__There may be ~~strikethroughed text~~ inside bold text.__
_There may be ~~strikethroughed text~~ inside italic text._
~~ If there is a space in the beginning or end, it won't work as per the [GFM][GFM] docs ~~
~~Strikethrough can be applied to
multiple lines. Just keep in mind
not to put any space in the beginning or end.~~
# Underscore In Words
The word `complicated` must be neither bold nor italic below:
perform_complicated_task
perform__complicated__task
But the first part below is italic and bold respectively:
_perform_complicated_task
__perform__complicated__task
# Keyboard Shortcuts
Keyboard shortcuts below should be highlighted:
---
A keyboard shortcut <kbd>Enter</kbd> can be in paragraph.
* A keyboard shortcut <kbd>Enter</kbd> can be in list.
_A keyboard shortcut <kbd>Enter</kbd> can be in italic._
__A keyboard shortcut <kbd>Enter</kbd> can be in bold.__
~~A keyboard shortcut <kbd>Enter</kbd> can be in deleted text.~~
<p>A keyboard shortcut <kbd>Enter</kbd> can be in HTML.</p>
<div>
A keyboard shortcut <kbd>Enter</kbd> can be in block level tags.
</div>
# Fenced Code Blocks
## In / Near List Items
Below fenced code blocks _should_ be highlighted.
---
* List item
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```
* List item
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```
---
Below are _not_ valid fenced code blocks according to the [GFM docs][GFM]. It says there must be a blank line before the code block. However, GitHub highlights them. So, they _should_ be highlighted.
---
* List item
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```
* List item
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```
## In / Near Paragraphs
Below is _not_ a _fenced_ code block, just a normal code block.
---
Paragraph
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```
---
Below 2 blocks are fenced code blocks. They _should_ be highlighted.
---
Paragraph
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```
Paragraph
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```
---
Below is not any type of code block. It _should not_ be highlighted.
---
Paragraph
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```
[GFM]: https://help.github.com/articles/github-flavored-markdown
|
