From: Eric Schulte <schulte.eric@gmail.com>
To: Tassilo Horn <tsdh@gnu.org>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Bug: Exporter omits inline code blocks [8.0.3 (release_8.0.3-238-g172061 @ /home/horn/Repos/el/org-mode/lisp/)]
Date: Thu, 13 Jun 2013 07:06:20 -0600 [thread overview]
Message-ID: <87obbadoqj.fsf@gmail.com> (raw)
In-Reply-To: 87sj0mib0w.fsf@thinkpad.tsdh.de
Tassilo Horn <tsdh@gnu.org> writes:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> There's no bug. Babel simply removes all inline source blocks when
>> executing source blocks. Hence, they cannot be parsed (and therefore
>> exported).
>>
>> This function is just a placeholder for now.
>
> Aha. I've used source blocks only for the markup especially when
> exporting until now. And the manual states that inline code blocks are
> not different to normal code blocks, just being inline. So that's at
> least unexpected behavior, and the manual should be updated accordingly.
>
They are treated just like code blocks, however they have different
default header arguments.
,----[org-babel-default-inline-header-args]
| org-babel-default-inline-header-args is a variable defined in `ob-core.el'.
| Its value is ((:session . "none")
| (:results . "replace")
| (:exports . "results"))
|
|
| Documentation:
| Default arguments to use when evaluating an inline source block.
|
| [back]
`----
If you'd like to propose a patch to the manual which makes this clear,
I'm happy to apply it.
Thanks,
>
> Bye,
> Tassilo
>
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-06-13 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 6:24 Bug: Exporter omits inline code blocks [8.0.3 (release_8.0.3-238-g172061 @ /home/horn/Repos/el/org-mode/lisp/)] Tassilo Horn
2013-06-13 8:50 ` Nicolas Goaziou
2013-06-13 10:02 ` Tassilo Horn
2013-06-13 13:06 ` Eric Schulte [this message]
2013-06-14 7:26 ` Tassilo Horn
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=87obbadoqj.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=tsdh@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).