Tissevert/pandoc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
pandoc/test/command/4624.md

34 lines
518 B
Markdown
Raw Normal View History

LaTeX reader: allow verbatim blocks ending with blank lines. Closes #4624.
2018-09-29 19:57:11 +02:00
```
% pandoc -f latex -t native
\begin{Verbatim}[key1=value1]
code1
\end{Verbatim}
\begin{lstlisting}[key2=value2]
code2
\end{lstlisting}
\begin{verbatim}
code3
\end{verbatim}
\begin{verbatim}
code4
\end{verbatim}
\begin{verbatim}
code5\end{verbatim}
^D
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
[ CodeBlock
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
( "" , [] , [ ( "key1" , "value1" ) ] ) "code1\n"
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
, CodeBlock
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
( "" , [] , [ ( "key2" , "value2" ) ] ) "code2\n "
, CodeBlock ( "" , [] , [] ) "code3"
, CodeBlock ( "" , [] , [] ) "code4"
, CodeBlock ( "" , [] , [] ) "code5"
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
]
LaTeX reader: allow verbatim blocks ending with blank lines. Closes #4624.
2018-09-29 19:57:11 +02:00
```
Reference in a new issue Copy permalink