From: John Hendy <jw.hendy@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: What determines if R source block output is wrapped in begin_example or not?
Date: Fri, 14 Jan 2022 07:13:40 -0600 [thread overview]
Message-ID: <CA+M2ft8iRtCDxewLpcf5tG4c4rD2z3H6X9dxZTpmC0yh2Q6agg@mail.gmail.com> (raw)
In-Reply-To: <87r19ahcmd.fsf@ucl.ac.uk>
On Fri, Jan 14, 2022 at 3:48 AM Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
> Have a look at
>
> ,----[ C-h v org-babel-min-lines-for-block-output RET ]
> | org-babel-min-lines-for-block-output is a variable defined in ‘ob-core.el’.
> |
> | Its value is 10
> |
> | 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.
> |
> `----
Well, indeed, that's definitely it! Out of curiosity, despite being an
org-mode user for... 10(?) yrs now, is there a heuristic on when to
look at the manual vs. when to M-x help RET v RET
[guess-and-check-randomly]?
I don't feel familiar enough with org internals to have known where to
look... despite this being 100% exactly what I experienced, so much so
it's comedic how accurately it's written vs. what I I would have
described.
Thanks so much!
John
> --
> : Eric S Fraga, with org release_9.5.2-298-g1f48d2 in Emacs 29.0.50
next prev parent reply other threads:[~2022-01-14 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 20:49 What determines if R source block output is wrapped in begin_example or not? John Hendy
2022-01-14 3:04 ` John Hendy
2022-01-14 9:48 ` Eric S Fraga
2022-01-14 13:13 ` John Hendy [this message]
2022-01-14 14:04 ` Eric S Fraga
2022-01-14 14:44 ` Ihor Radchenko
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=CA+M2ft8iRtCDxewLpcf5tG4c4rD2z3H6X9dxZTpmC0yh2Q6agg@mail.gmail.com \
--to=jw.hendy@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).