emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ista Zahn <istazahn@gmail.com>
To: Grant Rettke <gcr@wisdomandwonder.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: How to disable block evaluation results being wrapped with a single character like =?
Date: Mon, 4 Aug 2014 13:36:41 -0400	[thread overview]
Message-ID: <CA+vqiLF_GKobyB1NOUkTHSaoRnfiGwDF_V5GOr4HrkUJRwmmHg@mail.gmail.com> (raw)
In-Reply-To: <CAAjq1mddBKz9EXy5CR_OUB2L2J3y9cO6xmativBM2tGyucvUnA@mail.gmail.com>

Hi Grant,

I cannot reproduce. Here is what I see:

#+BEGIN_SRC emacs-lisp
  (setq  org-babel-min-lines-for-block-output 10)
  (print 1)
#+END_SRC

#+RESULTS:
: 1

#+BEGIN_SRC emacs-lisp
  (setq  org-babel-min-lines-for-block-output 0)
  (print 1)
#+END_SRC

#+RESULTS:
#+begin_example
1
#+end_example

Perhaps try with emacs -q and see what you get.


Best,
Ista

On Mon, Aug 4, 2014 at 1:23 PM, Grant Rettke <gcr@wisdomandwonder.com> wrote:
> That is what I was thinking.
>
> I had set it to 0.
>
> What happened is that instead of a block showing up, the results were
> delimited with a prepended '=' instead of a ':'.
>
> Unfortunately I forgot how this occurred, as I manually wrapped the
> result with a block instead, so org was happy to use that instead.
> Grant Rettke | ACM, ASA, FSF, IEEE, SIAM
> gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
> “Wisdom begins in wonder.” --Socrates
> ((λ (x) (x x)) (λ (x) (x x)))
> “Life has become immeasurably better since I have been forced to stop
> taking it seriously.” --Thompson
>
>
> On Sun, Aug 3, 2014 at 7:24 PM, Ista Zahn <istazahn@gmail.com> wrote:
>> I'm somewhat confused by the "wrapped in =" part, but I think you are
>> looking for 'C-h v org-babel-min-lines-for-block-output'.
>>
>> Best,
>> Ista
>>
>> On Sun, Aug 3, 2014 at 3:03 PM, Grant Rettke <gcr@wisdomandwonder.com> wrote:
>>> Hi,
>>>
>>> Sometimes block evaluation results are wrapped with a single character like =.
>>>
>>> When exporting to latex, the results block is lost.
>>>
>>> How may one force block evaluation always to be wrapped properly for
>>> export to latex?
>>>
>>> org 8.2.7a
>>>
>>> Kind regards,
>>>
>>> Grant Rettke | ACM, ASA, FSF, IEEE, SIAM
>>> gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
>>> “Wisdom begins in wonder.” --Socrates
>>> ((λ (x) (x x)) (λ (x) (x x)))
>>> “Life has become immeasurably better since I have been forced to stop
>>> taking it seriously.” --Thompson
>>>

      reply	other threads:[~2014-08-04 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03 19:03 How to disable block evaluation results being wrapped with a single character like =? Grant Rettke
2014-08-04  0:24 ` Ista Zahn
2014-08-04 17:23   ` Grant Rettke
2014-08-04 17:36     ` Ista Zahn [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=CA+vqiLF_GKobyB1NOUkTHSaoRnfiGwDF_V5GOr4HrkUJRwmmHg@mail.gmail.com \
    --to=istazahn@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gcr@wisdomandwonder.com \
    /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).