pandoc/test/command/5714.md

```
% pandoc -t native
# hi _a
b_

# hi _c
c
^D
[ Header
    1 ( "hi-_a" , [] , [] ) [ Str "hi" , Space , Str "_a" ]
, Para [ Str "b_" ]
, Header
    1 ( "hi-_c" , [] , [] ) [ Str "hi" , Space , Str "_c" ]
, Para [ Str "c" ]
]
```
Markdown reader: Headers: don't parse content over newline boundary. Closes #5714. 2019-08-27 19:15:00 +02:00			```
			`% pandoc -t native`
			`# hi _a`
			`b_`

			`# hi _c`
			`c`
			`^D`
Switch from pretty-simple to pretty-show for native output. Update tests. Reason: it turns out that the native output generated by pretty-simple isn't always readable by the native reader. According to https://github.com/cdepillabout/pretty-simple/issues/99 it is not a design goal of the library that the rendered values be readable using 'read'. This makes it unsuitable for our purposes. pretty-show is a bit slower and it uses 4-space indents (non-configurable), but it doesn't have this serious drawback. 2021-09-29 06:17:53 +02:00			`[ Header`
			`1 ( "hi-_a" , [] , [] ) [ Str "hi" , Space , Str "_a" ]`
			`, Para [ Str "b_" ]`
			`, Header`
			`1 ( "hi-_c" , [] , [] ) [ Str "hi" , Space , Str "_c" ]`
			`, Para [ Str "c" ]`
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.) 2021-09-19 21:09:51 +02:00			`]`
Markdown reader: Headers: don't parse content over newline boundary. Closes #5714. 2019-08-27 19:15:00 +02:00			```