You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present Pandoc is emitting \begin{verbatim} around fenced code blocks, so we would need to intercept these and instead insert \begin{Verbatim}[samepage=true].
Far better would be if this was simply a package level setting we could recommend and put in the default preamble.
The text was updated successfully, but these errors were encountered:
Ah. Pandoc already expected (and in its default template included, which we then ported to the beginning function in LatexPreamble, which is then emitted as 99_Beginning.latex file in the temporary directory) a \DefineVerbatimEnvironment{Highlighting}{Verbatim}. We can use that to change the initial (aka default) option values for the custom verbatim environment.
So the line needs to have the samepage=true option added. But now I'm doubting the wisdom of this. This is typesetting; if someone wants a pagebreak in a different place they can use \clearpage. Hm.
Ideally verbatim environments would not have page breaks in them.
According to this answer on TeX StackExchange, the following has the desired effect:
casual testing shows this to be workable.
At present Pandoc is emitting
\begin{verbatim}
around fenced code blocks, so we would need to intercept these and instead insert\begin{Verbatim}[samepage=true]
.Far better would be if this was simply a package level setting we could recommend and put in the default preamble.
The text was updated successfully, but these errors were encountered: