LaTeX: Better placement of non-text code cell output

[mgeier]

I did the same thing for nbsphinx in spatialaudio/nbsphinx@fc4fe32, so I thought I'll just apply the same trick here.

Before:

After:

Obviously, the vertical distance to the next paragraph is still too short, but I didn't know what's the best way to fix this. It's not obvious to me, any ideas?

[mgeier]

OK, I tried to improve the distance a bit (1f617c3), but the spacing is still off.

IMHO there is too much space between code cell inputs and outputs and too little space after the outputs.

[mgeier]

BTW, I forgot to mention that I made above screenshots with ipython/ipython#11357 in place. Without that, the math stuff would be centered.

[mgeier]

Just a little update: Please note that my PR here adds a minipage around the output, therefore making page breaks within the output impossible. That's not good!

In the meantime I've come up with a way to change this in nbsphinx (spatialaudio/nbsphinx#218), but this uses some Sphinx machinery, so sadly this isn't applicable here.

Hopefully somebody else comes up with a proper solution for nbconvert.

See also #323.

[t-makaro]

This could probably be redone within the new #992 template. Right now, text outputs are placed within a breakable tcolorbox. Image outputs could be placed within an unbreakable tcolorbox which would fix the issue with prompts appearing on a different page then the image. What outputs, other than text, need to be in a breakable box?

[mgeier]

@t-makaro

What outputs, other than text, need to be in a breakable box?

I guess there is plain text, Markdown and "stream" text (potentially with ANSI escape sequences).

Anyway, after the recent LaTeX improvements, this PR is obsolete and can be closed.