Period: .
-These should get escaped, even though they're matching pairs for
-other Markdown constructs:
-`
-
-Fix for backticks within HTML tag: like this
-
-Here's how you put `` `backticks` `` in a code span.
-
diff --git a/test/fixtures/remarked_pending/complex_mixture.html b/test/fixtures/remarked_pending/complex_mixture.html
deleted file mode 100644
index 8f78c4d..0000000
--- a/test/fixtures/remarked_pending/complex_mixture.html
+++ /dev/null
@@ -1,4 +0,0 @@
-A heading Just a note, I've found that I can't test my markdown parser vs others. For example, both markdown.js and showdown code blocks in lists wrong. They're also completely inconsistent with regards to paragraphs in list items.
A link. Not anymore.
This will make me fail the test because
-markdown.js doesnt acknowledge arbitrary html blocks =/ Paragraph.
bq Item 1 bq Item 2 New bq Item 1 New bq Item 2 Text here Another blockquote! I really need to get more creative with mockup text.. markdown.js breaks here again
Another Heading Hello world . Here is a link . And an image .
Code goes here.
-Lots of it...
diff --git a/test/fixtures/remarked_pending/complex_mixture.md b/test/fixtures/remarked_pending/complex_mixture.md
deleted file mode 100644
index 58e17a6..0000000
--- a/test/fixtures/remarked_pending/complex_mixture.md
+++ /dev/null
@@ -1,55 +0,0 @@
-[test]: http://google.com/ "Google"
-
-# A heading
-
-Just a note, I've found that I can't test my markdown parser vs others.
-For example, both markdown.js and showdown code blocks in lists wrong. They're
-also completely [inconsistent][test] with regards to paragraphs in list items.
-
-A link. Not anymore.
-
-This will make me fail the test because
-markdown.js doesnt acknowledge arbitrary html blocks =/
-
-* List Item 1
-
-* List Item 2
- * New List Item 1
- Hi, this is a list item.
- * New List Item 2
- Another item
- Code goes here.
- Lots of it...
- * New List Item 3
- The last item
-
-* List Item 3
-The final item.
-
-* List Item 4
-The real final item.
-
-Paragraph.
-
-> * bq Item 1
-> * bq Item 2
-> * New bq Item 1
-> * New bq Item 2
-> Text here
-
-* * *
-
-> Another blockquote!
-> I really need to get
-> more creative with
-> mockup text..
-> markdown.js breaks here again
-
-Another Heading
--------------
-
-Hello *world*. Here is a [link](//hello).
-And an image ![alt](src).
-
- Code goes here.
- Lots of it...
diff --git a/test/fixtures/remarked_pending/def_blocks.html b/test/fixtures/remarked_pending/def_blocks.html
deleted file mode 100644
index ffe6f19..0000000
--- a/test/fixtures/remarked_pending/def_blocks.html
+++ /dev/null
@@ -1,20 +0,0 @@
-
- hello
-[1]: hello
-
-
-
- hello
-
-
-
-
- foo
-bar
-bar
-
diff --git a/test/fixtures/remarked_pending/def_blocks.md b/test/fixtures/remarked_pending/def_blocks.md
deleted file mode 100644
index 4d16292..0000000
--- a/test/fixtures/remarked_pending/def_blocks.md
+++ /dev/null
@@ -1,21 +0,0 @@
-> hello
-> [1]: hello
-
-* * *
-
-> hello
-[2]: hello
-
-
-* hello
-* [3]: hello
-
-
-* hello
-[4]: hello
-
-
-> foo
-> bar
-[1]: foo
-> bar
diff --git a/test/fixtures/remarked_pending/double_link.html b/test/fixtures/remarked_pending/double_link.html
deleted file mode 100644
index 8e2f364..0000000
--- a/test/fixtures/remarked_pending/double_link.html
+++ /dev/null
@@ -1,3 +0,0 @@
-Already linked: http://example.com/ .
-Already linked: http://example.com/ .
-Already linked: http://example.com/ .
diff --git a/test/fixtures/remarked_pending/double_link.md b/test/fixtures/remarked_pending/double_link.md
deleted file mode 100644
index 5021673..0000000
--- a/test/fixtures/remarked_pending/double_link.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Already linked: http://example.com/ .
-
-Already linked: [http://example.com/](http://example.com/).
-
-Already linked: **http://example.com/** .
diff --git a/test/fixtures/remarked_pending/gfm_break.breaks.html b/test/fixtures/remarked_pending/gfm_break.breaks.html
deleted file mode 100644
index 398ba01..0000000
--- a/test/fixtures/remarked_pending/gfm_break.breaks.html
+++ /dev/null
@@ -1 +0,0 @@
-Look at the pretty line breaks.
diff --git a/test/fixtures/remarked_pending/gfm_break.breaks.md b/test/fixtures/remarked_pending/gfm_break.breaks.md
deleted file mode 100644
index 0d5b815..0000000
--- a/test/fixtures/remarked_pending/gfm_break.breaks.md
+++ /dev/null
@@ -1,3 +0,0 @@
-Look at the
-pretty line
-breaks.
diff --git a/test/fixtures/remarked_pending/gfm_code_hr_list.html b/test/fixtures/remarked_pending/gfm_code_hr_list.html
deleted file mode 100644
index 9fbd0fb..0000000
--- a/test/fixtures/remarked_pending/gfm_code_hr_list.html
+++ /dev/null
@@ -1,52 +0,0 @@
-foo
-
-bar:
-
-
-
-
-foo:
- line 1
- line 2
-
-foo:
-
-foo bar
bar:
- some code here
-
-
-foo bar
bar:
- foo
- ---
- bar
- ---
- foo
- bar
-
-foo bar
bar:
- ---
- foo
- foo
- ---
- bar
-
-foo bar
bar:
- foo
- ---
- bar
-
-foo
-
-
-
-
diff --git a/test/fixtures/remarked_pending/gfm_code_hr_list.md b/test/fixtures/remarked_pending/gfm_code_hr_list.md
deleted file mode 100644
index 0eba405..0000000
--- a/test/fixtures/remarked_pending/gfm_code_hr_list.md
+++ /dev/null
@@ -1,53 +0,0 @@
-## foo
-
-1. bar:
-
- > - one
- - two
- - three
- - four
- - five
-
-1. foo:
-
- ```
- line 1
- line 2
- ```
-
-1. foo:
-
- 1. foo `bar` bar:
-
- ``` erb
- some code here
- ```
-
- 2. foo `bar` bar:
-
- ``` erb
- foo
- ---
- bar
- ---
- foo
- bar
- ```
-
- 3. foo `bar` bar:
-
- ``` html
- ---
- foo
- foo
- ---
- bar
- ```
-
- 4. foo `bar` bar:
-
- foo
- ---
- bar
-
- 5. foo
diff --git a/test/fixtures/remarked_pending/gfm_del.html b/test/fixtures/remarked_pending/gfm_del.html
deleted file mode 100644
index 95e9ec7..0000000
--- a/test/fixtures/remarked_pending/gfm_del.html
+++ /dev/null
@@ -1 +0,0 @@
-hello hi world
diff --git a/test/fixtures/remarked_pending/gfm_del.md b/test/fixtures/remarked_pending/gfm_del.md
deleted file mode 100644
index d29ca77..0000000
--- a/test/fixtures/remarked_pending/gfm_del.md
+++ /dev/null
@@ -1 +0,0 @@
-hello ~~hi~~ world
diff --git a/test/fixtures/remarked_pending/gfm_em.html b/test/fixtures/remarked_pending/gfm_em.html
deleted file mode 100644
index 8fac346..0000000
--- a/test/fixtures/remarked_pending/gfm_em.html
+++ /dev/null
@@ -1 +0,0 @@
-These words should_not_be_emphasized.
diff --git a/test/fixtures/remarked_pending/gfm_em.md b/test/fixtures/remarked_pending/gfm_em.md
deleted file mode 100644
index 6319874..0000000
--- a/test/fixtures/remarked_pending/gfm_em.md
+++ /dev/null
@@ -1 +0,0 @@
-These words should_not_be_emphasized.
diff --git a/test/fixtures/remarked_pending/gfm_links.html b/test/fixtures/remarked_pending/gfm_links.html
deleted file mode 100644
index 4f62ae1..0000000
--- a/test/fixtures/remarked_pending/gfm_links.html
+++ /dev/null
@@ -1,2 +0,0 @@
-This should be a link:
-http://example.com/hello-world .
diff --git a/test/fixtures/remarked_pending/gfm_links.md b/test/fixtures/remarked_pending/gfm_links.md
deleted file mode 100644
index c133666..0000000
--- a/test/fixtures/remarked_pending/gfm_links.md
+++ /dev/null
@@ -1 +0,0 @@
-This should be a link: http://example.com/hello-world.
diff --git a/test/fixtures/remarked_pending/gfm_tables.html b/test/fixtures/remarked_pending/gfm_tables.html
deleted file mode 100644
index 70bec82..0000000
--- a/test/fixtures/remarked_pending/gfm_tables.html
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
- Heading 1 Heading 2
-
-
- Cell 1 Cell 2
- Cell 3 Cell 4
-
-
-
-
- Header 1 Header 2 Header 3 Header 4
-
-
- Cell 1 Cell 2 Cell 3 Cell 4
- Cell 5 Cell 6 Cell 7 Cell 8
-
-
-Test code
-
-
- Header 1 Header 2
-
-
- Cell 1 Cell 2
- Cell 3 Cell 4
-
-
-
-
- Header 1 Header 2 Header 3 Header 4
-
-
- Cell 1 Cell 2 Cell 3 Cell 4
- Cell 5 Cell 6 Cell 7 Cell 8
-
-
diff --git a/test/fixtures/remarked_pending/gfm_tables.md b/test/fixtures/remarked_pending/gfm_tables.md
deleted file mode 100644
index 5fd6321..0000000
--- a/test/fixtures/remarked_pending/gfm_tables.md
+++ /dev/null
@@ -1,21 +0,0 @@
-| Heading 1 | Heading 2
-| --------- | ---------
-| Cell 1 | Cell 2
-| Cell 3 | Cell 4
-
-| Header 1 | Header 2 | Header 3 | Header 4 |
-| :------: | -------: | :------- | -------- |
-| Cell 1 | Cell 2 | Cell 3 | Cell 4 |
-| Cell 5 | Cell 6 | Cell 7 | Cell 8 |
-
- Test code
-
-Header 1 | Header 2
--------- | --------
-Cell 1 | Cell 2
-Cell 3 | Cell 4
-
-Header 1|Header 2|Header 3|Header 4
-:-------|:------:|-------:|--------
-Cell 1 |Cell 2 |Cell 3 |Cell 4
-*Cell 5*|Cell 6 |Cell 7 |Cell 8
diff --git a/test/fixtures/remarked_pending/gfm_toplevel_paragraphs.html b/test/fixtures/remarked_pending/gfm_toplevel_paragraphs.html
deleted file mode 100644
index 4cc816b..0000000
--- a/test/fixtures/remarked_pending/gfm_toplevel_paragraphs.html
+++ /dev/null
@@ -1,23 +0,0 @@
-hello world
- how are you
- how are you
-hello world
-how are you
-hello world
-
-hello world
-how are you
-hello world
-how are you
-hello world
-how are you
-hello world
-
-hello world
-how are you
-hello world
-how are you
-hello world
-
-hello
-hello
diff --git a/test/fixtures/remarked_pending/gfm_toplevel_paragraphs.md b/test/fixtures/remarked_pending/gfm_toplevel_paragraphs.md
deleted file mode 100644
index 66366c0..0000000
--- a/test/fixtures/remarked_pending/gfm_toplevel_paragraphs.md
+++ /dev/null
@@ -1,37 +0,0 @@
-hello world
- how are you
- how are you
-
-hello world
-```
-how are you
-```
-
-hello world
-* * *
-
-hello world
-# how are you
-
-hello world
-how are you
-===========
-
-hello world
-> how are you
-
-hello world
-* how are you
-
-hello world
-how are you
-
-hello world
-how are you
-
-hello [world][how]
-[how]: /are/you
-
-hello
-
-hello
diff --git a/test/fixtures/remarked_pending/hard_wrapped_paragraphs_with_list_like_lines.nogfm.html b/test/fixtures/remarked_pending/hard_wrapped_paragraphs_with_list_like_lines.nogfm.html
deleted file mode 100644
index e394772..0000000
--- a/test/fixtures/remarked_pending/hard_wrapped_paragraphs_with_list_like_lines.nogfm.html
+++ /dev/null
@@ -1,7 +0,0 @@
-In Markdown 1.0.0 and earlier. Version
-8. This line turns into a list item.
-Because a hard-wrapped line in the
-middle of a paragraph looked like a
-list item.
-Here's one with a bullet.
-* criminey.
diff --git a/test/fixtures/remarked_pending/hard_wrapped_paragraphs_with_list_like_lines.nogfm.md b/test/fixtures/remarked_pending/hard_wrapped_paragraphs_with_list_like_lines.nogfm.md
deleted file mode 100644
index f8a5b27..0000000
--- a/test/fixtures/remarked_pending/hard_wrapped_paragraphs_with_list_like_lines.nogfm.md
+++ /dev/null
@@ -1,8 +0,0 @@
-In Markdown 1.0.0 and earlier. Version
-8. This line turns into a list item.
-Because a hard-wrapped line in the
-middle of a paragraph looked like a
-list item.
-
-Here's one with a bullet.
-* criminey.
diff --git a/test/fixtures/remarked_pending/hr_list_break.html b/test/fixtures/remarked_pending/hr_list_break.html
deleted file mode 100644
index 94885b2..0000000
--- a/test/fixtures/remarked_pending/hr_list_break.html
+++ /dev/null
@@ -1,8 +0,0 @@
-
-hello
-world
-how
-are
-
-
-you today?
diff --git a/test/fixtures/remarked_pending/hr_list_break.md b/test/fixtures/remarked_pending/hr_list_break.md
deleted file mode 100644
index 036fe47..0000000
--- a/test/fixtures/remarked_pending/hr_list_break.md
+++ /dev/null
@@ -1,6 +0,0 @@
-* hello
-world
-* how
-are
-* * *
-you today?
diff --git a/test/fixtures/remarked_pending/inline_html_advanced.html b/test/fixtures/remarked_pending/inline_html_advanced.html
deleted file mode 100644
index a97c821..0000000
--- a/test/fixtures/remarked_pending/inline_html_advanced.html
+++ /dev/null
@@ -1,12 +0,0 @@
-Simple block on one line:
-foo
-And nested without indentation:
-
diff --git a/test/fixtures/remarked_pending/inline_html_advanced.md b/test/fixtures/remarked_pending/inline_html_advanced.md
deleted file mode 100644
index 86b7206..0000000
--- a/test/fixtures/remarked_pending/inline_html_advanced.md
+++ /dev/null
@@ -1,15 +0,0 @@
-Simple block on one line:
-
-foo
-
-And nested without indentation:
-
-
diff --git a/test/fixtures/remarked_pending/inline_html_comments.html b/test/fixtures/remarked_pending/inline_html_comments.html
deleted file mode 100644
index ebc4818..0000000
--- a/test/fixtures/remarked_pending/inline_html_comments.html
+++ /dev/null
@@ -1,8 +0,0 @@
-Paragraph one.
-
-
-Paragraph two.
-
-The end.
diff --git a/test/fixtures/remarked_pending/inline_html_comments.md b/test/fixtures/remarked_pending/inline_html_comments.md
deleted file mode 100644
index 41d830d..0000000
--- a/test/fixtures/remarked_pending/inline_html_comments.md
+++ /dev/null
@@ -1,13 +0,0 @@
-Paragraph one.
-
-
-
-
-
-Paragraph two.
-
-
-
-The end.
diff --git a/test/fixtures/remarked_pending/inline_html_simple.html b/test/fixtures/remarked_pending/inline_html_simple.html
deleted file mode 100644
index 5157c50..0000000
--- a/test/fixtures/remarked_pending/inline_html_simple.html
+++ /dev/null
@@ -1,45 +0,0 @@
-Here's a simple block:
-
- foo
-
-This should be a code block, though:
-<div>
- foo
-</div>
-
-As should this:
-<div>foo</div>
-
-Now, nested:
-
-This should just be an HTML comment:
-
-Multiline:
-
-Code block:
-<!-- Comment -->
-
-Just plain comment, with trailing spaces on the line:
-
-Code:
-<hr>
-
-Hr's:
-
-
-
-
-
-
-
-
-
diff --git a/test/fixtures/remarked_pending/inline_html_simple.md b/test/fixtures/remarked_pending/inline_html_simple.md
deleted file mode 100644
index df49d7b..0000000
--- a/test/fixtures/remarked_pending/inline_html_simple.md
+++ /dev/null
@@ -1,69 +0,0 @@
-Here's a simple block:
-
-
- foo
-
-
-This should be a code block, though:
-
-
- foo
-
-
-As should this:
-
- foo
-
-Now, nested:
-
-
-
-This should just be an HTML comment:
-
-
-
-Multiline:
-
-
-
-Code block:
-
-
-
-Just plain comment, with trailing spaces on the line:
-
-
-
-Code:
-
-
-
-Hr's:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/test/fixtures/remarked_pending/lazy_blockquotes.html b/test/fixtures/remarked_pending/lazy_blockquotes.html
deleted file mode 100644
index a701d42..0000000
--- a/test/fixtures/remarked_pending/lazy_blockquotes.html
+++ /dev/null
@@ -1,4 +0,0 @@
-
- hi there
-bud
-
diff --git a/test/fixtures/remarked_pending/lazy_blockquotes.md b/test/fixtures/remarked_pending/lazy_blockquotes.md
deleted file mode 100644
index c0e0b15..0000000
--- a/test/fixtures/remarked_pending/lazy_blockquotes.md
+++ /dev/null
@@ -1,2 +0,0 @@
-> hi there
-bud
diff --git a/test/fixtures/remarked_pending/links_case_insensitive_refs.html b/test/fixtures/remarked_pending/links_case_insensitive_refs.html
deleted file mode 100644
index c54388e..0000000
--- a/test/fixtures/remarked_pending/links_case_insensitive_refs.html
+++ /dev/null
@@ -1 +0,0 @@
-hi
diff --git a/test/fixtures/remarked_pending/links_case_insensitive_refs.md b/test/fixtures/remarked_pending/links_case_insensitive_refs.md
deleted file mode 100644
index 598915a..0000000
--- a/test/fixtures/remarked_pending/links_case_insensitive_refs.md
+++ /dev/null
@@ -1,3 +0,0 @@
-[hi]
-
-[HI]: /url
diff --git a/test/fixtures/remarked_pending/links_inline_style.html b/test/fixtures/remarked_pending/links_inline_style.html
deleted file mode 100644
index 1194cc8..0000000
--- a/test/fixtures/remarked_pending/links_inline_style.html
+++ /dev/null
@@ -1,8 +0,0 @@
-Just a URL .
-URL and title .
-URL and title .
-URL and title .
-URL and title .
-URL and title .
-URL and title .
-Empty .
diff --git a/test/fixtures/remarked_pending/links_inline_style.md b/test/fixtures/remarked_pending/links_inline_style.md
deleted file mode 100644
index 8c8eb49..0000000
--- a/test/fixtures/remarked_pending/links_inline_style.md
+++ /dev/null
@@ -1,15 +0,0 @@
-Just a [URL](/url/).
-
-[URL and title](/url/ "title").
-
-[URL and title](/url/ "title preceded by two spaces").
-
-[URL and title](/url/ "title preceded by a tab").
-
-[URL and title](/url/ "title has spaces afterward" ).
-
-[URL and title]( /url/has space ).
-
-[URL and title]( /url/has space/ "url has space and title").
-
-[Empty]().
diff --git a/test/fixtures/remarked_pending/links_literal_quotes_in_titles.html b/test/fixtures/remarked_pending/links_literal_quotes_in_titles.html
deleted file mode 100644
index 62e8641..0000000
--- a/test/fixtures/remarked_pending/links_literal_quotes_in_titles.html
+++ /dev/null
@@ -1,2 +0,0 @@
-Foo bar .
-Foo bar .
diff --git a/test/fixtures/remarked_pending/links_literal_quotes_in_titles.md b/test/fixtures/remarked_pending/links_literal_quotes_in_titles.md
deleted file mode 100644
index 29d0e42..0000000
--- a/test/fixtures/remarked_pending/links_literal_quotes_in_titles.md
+++ /dev/null
@@ -1,7 +0,0 @@
-Foo [bar][].
-
-Foo [bar](/url/ "Title with "quotes" inside").
-
-
- [bar]: /url/ "Title with "quotes" inside"
-
diff --git a/test/fixtures/remarked_pending/links_ref_paren.html b/test/fixtures/remarked_pending/links_ref_paren.html
deleted file mode 100644
index cff6977..0000000
--- a/test/fixtures/remarked_pending/links_ref_paren.html
+++ /dev/null
@@ -1 +0,0 @@
-hi
diff --git a/test/fixtures/remarked_pending/links_ref_paren.md b/test/fixtures/remarked_pending/links_ref_paren.md
deleted file mode 100644
index aa97c91..0000000
--- a/test/fixtures/remarked_pending/links_ref_paren.md
+++ /dev/null
@@ -1,3 +0,0 @@
-[hi]
-
-[hi]: /url (there)
diff --git a/test/fixtures/remarked_pending/links_reference_style.html b/test/fixtures/remarked_pending/links_reference_style.html
deleted file mode 100644
index 4c0e7cb..0000000
--- a/test/fixtures/remarked_pending/links_reference_style.html
+++ /dev/null
@@ -1,28 +0,0 @@
-Foo bar .
-Foo bar .
-Foo bar .
-With embedded [brackets] .
-Indented once .
-Indented twice .
-Indented thrice .
-Indented [four][] times.
-[four]: /url
-
-
-this should work
-So should this .
-And this .
-And this .
-And this .
-But not [that] [].
-Nor [that][].
-Nor [that].
-[Something in brackets like this should work]
-[Same with this .]
-In this case, this points to something else.
-Backslashing should suppress [this] and [this].
-
-Here's one where the link
-breaks across lines.
-Here's another where the link
-breaks across lines, but with a line-ending space.
diff --git a/test/fixtures/remarked_pending/links_reference_style.md b/test/fixtures/remarked_pending/links_reference_style.md
deleted file mode 100644
index 341ec88..0000000
--- a/test/fixtures/remarked_pending/links_reference_style.md
+++ /dev/null
@@ -1,71 +0,0 @@
-Foo [bar] [1].
-
-Foo [bar][1].
-
-Foo [bar]
-[1].
-
-[1]: /url/ "Title"
-
-
-With [embedded [brackets]] [b].
-
-
-Indented [once][].
-
-Indented [twice][].
-
-Indented [thrice][].
-
-Indented [four][] times.
-
- [once]: /url
-
- [twice]: /url
-
- [thrice]: /url
-
- [four]: /url
-
-
-[b]: /url/
-
-* * *
-
-[this] [this] should work
-
-So should [this][this].
-
-And [this] [].
-
-And [this][].
-
-And [this].
-
-But not [that] [].
-
-Nor [that][].
-
-Nor [that].
-
-[Something in brackets like [this][] should work]
-
-[Same with [this].]
-
-In this case, [this](/somethingelse/) points to something else.
-
-Backslashing should suppress \[this] and [this\].
-
-[this]: foo
-
-
-* * *
-
-Here's one where the [link
-breaks] across lines.
-
-Here's another where the [link
-breaks] across lines, but with a line-ending space.
-
-
-[link breaks]: /url/
diff --git a/test/fixtures/remarked_pending/links_shortcut_references.html b/test/fixtures/remarked_pending/links_shortcut_references.html
deleted file mode 100644
index e614a64..0000000
--- a/test/fixtures/remarked_pending/links_shortcut_references.html
+++ /dev/null
@@ -1,6 +0,0 @@
-This is the simple case .
-This one has a line
-break .
-This one has a line
-break with a line-ending space.
-this and the other
diff --git a/test/fixtures/remarked_pending/links_shortcut_references.md b/test/fixtures/remarked_pending/links_shortcut_references.md
deleted file mode 100644
index 8c44c98..0000000
--- a/test/fixtures/remarked_pending/links_shortcut_references.md
+++ /dev/null
@@ -1,20 +0,0 @@
-This is the [simple case].
-
-[simple case]: /simple
-
-
-
-This one has a [line
-break].
-
-This one has a [line
-break] with a line-ending space.
-
-[line break]: /foo
-
-
-[this] [that] and the [other]
-
-[this]: /this
-[that]: /that
-[other]: /other
diff --git a/test/fixtures/remarked_pending/list_item_text.html b/test/fixtures/remarked_pending/list_item_text.html
deleted file mode 100644
index 142df36..0000000
--- a/test/fixtures/remarked_pending/list_item_text.html
+++ /dev/null
@@ -1 +0,0 @@
-
diff --git a/test/fixtures/remarked_pending/list_item_text.md b/test/fixtures/remarked_pending/list_item_text.md
deleted file mode 100644
index a8f81b1..0000000
--- a/test/fixtures/remarked_pending/list_item_text.md
+++ /dev/null
@@ -1,5 +0,0 @@
- * item1
-
- * item2
-
- text
diff --git a/test/fixtures/remarked_pending/loose_lists.html b/test/fixtures/remarked_pending/loose_lists.html
deleted file mode 100644
index 757b1ec..0000000
--- a/test/fixtures/remarked_pending/loose_lists.html
+++ /dev/null
@@ -1,39 +0,0 @@
-
-hello
-world
-how
-are
-you
-
-better behavior:
-
-
-
-
-
-hello
-world
-how
-are
-
-
-hello
-world
-how
-are
-
diff --git a/test/fixtures/remarked_pending/loose_lists.md b/test/fixtures/remarked_pending/loose_lists.md
deleted file mode 100644
index cb360a1..0000000
--- a/test/fixtures/remarked_pending/loose_lists.md
+++ /dev/null
@@ -1,59 +0,0 @@
-* hello
- world
-
- how
- are
-* you
-
-
-
-better behavior:
-
-* hello
- * world
- how
-
- are
- you
-
- * today
-* hi
-
-
-
-* hello
-
-* world
-* hi
-
-
-
-* hello
-* world
-
-* hi
-
-
-
-* hello
-* world
-
- how
-* hi
-
-
-
-* hello
-* world
-* how
-
- are
-
-
-
-* hello
-* world
-
-* how
-
- are
diff --git a/test/fixtures/remarked_pending/markdown_documentation_basics.html b/test/fixtures/remarked_pending/markdown_documentation_basics.html
deleted file mode 100644
index 538f953..0000000
--- a/test/fixtures/remarked_pending/markdown_documentation_basics.html
+++ /dev/null
@@ -1,219 +0,0 @@
-Markdown: Basics
-
-
-This page offers a brief overview of what it's like to use Markdown.
-The syntax page provides complete, detailed documentation for
-every feature, but Markdown should be very easy to pick up simply by
-looking at a few examples of it in action. The examples on this page
-are written in a before/after style, showing example syntax and the
-HTML output produced by Markdown.
-It's also helpful to simply try Markdown out; the Dingus is a
-web application that allows you type your own Markdown-formatted text
-and translate it to XHTML.
-Note: This document is itself written using Markdown; you
-can see the source for it by adding '.text' to the URL .
-
-A paragraph is simply one or more consecutive lines of text, separated
-by one or more blank lines. (A blank line is any line that looks like a
-blank line -- a line containing nothing spaces or tabs is considered
-blank.) Normal paragraphs should not be intended with spaces or tabs.
-Markdown offers two styles of headers: Setext and atx .
-Setext-style headers for <h1>
and <h2>
are created by
-"underlining" with equal signs (=
) and hyphens (-
), respectively.
-To create an atx-style header, you put 1-6 hash marks (#
) at the
-beginning of the line -- the number of hashes equals the resulting
-HTML header level.
-Blockquotes are indicated using email-style '>
' angle brackets.
-Markdown:
-A First Level Header
-====================
-A Second Level Header
----------------------
-Now is the time for all good men to come to
-the aid of their country. This is just a
-regular paragraph.
-The quick brown fox jumped over the lazy
-dog's back.
-### Header 3
-> This is a blockquote.
->
-> This is the second paragraph in the blockquote.
->
-> ## This is an H2 in a blockquote
-
-Output:
-<h1>A First Level Header</h1>
-<h2>A Second Level Header</h2>
-<p>Now is the time for all good men to come to
-the aid of their country. This is just a
-regular paragraph.</p>
-<p>The quick brown fox jumped over the lazy
-dog's back.</p>
-<h3>Header 3</h3>
-<blockquote>
- <p>This is a blockquote.</p>
- <p>This is the second paragraph in the blockquote.</p>
- <h2>This is an H2 in a blockquote</h2>
-</blockquote>
-
-Phrase Emphasis
-Markdown uses asterisks and underscores to indicate spans of emphasis.
-Markdown:
-Some of these words *are emphasized*.
-Some of these words _are emphasized also_.
-Use two asterisks for **strong emphasis**.
-Or, if you prefer, __use two underscores instead__.
-
-Output:
-<p>Some of these words <em>are emphasized</em>.
-Some of these words <em>are emphasized also</em>.</p>
-<p>Use two asterisks for <strong>strong emphasis</strong>.
-Or, if you prefer, <strong>use two underscores instead</strong>.</p>
-
-Lists
-Unordered (bulleted) lists use asterisks, pluses, and hyphens (*
,
-+
, and -
) as list markers. These three markers are
-interchangable; this:
-* Candy.
-* Gum.
-* Booze.
-
-this:
-+ Candy.
-+ Gum.
-+ Booze.
-
-and this:
-- Candy.
-- Gum.
-- Booze.
-
-all produce the same output:
-<ul>
-<li>Candy.</li>
-<li>Gum.</li>
-<li>Booze.</li>
-</ul>
-
-Ordered (numbered) lists use regular numbers, followed by periods, as
-list markers:
-1. Red
-2. Green
-3. Blue
-
-Output:
-<ol>
-<li>Red</li>
-<li>Green</li>
-<li>Blue</li>
-</ol>
-
-If you put blank lines between items, you'll get <p>
tags for the
-list item text. You can create multi-paragraph list items by indenting
-the paragraphs by 4 spaces or 1 tab:
-* A list item.
- With multiple paragraphs.
-* Another item in the list.
-
-Output:
-<ul>
-<li><p>A list item.</p>
-<p>With multiple paragraphs.</p></li>
-<li><p>Another item in the list.</p></li>
-</ul>
-
-Links
-Markdown supports two styles for creating links: inline and
-reference . With both styles, you use square brackets to delimit the
-text you want to turn into a link.
-Inline-style links use parentheses immediately after the link text.
-For example:
-This is an [example link](http://example.com/).
-
-Output:
-<p>This is an <a href="http://example.com/">
-example link</a>.</p>
-
-Optionally, you may include a title attribute in the parentheses:
-This is an [example link](http://example.com/ "With a Title").
-
-Output:
-<p>This is an <a href="http://example.com/" title="With a Title">
-example link</a>.</p>
-
-Reference-style links allow you to refer to your links by names, which
-you define elsewhere in your document:
-I get 10 times more traffic from [Google][1] than from
-[Yahoo][2] or [MSN][3].
-[1]: http://google.com/ "Google"
-[2]: http://search.yahoo.com/ "Yahoo Search"
-[3]: http://search.msn.com/ "MSN Search"
-
-Output:
-<p>I get 10 times more traffic from <a href="http://google.com/"
-title="Google">Google</a> than from <a href="http://search.yahoo.com/"
-title="Yahoo Search">Yahoo</a> or <a href="http://search.msn.com/"
-title="MSN Search">MSN</a>.</p>
-
-The title attribute is optional. Link names may contain letters,
-numbers and spaces, but are not case sensitive:
-I start my morning with a cup of coffee and
-[The New York Times][NY Times].
-[ny times]: http://www.nytimes.com/
-
-Output:
-<p>I start my morning with a cup of coffee and
-<a href="http://www.nytimes.com/">The New York Times</a>.</p>
-
-Images
-Image syntax is very much like link syntax.
-Inline (titles are optional):
-![alt text](/path/to/img.jpg "Title")
-
-Reference-style:
-![alt text][id]
-[id]: /path/to/img.jpg "Title"
-
-Both of the above examples produce the same output:
-<img src="/path/to/img.jpg" alt="alt text" title="Title" />
-
-Code
-In a regular paragraph, you can create code span by wrapping text in
-backtick quotes. Any ampersands (&
) and angle brackets (<
or
->
) will automatically be translated into HTML entities. This makes
-it easy to use Markdown to write about HTML example code:
-I strongly recommend against using any `<blink>` tags.
-I wish SmartyPants used named entities like `—`
-instead of decimal-encoded entites like `—`.
-
-Output:
-<p>I strongly recommend against using any
-<code><blink></code> tags.</p>
-<p>I wish SmartyPants used named entities like
-<code>&mdash;</code> instead of decimal-encoded
-entites like <code>&#8212;</code>.</p>
-
-To specify an entire block of pre-formatted code, indent every line of
-the block by 4 spaces or 1 tab. Just like with code spans, &
, <
,
-and >
characters will be escaped automatically.
-Markdown:
-If you want your page to validate under XHTML 1.0 Strict,
-you've got to put paragraph tags in your blockquotes:
- <blockquote>
- <p>For example.</p>
- </blockquote>
-
-Output:
-<p>If you want your page to validate under XHTML 1.0 Strict,
-you've got to put paragraph tags in your blockquotes:</p>
-<pre><code><blockquote>
- <p>For example.</p>
-</blockquote>
-</code></pre>
-
diff --git a/test/fixtures/remarked_pending/markdown_documentation_basics.md b/test/fixtures/remarked_pending/markdown_documentation_basics.md
deleted file mode 100644
index 522cabc..0000000
--- a/test/fixtures/remarked_pending/markdown_documentation_basics.md
+++ /dev/null
@@ -1,306 +0,0 @@
-Markdown: Basics
-================
-
-
-
-
-Getting the Gist of Markdown's Formatting Syntax
-------------------------------------------------
-
-This page offers a brief overview of what it's like to use Markdown.
-The [syntax page] [s] provides complete, detailed documentation for
-every feature, but Markdown should be very easy to pick up simply by
-looking at a few examples of it in action. The examples on this page
-are written in a before/after style, showing example syntax and the
-HTML output produced by Markdown.
-
-It's also helpful to simply try Markdown out; the [Dingus] [d] is a
-web application that allows you type your own Markdown-formatted text
-and translate it to XHTML.
-
-**Note:** This document is itself written using Markdown; you
-can [see the source for it by adding '.text' to the URL] [src].
-
- [s]: /projects/markdown/syntax "Markdown Syntax"
- [d]: /projects/markdown/dingus "Markdown Dingus"
- [src]: /projects/markdown/basics.text
-
-
-## Paragraphs, Headers, Blockquotes ##
-
-A paragraph is simply one or more consecutive lines of text, separated
-by one or more blank lines. (A blank line is any line that looks like a
-blank line -- a line containing nothing spaces or tabs is considered
-blank.) Normal paragraphs should not be intended with spaces or tabs.
-
-Markdown offers two styles of headers: *Setext* and *atx*.
-Setext-style headers for `` and `` are created by
-"underlining" with equal signs (`=`) and hyphens (`-`), respectively.
-To create an atx-style header, you put 1-6 hash marks (`#`) at the
-beginning of the line -- the number of hashes equals the resulting
-HTML header level.
-
-Blockquotes are indicated using email-style '`>`' angle brackets.
-
-Markdown:
-
- A First Level Header
- ====================
-
- A Second Level Header
- ---------------------
-
- Now is the time for all good men to come to
- the aid of their country. This is just a
- regular paragraph.
-
- The quick brown fox jumped over the lazy
- dog's back.
-
- ### Header 3
-
- > This is a blockquote.
- >
- > This is the second paragraph in the blockquote.
- >
- > ## This is an H2 in a blockquote
-
-
-Output:
-
- A First Level Header
-
- A Second Level Header
-
- Now is the time for all good men to come to
- the aid of their country. This is just a
- regular paragraph.
-
- The quick brown fox jumped over the lazy
- dog's back.
-
- Header 3
-
-
- This is a blockquote.
-
- This is the second paragraph in the blockquote.
-
- This is an H2 in a blockquote
-
-
-
-
-### Phrase Emphasis ###
-
-Markdown uses asterisks and underscores to indicate spans of emphasis.
-
-Markdown:
-
- Some of these words *are emphasized*.
- Some of these words _are emphasized also_.
-
- Use two asterisks for **strong emphasis**.
- Or, if you prefer, __use two underscores instead__.
-
-Output:
-
- Some of these words are emphasized .
- Some of these words are emphasized also .
-
- Use two asterisks for strong emphasis .
- Or, if you prefer, use two underscores instead .
-
-
-
-## Lists ##
-
-Unordered (bulleted) lists use asterisks, pluses, and hyphens (`*`,
-`+`, and `-`) as list markers. These three markers are
-interchangable; this:
-
- * Candy.
- * Gum.
- * Booze.
-
-this:
-
- + Candy.
- + Gum.
- + Booze.
-
-and this:
-
- - Candy.
- - Gum.
- - Booze.
-
-all produce the same output:
-
-
- Candy.
- Gum.
- Booze.
-
-
-Ordered (numbered) lists use regular numbers, followed by periods, as
-list markers:
-
- 1. Red
- 2. Green
- 3. Blue
-
-Output:
-
-
- Red
- Green
- Blue
-
-
-If you put blank lines between items, you'll get `` tags for the
-list item text. You can create multi-paragraph list items by indenting
-the paragraphs by 4 spaces or 1 tab:
-
- * A list item.
-
- With multiple paragraphs.
-
- * Another item in the list.
-
-Output:
-
-
-
-
-
-### Links ###
-
-Markdown supports two styles for creating links: *inline* and
-*reference*. With both styles, you use square brackets to delimit the
-text you want to turn into a link.
-
-Inline-style links use parentheses immediately after the link text.
-For example:
-
- This is an [example link](http://example.com/).
-
-Output:
-
- This is an
- example link .
-
-Optionally, you may include a title attribute in the parentheses:
-
- This is an [example link](http://example.com/ "With a Title").
-
-Output:
-
- This is an
- example link .
-
-Reference-style links allow you to refer to your links by names, which
-you define elsewhere in your document:
-
- I get 10 times more traffic from [Google][1] than from
- [Yahoo][2] or [MSN][3].
-
- [1]: http://google.com/ "Google"
- [2]: http://search.yahoo.com/ "Yahoo Search"
- [3]: http://search.msn.com/ "MSN Search"
-
-Output:
-
- I get 10 times more traffic from Google than from Yahoo or MSN .
-
-The title attribute is optional. Link names may contain letters,
-numbers and spaces, but are *not* case sensitive:
-
- I start my morning with a cup of coffee and
- [The New York Times][NY Times].
-
- [ny times]: http://www.nytimes.com/
-
-Output:
-
- I start my morning with a cup of coffee and
- The New York Times .
-
-
-### Images ###
-
-Image syntax is very much like link syntax.
-
-Inline (titles are optional):
-
- ![alt text](/path/to/img.jpg "Title")
-
-Reference-style:
-
- ![alt text][id]
-
- [id]: /path/to/img.jpg "Title"
-
-Both of the above examples produce the same output:
-
-
-
-
-
-### Code ###
-
-In a regular paragraph, you can create code span by wrapping text in
-backtick quotes. Any ampersands (`&`) and angle brackets (`<` or
-`>`) will automatically be translated into HTML entities. This makes
-it easy to use Markdown to write about HTML example code:
-
- I strongly recommend against using any `` tags.
-
- I wish SmartyPants used named entities like `—`
- instead of decimal-encoded entites like `—`.
-
-Output:
-
- I strongly recommend against using any
- <blink>
tags.
-
- I wish SmartyPants used named entities like
- —
instead of decimal-encoded
- entites like —
.
-
-
-To specify an entire block of pre-formatted code, indent every line of
-the block by 4 spaces or 1 tab. Just like with code spans, `&`, `<`,
-and `>` characters will be escaped automatically.
-
-Markdown:
-
- If you want your page to validate under XHTML 1.0 Strict,
- you've got to put paragraph tags in your blockquotes:
-
-
- For example.
-
-
-Output:
-
- If you want your page to validate under XHTML 1.0 Strict,
- you've got to put paragraph tags in your blockquotes:
-
- <blockquote>
- <p>For example.</p>
- </blockquote>
-
diff --git a/test/fixtures/remarked_pending/markdown_documentation_syntax.html b/test/fixtures/remarked_pending/markdown_documentation_syntax.html
deleted file mode 100644
index 4e840d9..0000000
--- a/test/fixtures/remarked_pending/markdown_documentation_syntax.html
+++ /dev/null
@@ -1,671 +0,0 @@
-Markdown: Syntax
-
-
-Note: This document is itself written using Markdown; you
-can see the source for it by adding '.text' to the URL .
-
-Overview
-Philosophy
-Markdown is intended to be as easy-to-read and easy-to-write as is feasible.
-Readability, however, is emphasized above all else. A Markdown-formatted
-document should be publishable as-is, as plain text, without looking
-like it's been remarked up with tags or formatting instructions. While
-Markdown's syntax has been influenced by several existing text-to-HTML
-filters -- including Setext , atx , Textile , reStructuredText ,
-Grutatext , and EtText -- the single biggest source of
-inspiration for Markdown's syntax is the format of plain text email.
-To this end, Markdown's syntax is comprised entirely of punctuation
-characters, which punctuation characters have been carefully chosen so
-as to look like what they mean. E.g., asterisks around a word actually
-look like *emphasis*. Markdown lists look like, well, lists. Even
-blockquotes look like quoted passages of text, assuming you've ever
-used email.
-Inline HTML
-Markdown's syntax is intended for one purpose: to be used as a
-format for writing for the web.
-Markdown is not a replacement for HTML, or even close to it. Its
-syntax is very small, corresponding only to a very small subset of
-HTML tags. The idea is not to create a syntax that makes it easier
-to insert HTML tags. In my opinion, HTML tags are already easy to
-insert. The idea for Markdown is to make it easy to read, write, and
-edit prose. HTML is a publishing format; Markdown is a writing
-format. Thus, Markdown's formatting syntax only addresses issues that
-can be conveyed in plain text.
-For any markup that is not covered by Markdown's syntax, you simply
-use HTML itself. There's no need to preface it or delimit it to
-indicate that you're switching from Markdown to HTML; you just use
-the tags.
-The only restrictions are that block-level HTML elements -- e.g. <div>
,
-<table>
, <pre>
, <p>
, etc. -- must be separated from surrounding
-content by blank lines, and the start and end tags of the block should
-not be indented with tabs or spaces. Markdown is smart enough not
-to add extra (unwanted) <p>
tags around HTML block-level tags.
-For example, to add an HTML table to a Markdown article:
-This is a regular paragraph.
-<table>
- <tr>
- <td>Foo</td>
- </tr>
-</table>
-This is another regular paragraph.
-
-Note that Markdown formatting syntax is not processed within block-level
-HTML tags. E.g., you can't use Markdown-style *emphasis*
inside an
-HTML block.
-Span-level HTML tags -- e.g. <span>
, <cite>
, or <del>
-- can be
-used anywhere in a Markdown paragraph, list item, or header. If you
-want, you can even use HTML tags instead of Markdown formatting; e.g. if
-you'd prefer to use HTML <a>
or <img>
tags instead of Markdown's
-link or image syntax, go right ahead.
-Unlike block-level HTML tags, Markdown syntax is processed within
-span-level tags.
-Automatic Escaping for Special Characters
-In HTML, there are two characters that demand special treatment: <
-and &
. Left angle brackets are used to start tags; ampersands are
-used to denote HTML entities. If you want to use them as literal
-characters, you must escape them as entities, e.g. <
, and
-&
.
-Ampersands in particular are bedeviling for web writers. If you want to
-write about 'AT&T', you need to write 'AT&T
'. You even need to
-escape ampersands within URLs. Thus, if you want to link to:
-http://images.google.com/images?num=30&q=larry+bird
-
-you need to encode the URL as:
-http://images.google.com/images?num=30&q=larry+bird
-
-in your anchor tag href
attribute. Needless to say, this is easy to
-forget, and is probably the single most common source of HTML validation
-errors in otherwise well-marked-up web sites.
-Markdown allows you to use these characters naturally, taking care of
-all the necessary escaping for you. If you use an ampersand as part of
-an HTML entity, it remains unchanged; otherwise it will be translated
-into &
.
-So, if you want to include a copyright symbol in your article, you can write:
-©
-
-and Markdown will leave it alone. But if you write:
-AT&T
-
-Markdown will translate it to:
-AT&T
-
-Similarly, because Markdown supports inline HTML , if you use
-angle brackets as delimiters for HTML tags, Markdown will treat them as
-such. But if you write:
-4 < 5
-
-Markdown will translate it to:
-4 < 5
-
-However, inside Markdown code spans and blocks, angle brackets and
-ampersands are always encoded automatically. This makes it easy to use
-Markdown to write about HTML code. (As opposed to raw HTML, which is a
-terrible format for writing about HTML syntax, because every single <
-and &
in your example code needs to be escaped.)
-
-Block Elements
-Paragraphs and Line Breaks
-A paragraph is simply one or more consecutive lines of text, separated
-by one or more blank lines. (A blank line is any line that looks like a
-blank line -- a line containing nothing but spaces or tabs is considered
-blank.) Normal paragraphs should not be intended with spaces or tabs.
-The implication of the "one or more consecutive lines of text" rule is
-that Markdown supports "hard-wrapped" text paragraphs. This differs
-significantly from most other text-to-HTML formatters (including Movable
-Type's "Convert Line Breaks" option) which translate every line break
-character in a paragraph into a <br />
tag.
-When you do want to insert a <br />
break tag using Markdown, you
-end a line with two or more spaces, then type return.
-Yes, this takes a tad more effort to create a <br />
, but a simplistic
-"every line break is a <br />
" rule wouldn't work for Markdown.
-Markdown's email-style blockquoting and multi-paragraph list items
-work best -- and look better -- when you format them with hard breaks.
-
-Markdown supports two styles of headers, Setext and atx .
-Setext-style headers are "underlined" using equal signs (for first-level
-headers) and dashes (for second-level headers). For example:
-This is an H1
-=============
-This is an H2
--------------
-
-Any number of underlining =
's or -
's will work.
-Atx-style headers use 1-6 hash characters at the start of the line,
-corresponding to header levels 1-6. For example:
-# This is an H1
-## This is an H2
-###### This is an H6
-
-Optionally, you may "close" atx-style headers. This is purely
-cosmetic -- you can use this if you think it looks better. The
-closing hashes don't even need to match the number of hashes
-used to open the header. (The number of opening hashes
-determines the header level.) :
-# This is an H1 #
-## This is an H2 ##
-### This is an H3 ######
-
-Blockquotes
-Markdown uses email-style >
characters for blockquoting. If you're
-familiar with quoting passages of text in an email message, then you
-know how to create a blockquote in Markdown. It looks best if you hard
-wrap the text and put a >
before every line:
-> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
-> consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
-> Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
->
-> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
-> id sem consectetuer libero luctus adipiscing.
-
-Markdown allows you to be lazy and only put the >
before the first
-line of a hard-wrapped paragraph:
-> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
-consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
-Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
-> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
-id sem consectetuer libero luctus adipiscing.
-
-Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by
-adding additional levels of >
:
-> This is the first level of quoting.
->
-> > This is nested blockquote.
->
-> Back to the first level.
-
-Blockquotes can contain other Markdown elements, including headers, lists,
-and code blocks:
-> ## This is a header.
->
-> 1. This is the first list item.
-> 2. This is the second list item.
->
-> Here's some example code:
->
-> return shell_exec("echo $input | $markdown_script");
-
-Any decent text editor should make email-style quoting easy. For
-example, with BBEdit, you can make a selection and choose Increase
-Quote Level from the Text menu.
-Lists
-Markdown supports ordered (numbered) and unordered (bulleted) lists.
-Unordered lists use asterisks, pluses, and hyphens -- interchangably
--- as list markers:
-* Red
-* Green
-* Blue
-
-is equivalent to:
-+ Red
-+ Green
-+ Blue
-
-and:
-- Red
-- Green
-- Blue
-
-Ordered lists use numbers followed by periods:
-1. Bird
-2. McHale
-3. Parish
-
-It's important to note that the actual numbers you use to mark the
-list have no effect on the HTML output Markdown produces. The HTML
-Markdown produces from the above list is:
-<ol>
-<li>Bird</li>
-<li>McHale</li>
-<li>Parish</li>
-</ol>
-
-If you instead wrote the list in Markdown like this:
-1. Bird
-1. McHale
-1. Parish
-
-or even:
-3. Bird
-1. McHale
-8. Parish
-
-you'd get the exact same HTML output. The point is, if you want to,
-you can use ordinal numbers in your ordered Markdown lists, so that
-the numbers in your source match the numbers in your published HTML.
-But if you want to be lazy, you don't have to.
-If you do use lazy list numbering, however, you should still start the
-list with the number 1. At some point in the future, Markdown may support
-starting ordered lists at an arbitrary number.
-List markers typically start at the left margin, but may be indented by
-up to three spaces. List markers must be followed by one or more spaces
-or a tab.
-To make lists look nice, you can wrap items with hanging indents:
-* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
- Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
- viverra nec, fringilla in, laoreet vitae, risus.
-* Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
- Suspendisse id sem consectetuer libero luctus adipiscing.
-
-But if you want to be lazy, you don't have to:
-* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
-Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
-viverra nec, fringilla in, laoreet vitae, risus.
-* Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
-Suspendisse id sem consectetuer libero luctus adipiscing.
-
-If list items are separated by blank lines, Markdown will wrap the
-items in <p>
tags in the HTML output. For example, this input:
-* Bird
-* Magic
-
-will turn into:
-<ul>
-<li>Bird</li>
-<li>Magic</li>
-</ul>
-
-But this:
-* Bird
-* Magic
-
-will turn into:
-<ul>
-<li><p>Bird</p></li>
-<li><p>Magic</p></li>
-</ul>
-
-List items may consist of multiple paragraphs. Each subsequent
-paragraph in a list item must be intended by either 4 spaces
-or one tab:
-1. This is a list item with two paragraphs. Lorem ipsum dolor
- sit amet, consectetuer adipiscing elit. Aliquam hendrerit
- mi posuere lectus.
- Vestibulum enim wisi, viverra nec, fringilla in, laoreet
- vitae, risus. Donec sit amet nisl. Aliquam semper ipsum
- sit amet velit.
-2. Suspendisse id sem consectetuer libero luctus adipiscing.
-
-It looks nice if you indent every line of the subsequent
-paragraphs, but here again, Markdown will allow you to be
-lazy:
-* This is a list item with two paragraphs.
- This is the second paragraph in the list item. You're
-only required to indent the first line. Lorem ipsum dolor
-sit amet, consectetuer adipiscing elit.
-* Another item in the same list.
-
-To put a blockquote within a list item, the blockquote's >
-delimiters need to be indented:
-* A list item with a blockquote:
- > This is a blockquote
- > inside a list item.
-
-To put a code block within a list item, the code block needs
-to be indented twice -- 8 spaces or two tabs:
-* A list item with a code block:
- <code goes here>
-
-It's worth noting that it's possible to trigger an ordered list by
-accident, by writing something like this:
-1986. What a great season.
-
-In other words, a number-period-space sequence at the beginning of a
-line. To avoid this, you can backslash-escape the period:
-1986\. What a great season.
-
-Code Blocks
-Pre-formatted code blocks are used for writing about programming or
-markup source code. Rather than forming normal paragraphs, the lines
-of a code block are interpreted literally. Markdown wraps a code block
-in both <pre>
and <code>
tags.
-To produce a code block in Markdown, simply indent every line of the
-block by at least 4 spaces or 1 tab. For example, given this input:
-This is a normal paragraph:
- This is a code block.
-
-Markdown will generate:
-<p>This is a normal paragraph:</p>
-<pre><code>This is a code block.
-</code></pre>
-
-One level of indentation -- 4 spaces or 1 tab -- is removed from each
-line of the code block. For example, this:
-Here is an example of AppleScript:
- tell application "Foo"
- beep
- end tell
-
-will turn into:
-<p>Here is an example of AppleScript:</p>
-<pre><code>tell application "Foo"
- beep
-end tell
-</code></pre>
-
-A code block continues until it reaches a line that is not indented
-(or the end of the article).
-Within a code block, ampersands (&
) and angle brackets (<
and >
)
-are automatically converted into HTML entities. This makes it very
-easy to include example HTML source code using Markdown -- just paste
-it and indent it, and Markdown will handle the hassle of encoding the
-ampersands and angle brackets. For example, this:
- <div class="footer">
- © 2004 Foo Corporation
- </div>
-
-will turn into:
-<pre><code><div class="footer">
- &copy; 2004 Foo Corporation
-</div>
-</code></pre>
-
-Regular Markdown syntax is not processed within code blocks. E.g.,
-asterisks are just literal asterisks within a code block. This means
-it's also easy to use Markdown to write about Markdown's own syntax.
-Horizontal Rules
-You can produce a horizontal rule tag (<hr>
) by placing three or
-more hyphens, asterisks, or underscores on a line by themselves. If you
-wish, you may use spaces between the hyphens or asterisks. Each of the
-following lines will produce a horizontal rule:
-* * *
-***
-*****
-- - -
----------------------------------------
-_ _ _
-
-
-Span Elements
-Links
-Markdown supports two style of links: inline and reference .
-In both styles, the link text is delimited by [square brackets].
-To create an inline link, use a set of regular parentheses immediately
-after the link text's closing square bracket. Inside the parentheses,
-put the URL where you want the link to point, along with an optional
-title for the link, surrounded in quotes. For example:
-This is [an example](http://example.com/ "Title") inline link.
-[This link](http://example.net/) has no title attribute.
-
-Will produce:
-<p>This is <a href="http://example.com/" title="Title">
-an example</a> inline link.</p>
-<p><a href="http://example.net/">This link</a> has no
-title attribute.</p>
-
-If you're referring to a local resource on the same server, you can
-use relative paths:
-See my [About](/about/) page for details.
-
-Reference-style links use a second set of square brackets, inside
-which you place a label of your choosing to identify the link:
-This is [an example][id] reference-style link.
-
-You can optionally use a space to separate the sets of brackets:
-This is [an example] [id] reference-style link.
-
-Then, anywhere in the document, you define your link label like this,
-on a line by itself:
-[id]: http://example.com/ "Optional Title Here"
-
-That is:
-
-Square brackets containing the link identifier (optionally
-indented from the left margin using up to three spaces);
-followed by a colon;
-followed by one or more spaces (or tabs);
-followed by the URL for the link;
-optionally followed by a title attribute for the link, enclosed
-in double or single quotes.
-
-The link URL may, optionally, be surrounded by angle brackets:
-[id]: <http://example.com/> "Optional Title Here"
-
-You can put the title attribute on the next line and use extra spaces
-or tabs for padding, which tends to look better with longer URLs:
-[id]: http://example.com/longish/path/to/resource/here
- "Optional Title Here"
-
-Link definitions are only used for creating links during Markdown
-processing, and are stripped from your document in the HTML output.
-Link definition names may constist of letters, numbers, spaces, and punctuation -- but they are not case sensitive. E.g. these two links:
-[link text][a]
-[link text][A]
-
-are equivalent.
-The implicit link name shortcut allows you to omit the name of the
-link, in which case the link text itself is used as the name.
-Just use an empty set of square brackets -- e.g., to link the word
-"Google" to the google.com web site, you could simply write:
-[Google][]
-
-And then define the link:
-[Google]: http://google.com/
-
-Because link names may contain spaces, this shortcut even works for
-multiple words in the link text:
-Visit [Daring Fireball][] for more information.
-
-And then define the link:
-[Daring Fireball]: http://daringfireball.net/
-
-Link definitions can be placed anywhere in your Markdown document. I
-tend to put them immediately after each paragraph in which they're
-used, but if you want, you can put them all at the end of your
-document, sort of like footnotes.
-Here's an example of reference links in action:
-I get 10 times more traffic from [Google] [1] than from
-[Yahoo] [2] or [MSN] [3].
- [1]: http://google.com/ "Google"
- [2]: http://search.yahoo.com/ "Yahoo Search"
- [3]: http://search.msn.com/ "MSN Search"
-
-Using the implicit link name shortcut, you could instead write:
-I get 10 times more traffic from [Google][] than from
-[Yahoo][] or [MSN][].
- [google]: http://google.com/ "Google"
- [yahoo]: http://search.yahoo.com/ "Yahoo Search"
- [msn]: http://search.msn.com/ "MSN Search"
-
-Both of the above examples will produce the following HTML output:
-<p>I get 10 times more traffic from <a href="http://google.com/"
-title="Google">Google</a> than from
-<a href="http://search.yahoo.com/" title="Yahoo Search">Yahoo</a>
-or <a href="http://search.msn.com/" title="MSN Search">MSN</a>.</p>
-
-For comparison, here is the same paragraph written using
-Markdown's inline link style:
-I get 10 times more traffic from [Google](http://google.com/ "Google")
-than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or
-[MSN](http://search.msn.com/ "MSN Search").
-
-The point of reference-style links is not that they're easier to
-write. The point is that with reference-style links, your document
-source is vastly more readable. Compare the above examples: using
-reference-style links, the paragraph itself is only 81 characters
-long; with inline-style links, it's 176 characters; and as raw HTML,
-it's 234 characters. In the raw HTML, there's more markup than there
-is text.
-With Markdown's reference-style links, a source document much more
-closely resembles the final output, as rendered in a browser. By
-allowing you to move the markup-related metadata out of the paragraph,
-you can add links without interrupting the narrative flow of your
-prose.
-Emphasis
-Markdown treats asterisks (*
) and underscores (_
) as indicators of
-emphasis. Text wrapped with one *
or _
will be wrapped with an
-HTML <em>
tag; double *
's or _
's will be wrapped with an HTML
-<strong>
tag. E.g., this input:
-*single asterisks*
-_single underscores_
-**double asterisks**
-__double underscores__
-
-will produce:
-<em>single asterisks</em>
-<em>single underscores</em>
-<strong>double asterisks</strong>
-<strong>double underscores</strong>
-
-You can use whichever style you prefer; the lone restriction is that
-the same character must be used to open and close an emphasis span.
-Emphasis can be used in the middle of a word:
-un*fucking*believable
-
-But if you surround an *
or _
with spaces, it'll be treated as a
-literal asterisk or underscore.
-To produce a literal asterisk or underscore at a position where it
-would otherwise be used as an emphasis delimiter, you can backslash
-escape it:
-\*this text is surrounded by literal asterisks\*
-
-Code
-To indicate a span of code, wrap it with backtick quotes (`
).
-Unlike a pre-formatted code block, a code span indicates code within a
-normal paragraph. For example:
-Use the `printf()` function.
-
-will produce:
-<p>Use the <code>printf()</code> function.</p>
-
-To include a literal backtick character within a code span, you can use
-multiple backticks as the opening and closing delimiters:
-``There is a literal backtick (`) here.``
-
-which will produce this:
-<p><code>There is a literal backtick (`) here.</code></p>
-
-The backtick delimiters surrounding a code span may include spaces --
-one after the opening, one before the closing. This allows you to place
-literal backtick characters at the beginning or end of a code span:
-A single backtick in a code span: `` ` ``
-A backtick-delimited string in a code span: `` `foo` ``
-
-will produce:
-<p>A single backtick in a code span: <code>`</code></p>
-<p>A backtick-delimited string in a code span: <code>`foo`</code></p>
-
-With a code span, ampersands and angle brackets are encoded as HTML
-entities automatically, which makes it easy to include example HTML
-tags. Markdown will turn this:
-Please don't use any `<blink>` tags.
-
-into:
-<p>Please don't use any <code><blink></code> tags.</p>
-
-You can write this:
-`—` is the decimal-encoded equivalent of `—`.
-
-to produce:
-<p><code>&#8212;</code> is the decimal-encoded
-equivalent of <code>&mdash;</code>.</p>
-
-Images
-Admittedly, it's fairly difficult to devise a "natural" syntax for
-placing images into a plain text document format.
-Markdown uses an image syntax that is intended to resemble the syntax
-for links, allowing for two styles: inline and reference .
-Inline image syntax looks like this:
-![Alt text](/path/to/img.jpg)
-![Alt text](/path/to/img.jpg "Optional title")
-
-That is:
-
-An exclamation mark: !
;
-followed by a set of square brackets, containing the alt
-attribute text for the image;
-followed by a set of parentheses, containing the URL or path to
-the image, and an optional title
attribute enclosed in double
-or single quotes.
-
-Reference-style image syntax looks like this:
-![Alt text][id]
-
-Where "id" is the name of a defined image reference. Image references
-are defined using syntax identical to link references:
-[id]: url/to/image "Optional title attribute"
-
-As of this writing, Markdown has no syntax for specifying the
-dimensions of an image; if this is important to you, you can simply
-use regular HTML <img>
tags.
-
-Miscellaneous
-Automatic Links
-Markdown supports a shortcut style for creating "automatic" links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:
-<http://example.com/>
-
-Markdown will turn this into:
-<a href="http://example.com/">http://example.com/</a>
-
-Automatic links for email addresses work similarly, except that
-Markdown will also perform a bit of randomized decimal and hex
-entity-encoding to help obscure your address from address-harvesting
-spambots. For example, Markdown will turn this:
-<address@example.com>
-
-into something like this:
-<a href="mailto:addre
-ss@example.co
-m">address@exa
-mple.com</a>
-
-which will render in a browser as a clickable link to "address@example.com".
-(This sort of entity-encoding trick will indeed fool many, if not
-most, address-harvesting bots, but it definitely won't fool all of
-them. It's better than nothing, but an address published in this way
-will probably eventually start receiving spam.)
-Backslash Escapes
-Markdown allows you to use backslash escapes to generate literal
-characters which would otherwise have special meaning in Markdown's
-formatting syntax. For example, if you wanted to surround a word with
-literal asterisks (instead of an HTML <em>
tag), you can backslashes
-before the asterisks, like this:
-\*literal asterisks\*
-
-Markdown provides backslash escapes for the following characters:
-\ backslash
-` backtick
-* asterisk
-_ underscore
-{} curly braces
-[] square brackets
-() parentheses
-# hash mark
-+ plus sign
-- minus sign (hyphen)
-. dot
-! exclamation mark
-
diff --git a/test/fixtures/remarked_pending/markdown_documentation_syntax.md b/test/fixtures/remarked_pending/markdown_documentation_syntax.md
deleted file mode 100644
index ce6c45f..0000000
--- a/test/fixtures/remarked_pending/markdown_documentation_syntax.md
+++ /dev/null
@@ -1,888 +0,0 @@
-Markdown: Syntax
-================
-
-
-
-
-* [Overview](#overview)
- * [Philosophy](#philosophy)
- * [Inline HTML](#html)
- * [Automatic Escaping for Special Characters](#autoescape)
-* [Block Elements](#block)
- * [Paragraphs and Line Breaks](#p)
- * [Headers](#header)
- * [Blockquotes](#blockquote)
- * [Lists](#list)
- * [Code Blocks](#precode)
- * [Horizontal Rules](#hr)
-* [Span Elements](#span)
- * [Links](#link)
- * [Emphasis](#em)
- * [Code](#code)
- * [Images](#img)
-* [Miscellaneous](#misc)
- * [Backslash Escapes](#backslash)
- * [Automatic Links](#autolink)
-
-
-**Note:** This document is itself written using Markdown; you
-can [see the source for it by adding '.text' to the URL][src].
-
- [src]: /projects/markdown/syntax.text
-
-* * *
-
-Overview
-
-Philosophy
-
-Markdown is intended to be as easy-to-read and easy-to-write as is feasible.
-
-Readability, however, is emphasized above all else. A Markdown-formatted
-document should be publishable as-is, as plain text, without looking
-like it's been remarked up with tags or formatting instructions. While
-Markdown's syntax has been influenced by several existing text-to-HTML
-filters -- including [Setext] [1], [atx] [2], [Textile] [3], [reStructuredText] [4],
-[Grutatext] [5], and [EtText] [6] -- the single biggest source of
-inspiration for Markdown's syntax is the format of plain text email.
-
- [1]: http://docutils.sourceforge.net/mirror/setext.html
- [2]: http://www.aaronsw.com/2002/atx/
- [3]: http://textism.com/tools/textile/
- [4]: http://docutils.sourceforge.net/rst.html
- [5]: http://www.triptico.com/software/grutatxt.html
- [6]: http://ettext.taint.org/doc/
-
-To this end, Markdown's syntax is comprised entirely of punctuation
-characters, which punctuation characters have been carefully chosen so
-as to look like what they mean. E.g., asterisks around a word actually
-look like \*emphasis\*. Markdown lists look like, well, lists. Even
-blockquotes look like quoted passages of text, assuming you've ever
-used email.
-
-
-
-Inline HTML
-
-Markdown's syntax is intended for one purpose: to be used as a
-format for *writing* for the web.
-
-Markdown is not a replacement for HTML, or even close to it. Its
-syntax is very small, corresponding only to a very small subset of
-HTML tags. The idea is *not* to create a syntax that makes it easier
-to insert HTML tags. In my opinion, HTML tags are already easy to
-insert. The idea for Markdown is to make it easy to read, write, and
-edit prose. HTML is a *publishing* format; Markdown is a *writing*
-format. Thus, Markdown's formatting syntax only addresses issues that
-can be conveyed in plain text.
-
-For any markup that is not covered by Markdown's syntax, you simply
-use HTML itself. There's no need to preface it or delimit it to
-indicate that you're switching from Markdown to HTML; you just use
-the tags.
-
-The only restrictions are that block-level HTML elements -- e.g. ``,
-`
`, ``, ``, etc. -- must be separated from surrounding
-content by blank lines, and the start and end tags of the block should
-not be indented with tabs or spaces. Markdown is smart enough not
-to add extra (unwanted) `
` tags around HTML block-level tags.
-
-For example, to add an HTML table to a Markdown article:
-
- This is a regular paragraph.
-
-
-
- This is another regular paragraph.
-
-Note that Markdown formatting syntax is not processed within block-level
-HTML tags. E.g., you can't use Markdown-style `*emphasis*` inside an
-HTML block.
-
-Span-level HTML tags -- e.g. ``, ``, or `` -- can be
-used anywhere in a Markdown paragraph, list item, or header. If you
-want, you can even use HTML tags instead of Markdown formatting; e.g. if
-you'd prefer to use HTML `` or ` ` tags instead of Markdown's
-link or image syntax, go right ahead.
-
-Unlike block-level HTML tags, Markdown syntax *is* processed within
-span-level tags.
-
-
-Automatic Escaping for Special Characters
-
-In HTML, there are two characters that demand special treatment: `<`
-and `&`. Left angle brackets are used to start tags; ampersands are
-used to denote HTML entities. If you want to use them as literal
-characters, you must escape them as entities, e.g. `<`, and
-`&`.
-
-Ampersands in particular are bedeviling for web writers. If you want to
-write about 'AT&T', you need to write '`AT&T`'. You even need to
-escape ampersands within URLs. Thus, if you want to link to:
-
- http://images.google.com/images?num=30&q=larry+bird
-
-you need to encode the URL as:
-
- http://images.google.com/images?num=30&q=larry+bird
-
-in your anchor tag `href` attribute. Needless to say, this is easy to
-forget, and is probably the single most common source of HTML validation
-errors in otherwise well-marked-up web sites.
-
-Markdown allows you to use these characters naturally, taking care of
-all the necessary escaping for you. If you use an ampersand as part of
-an HTML entity, it remains unchanged; otherwise it will be translated
-into `&`.
-
-So, if you want to include a copyright symbol in your article, you can write:
-
- ©
-
-and Markdown will leave it alone. But if you write:
-
- AT&T
-
-Markdown will translate it to:
-
- AT&T
-
-Similarly, because Markdown supports [inline HTML](#html), if you use
-angle brackets as delimiters for HTML tags, Markdown will treat them as
-such. But if you write:
-
- 4 < 5
-
-Markdown will translate it to:
-
- 4 < 5
-
-However, inside Markdown code spans and blocks, angle brackets and
-ampersands are *always* encoded automatically. This makes it easy to use
-Markdown to write about HTML code. (As opposed to raw HTML, which is a
-terrible format for writing about HTML syntax, because every single `<`
-and `&` in your example code needs to be escaped.)
-
-
-* * *
-
-
-Block Elements
-
-
-Paragraphs and Line Breaks
-
-A paragraph is simply one or more consecutive lines of text, separated
-by one or more blank lines. (A blank line is any line that looks like a
-blank line -- a line containing nothing but spaces or tabs is considered
-blank.) Normal paragraphs should not be intended with spaces or tabs.
-
-The implication of the "one or more consecutive lines of text" rule is
-that Markdown supports "hard-wrapped" text paragraphs. This differs
-significantly from most other text-to-HTML formatters (including Movable
-Type's "Convert Line Breaks" option) which translate every line break
-character in a paragraph into a ` ` tag.
-
-When you *do* want to insert a ` ` break tag using Markdown, you
-end a line with two or more spaces, then type return.
-
-Yes, this takes a tad more effort to create a ` `, but a simplistic
-"every line break is a ` `" rule wouldn't work for Markdown.
-Markdown's email-style [blockquoting][bq] and multi-paragraph [list items][l]
-work best -- and look better -- when you format them with hard breaks.
-
- [bq]: #blockquote
- [l]: #list
-
-
-
-
-
-Markdown supports two styles of headers, [Setext] [1] and [atx] [2].
-
-Setext-style headers are "underlined" using equal signs (for first-level
-headers) and dashes (for second-level headers). For example:
-
- This is an H1
- =============
-
- This is an H2
- -------------
-
-Any number of underlining `=`'s or `-`'s will work.
-
-Atx-style headers use 1-6 hash characters at the start of the line,
-corresponding to header levels 1-6. For example:
-
- # This is an H1
-
- ## This is an H2
-
- ###### This is an H6
-
-Optionally, you may "close" atx-style headers. This is purely
-cosmetic -- you can use this if you think it looks better. The
-closing hashes don't even need to match the number of hashes
-used to open the header. (The number of opening hashes
-determines the header level.) :
-
- # This is an H1 #
-
- ## This is an H2 ##
-
- ### This is an H3 ######
-
-
-Blockquotes
-
-Markdown uses email-style `>` characters for blockquoting. If you're
-familiar with quoting passages of text in an email message, then you
-know how to create a blockquote in Markdown. It looks best if you hard
-wrap the text and put a `>` before every line:
-
- > This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
- > consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
- > Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
- >
- > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
- > id sem consectetuer libero luctus adipiscing.
-
-Markdown allows you to be lazy and only put the `>` before the first
-line of a hard-wrapped paragraph:
-
- > This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
- consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
- Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
-
- > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
- id sem consectetuer libero luctus adipiscing.
-
-Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by
-adding additional levels of `>`:
-
- > This is the first level of quoting.
- >
- > > This is nested blockquote.
- >
- > Back to the first level.
-
-Blockquotes can contain other Markdown elements, including headers, lists,
-and code blocks:
-
- > ## This is a header.
- >
- > 1. This is the first list item.
- > 2. This is the second list item.
- >
- > Here's some example code:
- >
- > return shell_exec("echo $input | $markdown_script");
-
-Any decent text editor should make email-style quoting easy. For
-example, with BBEdit, you can make a selection and choose Increase
-Quote Level from the Text menu.
-
-
-Lists
-
-Markdown supports ordered (numbered) and unordered (bulleted) lists.
-
-Unordered lists use asterisks, pluses, and hyphens -- interchangably
--- as list markers:
-
- * Red
- * Green
- * Blue
-
-is equivalent to:
-
- + Red
- + Green
- + Blue
-
-and:
-
- - Red
- - Green
- - Blue
-
-Ordered lists use numbers followed by periods:
-
- 1. Bird
- 2. McHale
- 3. Parish
-
-It's important to note that the actual numbers you use to mark the
-list have no effect on the HTML output Markdown produces. The HTML
-Markdown produces from the above list is:
-
-
- Bird
- McHale
- Parish
-
-
-If you instead wrote the list in Markdown like this:
-
- 1. Bird
- 1. McHale
- 1. Parish
-
-or even:
-
- 3. Bird
- 1. McHale
- 8. Parish
-
-you'd get the exact same HTML output. The point is, if you want to,
-you can use ordinal numbers in your ordered Markdown lists, so that
-the numbers in your source match the numbers in your published HTML.
-But if you want to be lazy, you don't have to.
-
-If you do use lazy list numbering, however, you should still start the
-list with the number 1. At some point in the future, Markdown may support
-starting ordered lists at an arbitrary number.
-
-List markers typically start at the left margin, but may be indented by
-up to three spaces. List markers must be followed by one or more spaces
-or a tab.
-
-To make lists look nice, you can wrap items with hanging indents:
-
- * Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
- Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
- viverra nec, fringilla in, laoreet vitae, risus.
- * Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
- Suspendisse id sem consectetuer libero luctus adipiscing.
-
-But if you want to be lazy, you don't have to:
-
- * Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
- Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
- viverra nec, fringilla in, laoreet vitae, risus.
- * Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
- Suspendisse id sem consectetuer libero luctus adipiscing.
-
-If list items are separated by blank lines, Markdown will wrap the
-items in `` tags in the HTML output. For example, this input:
-
- * Bird
- * Magic
-
-will turn into:
-
-
-
-But this:
-
- * Bird
-
- * Magic
-
-will turn into:
-
-
-
-List items may consist of multiple paragraphs. Each subsequent
-paragraph in a list item must be intended by either 4 spaces
-or one tab:
-
- 1. This is a list item with two paragraphs. Lorem ipsum dolor
- sit amet, consectetuer adipiscing elit. Aliquam hendrerit
- mi posuere lectus.
-
- Vestibulum enim wisi, viverra nec, fringilla in, laoreet
- vitae, risus. Donec sit amet nisl. Aliquam semper ipsum
- sit amet velit.
-
- 2. Suspendisse id sem consectetuer libero luctus adipiscing.
-
-It looks nice if you indent every line of the subsequent
-paragraphs, but here again, Markdown will allow you to be
-lazy:
-
- * This is a list item with two paragraphs.
-
- This is the second paragraph in the list item. You're
- only required to indent the first line. Lorem ipsum dolor
- sit amet, consectetuer adipiscing elit.
-
- * Another item in the same list.
-
-To put a blockquote within a list item, the blockquote's `>`
-delimiters need to be indented:
-
- * A list item with a blockquote:
-
- > This is a blockquote
- > inside a list item.
-
-To put a code block within a list item, the code block needs
-to be indented *twice* -- 8 spaces or two tabs:
-
- * A list item with a code block:
-
-
-
-
-It's worth noting that it's possible to trigger an ordered list by
-accident, by writing something like this:
-
- 1986. What a great season.
-
-In other words, a *number-period-space* sequence at the beginning of a
-line. To avoid this, you can backslash-escape the period:
-
- 1986\. What a great season.
-
-
-
-Code Blocks
-
-Pre-formatted code blocks are used for writing about programming or
-markup source code. Rather than forming normal paragraphs, the lines
-of a code block are interpreted literally. Markdown wraps a code block
-in both `` and `` tags.
-
-To produce a code block in Markdown, simply indent every line of the
-block by at least 4 spaces or 1 tab. For example, given this input:
-
- This is a normal paragraph:
-
- This is a code block.
-
-Markdown will generate:
-
- This is a normal paragraph:
-
- This is a code block.
-
-
-One level of indentation -- 4 spaces or 1 tab -- is removed from each
-line of the code block. For example, this:
-
- Here is an example of AppleScript:
-
- tell application "Foo"
- beep
- end tell
-
-will turn into:
-
- Here is an example of AppleScript:
-
- tell application "Foo"
- beep
- end tell
-
-
-A code block continues until it reaches a line that is not indented
-(or the end of the article).
-
-Within a code block, ampersands (`&`) and angle brackets (`<` and `>`)
-are automatically converted into HTML entities. This makes it very
-easy to include example HTML source code using Markdown -- just paste
-it and indent it, and Markdown will handle the hassle of encoding the
-ampersands and angle brackets. For example, this:
-
-
-
-will turn into:
-
- <div class="footer">
- © 2004 Foo Corporation
- </div>
-
-
-Regular Markdown syntax is not processed within code blocks. E.g.,
-asterisks are just literal asterisks within a code block. This means
-it's also easy to use Markdown to write about Markdown's own syntax.
-
-
-
-Horizontal Rules
-
-You can produce a horizontal rule tag (` `) by placing three or
-more hyphens, asterisks, or underscores on a line by themselves. If you
-wish, you may use spaces between the hyphens or asterisks. Each of the
-following lines will produce a horizontal rule:
-
- * * *
-
- ***
-
- *****
-
- - - -
-
- ---------------------------------------
-
- _ _ _
-
-
-* * *
-
-Span Elements
-
-Links
-
-Markdown supports two style of links: *inline* and *reference*.
-
-In both styles, the link text is delimited by [square brackets].
-
-To create an inline link, use a set of regular parentheses immediately
-after the link text's closing square bracket. Inside the parentheses,
-put the URL where you want the link to point, along with an *optional*
-title for the link, surrounded in quotes. For example:
-
- This is [an example](http://example.com/ "Title") inline link.
-
- [This link](http://example.net/) has no title attribute.
-
-Will produce:
-
- This is
- an example inline link.
-
- This link has no
- title attribute.
-
-If you're referring to a local resource on the same server, you can
-use relative paths:
-
- See my [About](/about/) page for details.
-
-Reference-style links use a second set of square brackets, inside
-which you place a label of your choosing to identify the link:
-
- This is [an example][id] reference-style link.
-
-You can optionally use a space to separate the sets of brackets:
-
- This is [an example] [id] reference-style link.
-
-Then, anywhere in the document, you define your link label like this,
-on a line by itself:
-
- [id]: http://example.com/ "Optional Title Here"
-
-That is:
-
-* Square brackets containing the link identifier (optionally
- indented from the left margin using up to three spaces);
-* followed by a colon;
-* followed by one or more spaces (or tabs);
-* followed by the URL for the link;
-* optionally followed by a title attribute for the link, enclosed
- in double or single quotes.
-
-The link URL may, optionally, be surrounded by angle brackets:
-
- [id]: "Optional Title Here"
-
-You can put the title attribute on the next line and use extra spaces
-or tabs for padding, which tends to look better with longer URLs:
-
- [id]: http://example.com/longish/path/to/resource/here
- "Optional Title Here"
-
-Link definitions are only used for creating links during Markdown
-processing, and are stripped from your document in the HTML output.
-
-Link definition names may constist of letters, numbers, spaces, and punctuation -- but they are *not* case sensitive. E.g. these two links:
-
- [link text][a]
- [link text][A]
-
-are equivalent.
-
-The *implicit link name* shortcut allows you to omit the name of the
-link, in which case the link text itself is used as the name.
-Just use an empty set of square brackets -- e.g., to link the word
-"Google" to the google.com web site, you could simply write:
-
- [Google][]
-
-And then define the link:
-
- [Google]: http://google.com/
-
-Because link names may contain spaces, this shortcut even works for
-multiple words in the link text:
-
- Visit [Daring Fireball][] for more information.
-
-And then define the link:
-
- [Daring Fireball]: http://daringfireball.net/
-
-Link definitions can be placed anywhere in your Markdown document. I
-tend to put them immediately after each paragraph in which they're
-used, but if you want, you can put them all at the end of your
-document, sort of like footnotes.
-
-Here's an example of reference links in action:
-
- I get 10 times more traffic from [Google] [1] than from
- [Yahoo] [2] or [MSN] [3].
-
- [1]: http://google.com/ "Google"
- [2]: http://search.yahoo.com/ "Yahoo Search"
- [3]: http://search.msn.com/ "MSN Search"
-
-Using the implicit link name shortcut, you could instead write:
-
- I get 10 times more traffic from [Google][] than from
- [Yahoo][] or [MSN][].
-
- [google]: http://google.com/ "Google"
- [yahoo]: http://search.yahoo.com/ "Yahoo Search"
- [msn]: http://search.msn.com/ "MSN Search"
-
-Both of the above examples will produce the following HTML output:
-
- I get 10 times more traffic from Google than from
- Yahoo
- or MSN .
-
-For comparison, here is the same paragraph written using
-Markdown's inline link style:
-
- I get 10 times more traffic from [Google](http://google.com/ "Google")
- than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or
- [MSN](http://search.msn.com/ "MSN Search").
-
-The point of reference-style links is not that they're easier to
-write. The point is that with reference-style links, your document
-source is vastly more readable. Compare the above examples: using
-reference-style links, the paragraph itself is only 81 characters
-long; with inline-style links, it's 176 characters; and as raw HTML,
-it's 234 characters. In the raw HTML, there's more markup than there
-is text.
-
-With Markdown's reference-style links, a source document much more
-closely resembles the final output, as rendered in a browser. By
-allowing you to move the markup-related metadata out of the paragraph,
-you can add links without interrupting the narrative flow of your
-prose.
-
-
-Emphasis
-
-Markdown treats asterisks (`*`) and underscores (`_`) as indicators of
-emphasis. Text wrapped with one `*` or `_` will be wrapped with an
-HTML `` tag; double `*`'s or `_`'s will be wrapped with an HTML
-`` tag. E.g., this input:
-
- *single asterisks*
-
- _single underscores_
-
- **double asterisks**
-
- __double underscores__
-
-will produce:
-
- single asterisks
-
- single underscores
-
- double asterisks
-
- double underscores
-
-You can use whichever style you prefer; the lone restriction is that
-the same character must be used to open and close an emphasis span.
-
-Emphasis can be used in the middle of a word:
-
- un*fucking*believable
-
-But if you surround an `*` or `_` with spaces, it'll be treated as a
-literal asterisk or underscore.
-
-To produce a literal asterisk or underscore at a position where it
-would otherwise be used as an emphasis delimiter, you can backslash
-escape it:
-
- \*this text is surrounded by literal asterisks\*
-
-
-
-Code
-
-To indicate a span of code, wrap it with backtick quotes (`` ` ``).
-Unlike a pre-formatted code block, a code span indicates code within a
-normal paragraph. For example:
-
- Use the `printf()` function.
-
-will produce:
-
- Use the printf()
function.
-
-To include a literal backtick character within a code span, you can use
-multiple backticks as the opening and closing delimiters:
-
- ``There is a literal backtick (`) here.``
-
-which will produce this:
-
- There is a literal backtick (`) here.
-
-The backtick delimiters surrounding a code span may include spaces --
-one after the opening, one before the closing. This allows you to place
-literal backtick characters at the beginning or end of a code span:
-
- A single backtick in a code span: `` ` ``
-
- A backtick-delimited string in a code span: `` `foo` ``
-
-will produce:
-
- A single backtick in a code span: `
-
- A backtick-delimited string in a code span: `foo`
-
-With a code span, ampersands and angle brackets are encoded as HTML
-entities automatically, which makes it easy to include example HTML
-tags. Markdown will turn this:
-
- Please don't use any `` tags.
-
-into:
-
- Please don't use any <blink>
tags.
-
-You can write this:
-
- `—` is the decimal-encoded equivalent of `—`.
-
-to produce:
-
- —
is the decimal-encoded
- equivalent of —
.
-
-
-
-Images
-
-Admittedly, it's fairly difficult to devise a "natural" syntax for
-placing images into a plain text document format.
-
-Markdown uses an image syntax that is intended to resemble the syntax
-for links, allowing for two styles: *inline* and *reference*.
-
-Inline image syntax looks like this:
-
- ![Alt text](/path/to/img.jpg)
-
- ![Alt text](/path/to/img.jpg "Optional title")
-
-That is:
-
-* An exclamation mark: `!`;
-* followed by a set of square brackets, containing the `alt`
- attribute text for the image;
-* followed by a set of parentheses, containing the URL or path to
- the image, and an optional `title` attribute enclosed in double
- or single quotes.
-
-Reference-style image syntax looks like this:
-
- ![Alt text][id]
-
-Where "id" is the name of a defined image reference. Image references
-are defined using syntax identical to link references:
-
- [id]: url/to/image "Optional title attribute"
-
-As of this writing, Markdown has no syntax for specifying the
-dimensions of an image; if this is important to you, you can simply
-use regular HTML ` ` tags.
-
-
-* * *
-
-
-Miscellaneous
-
-Automatic Links
-
-Markdown supports a shortcut style for creating "automatic" links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:
-
-
-
-Markdown will turn this into:
-
- http://example.com/
-
-Automatic links for email addresses work similarly, except that
-Markdown will also perform a bit of randomized decimal and hex
-entity-encoding to help obscure your address from address-harvesting
-spambots. For example, Markdown will turn this:
-
-
-
-into something like this:
-
- address@exa
- mple.com
-
-which will render in a browser as a clickable link to "address@example.com".
-
-(This sort of entity-encoding trick will indeed fool many, if not
-most, address-harvesting bots, but it definitely won't fool all of
-them. It's better than nothing, but an address published in this way
-will probably eventually start receiving spam.)
-
-
-
-Backslash Escapes
-
-Markdown allows you to use backslash escapes to generate literal
-characters which would otherwise have special meaning in Markdown's
-formatting syntax. For example, if you wanted to surround a word with
-literal asterisks (instead of an HTML `` tag), you can backslashes
-before the asterisks, like this:
-
- \*literal asterisks\*
-
-Markdown provides backslash escapes for the following characters:
-
- \ backslash
- ` backtick
- * asterisk
- _ underscore
- {} curly braces
- [] square brackets
- () parentheses
- # hash mark
- + plus sign
- - minus sign (hyphen)
- . dot
- ! exclamation mark
-
diff --git a/test/fixtures/remarked_pending/nested_blockquotes.html b/test/fixtures/remarked_pending/nested_blockquotes.html
deleted file mode 100644
index d8ec7f8..0000000
--- a/test/fixtures/remarked_pending/nested_blockquotes.html
+++ /dev/null
@@ -1,9 +0,0 @@
-
- foo
-
-
- bar
-
-
- foo
-
diff --git a/test/fixtures/remarked_pending/nested_blockquotes.md b/test/fixtures/remarked_pending/nested_blockquotes.md
deleted file mode 100644
index ed3c624..0000000
--- a/test/fixtures/remarked_pending/nested_blockquotes.md
+++ /dev/null
@@ -1,5 +0,0 @@
-> foo
->
-> > bar
->
-> foo
diff --git a/test/fixtures/remarked_pending/nested_code.html b/test/fixtures/remarked_pending/nested_code.html
deleted file mode 100644
index c370592..0000000
--- a/test/fixtures/remarked_pending/nested_code.html
+++ /dev/null
@@ -1 +0,0 @@
-hi ther `` ok ```
diff --git a/test/fixtures/remarked_pending/nested_code.md b/test/fixtures/remarked_pending/nested_code.md
deleted file mode 100644
index 910e3d4..0000000
--- a/test/fixtures/remarked_pending/nested_code.md
+++ /dev/null
@@ -1 +0,0 @@
-````` hi ther `` ok ``` `````
diff --git a/test/fixtures/remarked_pending/nested_em.html b/test/fixtures/remarked_pending/nested_em.html
deleted file mode 100644
index 77151ad..0000000
--- a/test/fixtures/remarked_pending/nested_em.html
+++ /dev/null
@@ -1,2 +0,0 @@
-test test test
-test test test
diff --git a/test/fixtures/remarked_pending/nested_em.md b/test/fixtures/remarked_pending/nested_em.md
deleted file mode 100644
index 550d0eb..0000000
--- a/test/fixtures/remarked_pending/nested_em.md
+++ /dev/null
@@ -1,3 +0,0 @@
-*test **test** test*
-
-_test __test__ test_
diff --git a/test/fixtures/remarked_pending/nested_square_link.html b/test/fixtures/remarked_pending/nested_square_link.html
deleted file mode 100644
index c8b7940..0000000
--- a/test/fixtures/remarked_pending/nested_square_link.html
+++ /dev/null
@@ -1 +0,0 @@
-the ]
character
diff --git a/test/fixtures/remarked_pending/nested_square_link.md b/test/fixtures/remarked_pending/nested_square_link.md
deleted file mode 100644
index 82226ed..0000000
--- a/test/fixtures/remarked_pending/nested_square_link.md
+++ /dev/null
@@ -1 +0,0 @@
-[the `]` character](/url)
diff --git a/test/fixtures/remarked_pending/not_a_link.html b/test/fixtures/remarked_pending/not_a_link.html
deleted file mode 100644
index a01685d..0000000
--- a/test/fixtures/remarked_pending/not_a_link.html
+++ /dev/null
@@ -1 +0,0 @@
-[test](not a link)
diff --git a/test/fixtures/remarked_pending/not_a_link.md b/test/fixtures/remarked_pending/not_a_link.md
deleted file mode 100644
index 26f6043..0000000
--- a/test/fixtures/remarked_pending/not_a_link.md
+++ /dev/null
@@ -1 +0,0 @@
-\[test](not a link)
diff --git a/test/fixtures/remarked_pending/ordered_and_unordered_lists.html b/test/fixtures/remarked_pending/ordered_and_unordered_lists.html
deleted file mode 100644
index a8ff037..0000000
--- a/test/fixtures/remarked_pending/ordered_and_unordered_lists.html
+++ /dev/null
@@ -1,110 +0,0 @@
-Unordered
-Asterisks tight:
-
-asterisk 1
-asterisk 2
-asterisk 3
-
-Asterisks loose:
-
-asterisk 1
-asterisk 2
-asterisk 3
-
-
-Pluses tight:
-
-Plus 1
-Plus 2
-Plus 3
-
-Pluses loose:
-
-Plus 1
-Plus 2
-Plus 3
-
-
-Minuses tight:
-
-Minus 1
-Minus 2
-Minus 3
-
-Minuses loose:
-
-Minus 1
-Minus 2
-Minus 3
-
-Ordered
-Tight:
-
-First
-Second
-Third
-
-and:
-
-One
-Two
-Three
-
-Loose using tabs:
-
-First
-Second
-Third
-
-and using spaces:
-
-One
-Two
-Three
-
-Multiple paragraphs:
-
-Item 1, graf one.
-Item 2. graf two. The quick brown fox jumped over the lazy dog's
-back.
-Item 2.
-Item 3.
-
-Nested
-
-Here's another:
-
-First
-Second:
-
-Third
-
-Same thing but with paragraphs:
-
-First
-Second:
-
-Third
-
-This was an error in Markdown 1.0.1:
-
diff --git a/test/fixtures/remarked_pending/ordered_and_unordered_lists.md b/test/fixtures/remarked_pending/ordered_and_unordered_lists.md
deleted file mode 100644
index 7f3b497..0000000
--- a/test/fixtures/remarked_pending/ordered_and_unordered_lists.md
+++ /dev/null
@@ -1,131 +0,0 @@
-## Unordered
-
-Asterisks tight:
-
-* asterisk 1
-* asterisk 2
-* asterisk 3
-
-
-Asterisks loose:
-
-* asterisk 1
-
-* asterisk 2
-
-* asterisk 3
-
-* * *
-
-Pluses tight:
-
-+ Plus 1
-+ Plus 2
-+ Plus 3
-
-
-Pluses loose:
-
-+ Plus 1
-
-+ Plus 2
-
-+ Plus 3
-
-* * *
-
-
-Minuses tight:
-
-- Minus 1
-- Minus 2
-- Minus 3
-
-
-Minuses loose:
-
-- Minus 1
-
-- Minus 2
-
-- Minus 3
-
-
-## Ordered
-
-Tight:
-
-1. First
-2. Second
-3. Third
-
-and:
-
-1. One
-2. Two
-3. Three
-
-
-Loose using tabs:
-
-1. First
-
-2. Second
-
-3. Third
-
-and using spaces:
-
-1. One
-
-2. Two
-
-3. Three
-
-Multiple paragraphs:
-
-1. Item 1, graf one.
-
- Item 2. graf two. The quick brown fox jumped over the lazy dog's
- back.
-
-2. Item 2.
-
-3. Item 3.
-
-
-
-## Nested
-
-* Tab
- * Tab
- * Tab
-
-Here's another:
-
-1. First
-2. Second:
- * Fee
- * Fie
- * Foe
-3. Third
-
-Same thing but with paragraphs:
-
-1. First
-
-2. Second:
- * Fee
- * Fie
- * Foe
-
-3. Third
-
-
-This was an error in Markdown 1.0.1:
-
-* this
-
- * sub
-
- that
diff --git a/test/fixtures/remarked_pending/same_bullet.html b/test/fixtures/remarked_pending/same_bullet.html
deleted file mode 100644
index 9220741..0000000
--- a/test/fixtures/remarked_pending/same_bullet.html
+++ /dev/null
@@ -1,5 +0,0 @@
-
diff --git a/test/fixtures/remarked_pending/same_bullet.md b/test/fixtures/remarked_pending/same_bullet.md
deleted file mode 100644
index 27a8967..0000000
--- a/test/fixtures/remarked_pending/same_bullet.md
+++ /dev/null
@@ -1,3 +0,0 @@
-* test
-+ test
-- test
diff --git a/test/fixtures/remarked_pending/smartypants_text.html b/test/fixtures/remarked_pending/smartypants_text.html
deleted file mode 100644
index e4cf839..0000000
--- a/test/fixtures/remarked_pending/smartypants_text.html
+++ /dev/null
@@ -1,4 +0,0 @@
-Hello world ‘how’ “are” you — today…
-“It’s a more ‘challenging’ smartypants test…”
-‘And,’ as a bonus — “one
-multiline” test!
diff --git a/test/fixtures/remarked_pending/smartypants_text.md b/test/fixtures/remarked_pending/smartypants_text.md
deleted file mode 100644
index d91c8dc..0000000
--- a/test/fixtures/remarked_pending/smartypants_text.md
+++ /dev/null
@@ -1,6 +0,0 @@
-Hello world 'how' "are" you -- today...
-
-"It's a more 'challenging' smartypants test..."
-
-'And,' as a bonus -- "one
-multiline" test!
diff --git a/test/fixtures/remarked_pending/strong_and_em_together.html b/test/fixtures/remarked_pending/strong_and_em_together.html
deleted file mode 100644
index 2629594..0000000
--- a/test/fixtures/remarked_pending/strong_and_em_together.html
+++ /dev/null
@@ -1,4 +0,0 @@
-This is strong and em.
-So is this word.
-This is strong and em.
-So is this word.
diff --git a/test/fixtures/remarked_pending/strong_and_em_together.md b/test/fixtures/remarked_pending/strong_and_em_together.md
deleted file mode 100644
index 95ee690..0000000
--- a/test/fixtures/remarked_pending/strong_and_em_together.md
+++ /dev/null
@@ -1,7 +0,0 @@
-***This is strong and em.***
-
-So is ***this*** word.
-
-___This is strong and em.___
-
-So is ___this___ word.
diff --git a/test/fixtures/remarked_pending/tabs.html b/test/fixtures/remarked_pending/tabs.html
deleted file mode 100644
index e5351f2..0000000
--- a/test/fixtures/remarked_pending/tabs.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-Code:
-this code block is indented by one tab
-
-And:
- this code block is indented by two tabs
-
-And:
-+ this is an example list item
- indented with tabs
-+ this is an example list item
- indented with spaces
-
diff --git a/test/fixtures/remarked_pending/tabs.md b/test/fixtures/remarked_pending/tabs.md
deleted file mode 100644
index 589d113..0000000
--- a/test/fixtures/remarked_pending/tabs.md
+++ /dev/null
@@ -1,21 +0,0 @@
-+ this is a list item
- indented with tabs
-
-+ this is a list item
- indented with spaces
-
-Code:
-
- this code block is indented by one tab
-
-And:
-
- this code block is indented by two tabs
-
-And:
-
- + this is an example list item
- indented with tabs
-
- + this is an example list item
- indented with spaces
diff --git a/test/fixtures/remarked_pending/tricky_list.html b/test/fixtures/remarked_pending/tricky_list.html
deleted file mode 100644
index 12cc8df..0000000
--- a/test/fixtures/remarked_pending/tricky_list.html
+++ /dev/null
@@ -1,16 +0,0 @@
-hello world
-
-hello world
-
-hello world
-
-hello world
-
diff --git a/test/fixtures/remarked_pending/tricky_list.md b/test/fixtures/remarked_pending/tricky_list.md
deleted file mode 100644
index 9aa76ce..0000000
--- a/test/fixtures/remarked_pending/tricky_list.md
+++ /dev/null
@@ -1,15 +0,0 @@
-**hello** _world_
-
-* hello world
-
-**hello** _world_
-
-* hello world
-
-**hello** _world_
-
-* Hello world
-
-**hello** _world_
-
-* hello world
diff --git a/test/remarked.js b/test/remarked.js
deleted file mode 100644
index d17a2cb..0000000
--- a/test/remarked.js
+++ /dev/null
@@ -1,28 +0,0 @@
-/*global describe*/
-'use strict';
-
-
-var path = require('path');
-
-
-var utils = require('./utils');
-var Remarked = require('../');
-
-
-describe('remarked', function () {
- var md = new Remarked();
-
- // Set options, to give output more close to remarked
- md.set({
- langPrefix: 'lang-'
- });
-
- utils.addTests(path.join(__dirname, 'fixtures/remarked_ok'), md);
-});
-
-
-describe('remarked pending', function () {
- var md = new Remarked();
-
- utils.addTests(path.join(__dirname, 'fixtures/remarked_pending'), md, true);
-});