From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: HTML :exports both problem
Date: Mon, 19 Nov 2018 11:16:20 -0500 [thread overview]
Message-ID: <87va4tjb57.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: CAFAhFSXaLHaABJzVEA4Oo05=63Ba=RMaxxerF1LY_kscdL+yOg@mail.gmail.com
Lawrence Bottorff <borgauf@gmail.com> writes:
> That did the trick. Though I'm wondering why the #+name: would cause such craziness. . . Also, would anyone know why
>
> #+begin_src lisp :results output :exports both
> (dotimes (x 20)
> (dotimes (y 20)
> (format t "~3d " (* (1+ x) (1+ y))))
> (format t "~%"))
> #+end_src
>
> produces
>
> #+RESULTS:
> #+begin_example
> 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
> 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40
> ...
> #+end_example
>
> which is great. How did it know to sandwich the output between #+begin_example/#+end_example, thereby preserving the linefeeds? That's amazing. Is there a way to toggle that behavior?
>
I believe this is controlled by `org-babel-min-lines-for-block-output'. Help
on this variable says:
,----
| org-babel-min-lines-for-block-output is a variable defined in ‘ob-core.el’.
| Its value is 10
|
| Documentation:
| The minimum number of lines for block output.
| If number of lines of output is equal to or exceeds this
| value, the output is placed in a #+begin_example...#+end_example
| block. Otherwise the output is marked as literal by inserting
| colons at the starts of the lines. This variable only takes
| effect if the :results output option is in effect.
`----
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
prev parent reply other threads:[~2018-11-19 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 5:55 HTML :exports both problem Lawrence Bottorff
2018-11-19 9:16 ` Eric S Fraga
2018-11-19 15:02 ` Lawrence Bottorff
2018-11-19 15:51 ` Eric S Fraga
2018-11-19 16:16 ` Nick Dokos [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87va4tjb57.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).