Page-breaks between the mdframed content disappear when nested, why? - TeX

TopAnswers TeX

Meta

Databases

TeX

Code Golf

APL

C++

.net

db<>fiddle

Java

*nix

PHP

PowerShell

Python

Rust

टेक्-मराठी

Typst

Web Client Dev

Web Server Dev

Page-breaks between the mdframed content disappear when nested, why?

add tag

निरंजन

Question title says it all, MWE:

```
\documentclass{article}
\usepackage{lipsum}
\usepackage{mdframed}

\begin{document}
\begin{mdframed}
  \lipsum
  \begin{mdframed}
    \lipsum
    \begin{mdframed}
      \lipsum
    \end{mdframed}
  \end{mdframed}
\end{mdframed}
\end{document}
```

Why suddenly does the page-breaking stop?

comments

transcript

samcarter replying to निरंजन

Not surprising

निरंजन

@samcarter Even with blanker it is producing inconsistent results. See for example:

```
\documentclass{article}
\usepackage[most]{tcolorbox}
\usepackage{lipsum}
\newtcolorbox{mytcb}[1][]{%
  enforce breakable,% 
  blanker,%
  left={25pt},%
  #1%
}

\begin{document}
\section{Case 1}
\begin{mytcb}
  \lipsum[1]
  \begin{mytcb}
    \lipsum[1]
  \end{mytcb}
\end{mytcb}
\newpage
\section{Case 2}
\begin{mytcb}
  \lipsum
  \begin{mytcb}
    \lipsum
  \end{mytcb}
\end{mytcb}
\end{document}
```

In case 1 it accepts nesting without any problem, but as soon as the nested thing starts crossing the page it prints it on a fresh page like can be seen in case 2. Is this also a part of the _"mess"_ which the package author has mentioned in the doc? Is there any automatic solution to this? I just want case 2 to be continuous and I am done.

निरंजन replying to samcarter

Ah, I am using `blanker`, so this isn't going to bother me. :)

samcarter

![Screenshot 2022-07-21 at 16.40.53.png](/image?hash=2e4a81482880d58e68b89d9e7df15b5f965b5fb80e3b736de9965ff17079e9bf)

निरंजन replying to samcarter

I tried it, I couldn't find anything bad or objectionable as of now.

samcarter replying to निरंजन

Try it and look at the result and you'll understand what mess means :)

निरंजन

The manual says:

> But, a breakable box inside a breakable box will usually give a mess.

Quite vague. :(

What are the possible risks?

निरंजन

Oh, but just found out that `tcolorbox` has an option `enforce breakable` which makes it possible, don't know the risks yet, I shall look into it.

निरंजन replying to samcarter

Sad, the same problem persists with `tcolorbox` too.

samcarter replying to निरंजन

https://github.com/marcodaniel/mdframed/issues/3

निरंजन

I changed the question now.

निरंजन replying to samcarter

Actually I had a big definition for `myenv`, but while reducing it to an MWE, I didn't realize that having `xparse` itself was unnecessary. I missed one step of minimizing the working example :P

निरंजन replying to samcarter

Ah, it's `mdframed` only! Thanks. Is this a known problem?

निरंजन

An unrelated question,

```
  \begin{mdframed}%
    {#1}%
  \end{mdframed}%
```

Do I need `%`s here? If yes, do I need them with the `myenv`s too? Generally I haven't seen `%`s after `\begin{env}`s and `\end{env}`s, but to avoid spurious spaces, should it be there or not?

samcarter

@निरंजन, re: [your question](#question), you can test if this is xparse or mdframe:  
```  
\documentclass{article}
\usepackage{lipsum}
\usepackage{mdframed}
\begin{document}
\begin{mdframed}
  \lipsum
  \begin{mdframed}
    \lipsum
    \begin{mdframed}
      \lipsum
    \end{mdframed}
  \end{mdframed}
\end{mdframed}
\end{document}  
```

0 Answers