1. 1
2. 2
3. 3
4. 4
5. 5
6. 6
7. 7
8. 8
9. 9
10. 10
11. 11
12. 12
13. 13
14. 14
15. 15
16. 16
17. 17
18. 18
19. 19
20. 20
21. 21
22. 22
23. 23
24. 24
25. 25
26. 26
27. 27
28. 28
29. 29
30. 30
31. 31
32. 32
33. 33
34. 34
35. 35
36. 36
37. 37
38. 38
39. 39
40. 40
41. 41
42. 42
43. 43
44. 44
45. 45
46. 46
47. 47
48. 48
49. 49
50. 50
51. 51
52. 52
53. 53
54. 54
55. 55
56. 56
57. 57
58. 58
59. 59
60. 60
61. 61
62. 62
63. 63
64. 64
65. 65
66. 66
67. 67
68. 68
69. 69
70. 70
71. 71
72. 72
73. 73
74. 74
75. 75
76. 76
77. 77
78. 78
79. 79
80. 80

Highlight extension in Obsidian is so buggy... it changes between editing view and reading view.
So Macana does not strictly following the implementation: rather follow the same rule to GFM's strikethrough extension.

Many of these cases are **intentionally** excluded from unit tests, as there is no "correct" behavior.

## Basics

```markdown
==Hello, World!==
```

==Hello, World!==

## Escapes

```markdown
\==foo==
==bar\==baz
=====\=========
```

\==foo==
==bar\==baz
=====\=========

## Edge cases

### Avoid conflict with header usage (CommonMark)

```markdown
=====
```

=====

### Whitespaces

Whitespace right after the start `==` prevents the section from being highlighted.

```markdown
- == Not highlighted ==
- == Me too==
- ==I'm not highlighted in reading view      ==
```

- == Not highlighted ==
- == Me too==
- ==I'm not highlighted in reading view      ==

### No closing tags

It seems closing tag is optional. Ends at block end.

```markdown
==This is highlighted,
and this line too.

but this is not.
```

==This is highlighted,
and this line too.

but this is not.

### More than two symbols

```markdown
==========This is highlighted and 1+1=2 this too, ========but this isn't.
```

==========This is highlighted and 1+1=2 this too, ========but this isn't.

### Nested markers

```markdown
==Foo==Bar==Baz==
```

==Foo==Bar==Baz==