-
Notifications
You must be signed in to change notification settings - Fork 572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meaning of "Out" for export #365
Comments
One possibility would be to never use the return value and always use |
By default, nbconvert tries to put It should be straightforward to make a template that doesn't use |
Yeah I did the later, which puts an Out before every group. |
So the solution is "create templates that look reasonable" and close? I haven't checked all the templates, though. |
I'd be OK with skipping the |
Now #554 takes care of hiding output prompts with |
I realized a bit late that "Out" is only attached to the return value of a cell, not to output going to standard out. This is somewhat non-obvious.
I guess that is something done very intentionally, but it leads to some odd effects when converting to other formats, in particular markdown.
I kind of expected the "Out" do separate the input from the output, because there is no formatting as in the HTML. But that's not how it works. The "Out" could be anywhere in the output, or not present at all. And in black and white (print) the distinction between code and output can also not be made via the syntax highlighting.
For my book, I would like to have an "Out" associated with the output to make clear what the output is, but that means I'm changing the semantics with respect to what it means in the notebook, which is also not ideal.
Has anyone thought about this? What do you think would be a good way to format "the output" of a cell when exporting for publishing?
In notebook usage, I never really paid attention to where the "Out" is because the colors are a much stronger cue.
The text was updated successfully, but these errors were encountered: