Show More
@@ -38,10 +38,24 b'' | |||
|
38 | 38 | |
|
39 | 39 | % codecell is the whole input+output set of blocks that a Code cell can |
|
40 | 40 | % generate. |
|
41 | \newenvironment{codecell}{% | |
|
42 | \def\FrameCommand{\color{mediumgray} \vrule width 1pt \hspace{5pt}}% | |
|
43 | \MakeFramed{\vspace{-0.5em}\FrameRestore}} | |
|
44 | {\unskip\endMakeFramed} | |
|
41 | ||
|
42 | % TODO: unfortunately, it seems that using a framed codecell environment breaks | |
|
43 | % the ability of the frames inside of it to be broken across pages. This | |
|
44 | % causes at least the problem of having lots of empty space at the bottom of | |
|
45 | % pages as new frames are moved to the next page, and if a single frame is too | |
|
46 | % long to fit on a page, will completely stop latex from compiling the | |
|
47 | % document. So unless we figure out a solution to this, we'll have to instead | |
|
48 | % leave the codecell env. as empty. I'm keeping the original codecell | |
|
49 | % definition here (a thin vertical bar) for reference, in case we find a | |
|
50 | % solution to the page break issue. | |
|
51 | ||
|
52 | %% \newenvironment{codecell}{% | |
|
53 | %% \def\FrameCommand{\color{mediumgray} \vrule width 1pt \hspace{5pt}}% | |
|
54 | %% \MakeFramed{\vspace{-0.5em}}} | |
|
55 | %% {\unskip\endMakeFramed} | |
|
56 | ||
|
57 | % For now, make this a no-op... | |
|
58 | \newenvironment{codecell}{} | |
|
45 | 59 | |
|
46 | 60 | \newenvironment{codeinput}{% |
|
47 | 61 | \def\FrameCommand{\colorbox{inputbackground}}% |
General Comments 0
You need to be logged in to leave comments.
Login now