From: Grant Rettke <gcr@wisdomandwonder.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Evaluating inline source blocks on export issue
Date: Wed, 23 Jul 2014 08:20:07 -0500 [thread overview]
Message-ID: <CAAjq1me5Yz4Mb=CDEbtYiUSd_W9HN8mad3OB97wcvoEKK0ZW5A@mail.gmail.com> (raw)
In-Reply-To: <87sils9rf7.fsf@gmail.com>
Thanks for looking Thomas and Nick.
When I set this and export
,----
| (setq org-export-babel-evaluate t)
`----
I get the expected result of
,----
| Here is a `16', stuck in the middle of some prose.
`----
But when I do this and export
,----
| (setq org-export-babel-evaluate 'inline-only)
`----
I get this output which is not what I expected
,----
| Here is a , stuck in the middle of some prose.
`----
I thought that I was enabling inline code block execution correctly
and making the inline call correctly.
How does it look should it be doing what I had wanted?
I have not yet begun trimming down my org initialization, and trying
to decide when I need to start narrowing things down by deduction.
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 Wed, Jul 23, 2014 at 7:43 AM, Nick Dokos <ndokos@gmail.com> wrote:
> Grant Rettke <gcr@wisdomandwonder.com> writes:
>
>> Good evening,
>>
>> From [org-scraps] I pasted this example into a buffer:
>>
>> ,—-
>> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>>
>> #+name: square
>> #+begin_src emacs-lisp :var it=0
>>
>> (* it it)
>> #+end_src
>>
>> Here is a call_square(it=4), stuck in the middle of some prose.
>> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>> `—-
>>
>> When I export the buffer I get:
>>
>> ,—-
>> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>> ╭────
>> │ (* it it)
>> ╰────
>>
>> Here is a , stuck in the middle of some prose.
>> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>> `—-
>>
>> I expected a 16 to have appeared there.
>>
>
> The following works for me:
>
> --8<---------------cut here---------------start------------->8---
> #+name: square
> #+begin_src emacs-lisp :var it=0 :exports none
> (* it it)
> #+end_src
>
> Here is a call_square(it=4), stuck in the middle of some prose.
> --8<---------------cut here---------------end--------------->8---
>
> --
> Nick
>
>
next prev parent reply other threads:[~2014-07-23 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 1:50 Evaluating inline source blocks on export issue Grant Rettke
2014-07-23 2:39 ` Thomas S. Dye
2014-07-23 12:43 ` Nick Dokos
2014-07-23 13:20 ` Grant Rettke [this message]
2014-07-24 1:24 ` Nick Dokos
2014-07-24 10:14 ` Andreas Leha
2014-07-25 1:53 ` Ista Zahn
2014-07-25 18:01 ` Grant Rettke
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='CAAjq1me5Yz4Mb=CDEbtYiUSd_W9HN8mad3OB97wcvoEKK0ZW5A@mail.gmail.com' \
--to=gcr@wisdomandwonder.com \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.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).