emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Christian Heinrich <com-orgmode-mailinglist@gladbachcity.de>
To: Emacs-orgmode@gnu.org
Subject: Problems with inline source blocks
Date: Mon, 27 May 2019 18:47:27 +0200	[thread overview]
Message-ID: <94a31341b606bc671670ea5822c42fcee5d83bcc.camel@gladbachcity.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]

Hi everyone,

several issues with inline source blocks:

1) https://orgmode.org/manual/Exporting-code-blocks.html states:

> The :exports header arguments control exporting code blocks only and
> not inline code:

but https://orgmode.org/manual/Using-Header-Arguments.html#Using-Header-Arguments gives as example:

> src_haskell[:exports both]{fac 5}

Which one is true?

2) I cannot get the results of inline blocks to be exported.

When I have a file that contains:

> Test: src_R[:exports results]{4*4} {{{results(=16=)}}}

then the code is always exported but the results are only exported up to
623cc4625950f84442d4cde0faa9cc3ea0233283

but starting from 65ebb128bc380fe4795dedd655d6f7b685249842
the results macro is ignored and the result never appears.

Looking at online documentation (other projects) like 
https://org-babel.readthedocs.io/en/latest/eval/#inline-code-blocks I realize that this may be a
problem in general (look at the Example sections, such as "The answer to 2 + 3 is .")


3) The source block never gets evaluated. I tried 
src_sh{touch /tmp/test21.txt}

but this file doesn't get created, only when I execute it directly.

Can anyone point out what I'm doing wrong, or is this actually a bug? I can't even get a basic
source block like

#+begin_src R :results output :session *R* :exports none
5*5
#+end_src

to ignore the code when exporting (but it's not evaluated).


Thanks!
Christian

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

next             reply	other threads:[~2019-05-27 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 16:47 Christian Heinrich [this message]
2019-05-28 16:39 ` Problems with inline source blocks Berry, Charles
2019-05-29  2:05   ` Outdated manual web pages left in place WAS: " Berry, Charles

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=94a31341b606bc671670ea5822c42fcee5d83bcc.camel@gladbachcity.de \
    --to=com-orgmode-mailinglist@gladbachcity.de \
    --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

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).