diff options
| author | John MacFarlane <jgm@berkeley.edu> | 2021-09-19 12:09:51 -0700 |
|---|---|---|
| committer | John MacFarlane <jgm@berkeley.edu> | 2021-09-21 12:37:42 -0700 |
| commit | c266734448544a118ed80e47deaa2590131c7f84 (patch) | |
| tree | d5793b1dc732456894c96e8ee6829dab9d539388 /test/writer.org | |
| parent | 5f7e7f539a02818d0a94309b15d648d51d1eaee6 (diff) | |
| download | pandoc-c266734448544a118ed80e47deaa2590131c7f84.tar.gz | |
Use pretty-simple to format native output.
Previously we used our own homespun formatting. But this
produces over-long lines that aren't ideal for diffs in tests.
Easier to use something off-the-shelf and standard.
Closes #7580.
Performance is slower by about a factor of 10, but this isn't
really a problem because native isn't suitable as a serialization
format. (For serialization you should use json, because the reader
is so much faster than native.)
Diffstat (limited to 'test/writer.org')
| -rw-r--r-- | test/writer.org | 15 |
1 files changed, 7 insertions, 8 deletions
diff --git a/test/writer.org b/test/writer.org index 38ec35a3e..604aca21d 100644 --- a/test/writer.org +++ b/test/writer.org @@ -566,8 +566,8 @@ Superscripts: a^{bc}d a^{/hello/} a^{hello there}. Subscripts: H_{2}O, H_{23}O, H_{many of them}O. -These should not be superscripts or subscripts, because of the unescaped -spaces: a^b c^d, a~b c~d. +These should not be superscripts or subscripts, because of the unescaped spaces: +a^b c^d, a~b c~d. -------------- @@ -739,8 +739,7 @@ Foo [[/url/][biz]]. :PROPERTIES: :CUSTOM_ID: with-ampersands :END: -Here's a [[http://example.com/?foo=1&bar=2][link with an ampersand in the -URL]]. +Here's a [[http://example.com/?foo=1&bar=2][link with an ampersand in the URL]]. Here's a link with an amersand in the link text: [[http://att.com/][AT&T]]. @@ -801,8 +800,8 @@ note.[fn:3] This paragraph should not be part of the note, as it is not indented. -[fn:1] Here is the footnote. It can go anywhere after the footnote reference. - It need not be placed at the end of the document. +[fn:1] Here is the footnote. It can go anywhere after the footnote reference. It + need not be placed at the end of the document. [fn:2] Here's the long note. This one contains multiple blocks. @@ -813,8 +812,8 @@ This paragraph should not be part of the note, as it is not indented. { <code> } #+end_example - If you want, you can indent every line, but you can also be lazy and - just indent the first line of each block. + If you want, you can indent every line, but you can also be lazy and just + indent the first line of each block. [fn:3] This is /easier/ to type. Inline notes may contain [[http://google.com][links]] and =]= verbatim characters, as well as |