From: tsd@tsdye.com (Thomas S. Dye)
To: Grant Rettke <gcr@wisdomandwonder.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Evaluating inline source blocks on export issue
Date: Tue, 22 Jul 2014 16:39:08 -1000 [thread overview]
Message-ID: <m261ioyf1v.fsf@tsdye.com> (raw)
In-Reply-To: <CAAjq1mccX63z-xjFbWjWUAmqQv34354FUXav-mYo7YRx7TbiTw@mail.gmail.com> (Grant Rettke's message of "Tue, 22 Jul 2014 20:50:46 -0500")
Aloha Grant,
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)
> ╰────
To get rid of the source code block in the export buffer, you can put it
under a heading that is tagged with :noexport:. I keep a heading at the
end of most documents to hold source code blocks and find it convenient.
>
> Here is a , stuck in the middle of some prose.
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> `—-
I'm not certain if this will fix your problem (untested), but I set
:results raw in this situation. I use properties for this so the
call_foo() part stays a reasonable length:
* Description of the Hawaiian Stone Axes
:PROPERTIES:
:RESULTS: raw
:END:
hth,
Tom
>
> I expected a 16 to have appeared there.
>
> I did double check that inline call blocks work on export:
>
> ╭────
> │ (list org-export-babel-evaluate)
> ╰────
>
> #+NAME:
> | inline-only |
>
> Clearly I am missing something.
>
> What am I doing wrong here?
>
> My environment:
>
> ╭────
> │ (format "%S" (emacs-version))
> ╰────
>
> #+NAME:
> #+begin_example
> "GNU Emacs 24.3.1 (x86_64-apple-darwin13.2.0, Carbon Version 1.6.0
> AppKit 1265.2)
> of 2014-07-03 on orion"
> #+end_example
>
> ╭────
> │ (format "%S" (org-version))
> ╰────
>
> #+NAME:
> #+begin_example
> "8.2.7a"
> #+end_example
>
> Kind regards,
>
> gcr
>
>
> [org-scraps]
> https://raw.githubusercontent.com/eschulte/org-scraps/master/scraps.org
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2014-07-23 2:39 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 [this message]
2014-07-23 12:43 ` Nick Dokos
2014-07-23 13:20 ` Grant Rettke
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=m261ioyf1v.fsf@tsdye.com \
--to=tsd@tsdye.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).