From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Berry, Charles" Subject: Re: Problems with inline source blocks Date: Tue, 28 May 2019 16:39:01 +0000 Message-ID: <0705CEDA-C8C9-467A-9C6D-F21882DFEC8A@ucsd.edu> References: <94a31341b606bc671670ea5822c42fcee5d83bcc.camel@gladbachcity.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:56735) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hVfBi-00029d-Fe for Emacs-orgmode@gnu.org; Tue, 28 May 2019 12:42:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hVfBZ-0001AE-4U for Emacs-orgmode@gnu.org; Tue, 28 May 2019 12:42:53 -0400 Received: from iport-acv2-out.ucsd.edu ([132.239.0.174]:59624) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1hVfBJ-0008K9-CA for Emacs-orgmode@gnu.org; Tue, 28 May 2019 12:42:39 -0400 In-Reply-To: <94a31341b606bc671670ea5822c42fcee5d83bcc.camel@gladbachcity.de> Content-Language: en-US Content-ID: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Christian Heinrich Cc: "Emacs-orgmode@gnu.org" > On May 27, 2019, at 9:47 AM, Christian Heinrich wrote: >=20 > Hi everyone, >=20 > several issues with inline source blocks: None of the behavior you cite is in the current master as of 28-may-2019: 4a383ee0f19a001b272097398b43312fc0655798 >=20 > 1) https://orgmode.org/manual/Exporting-code-blocks.html states: >=20 >> The :exports header arguments control exporting code blocks only and >> not inline code: No mention of inline blocks in 14.6 Exporting Code Blocks. I guess that web= page needs to update or refers to something other than master. >=20 > but https://orgmode.org/manual/Using-Header-Arguments.html#Using-Header-A= rguments gives as example: >=20 >> src_haskell[:exports both]{fac 5} >=20 > Which one is true? >=20 As you can verify with your test, header args do affect inline src blocks. = I believe this is consistent with the current manual. > 2) I cannot get the results of inline blocks to be exported. >=20 > When I have a file that contains: >=20 >> Test: src_R[:exports results]{4*4} {{{results(=3D16=3D)}}} This worked for me when exporting to an ascii buffer. There were some problems starting with 5f5d82ed516b7b385a9258271becbfa247e9= 4af3, but these were fixed long ago. >=20 > then the code is always exported but the results are only exported up to > 623cc4625950f84442d4cde0faa9cc3ea0233283 >=20 > but starting from 65ebb128bc380fe4795dedd655d6f7b685249842 > the results macro is ignored and the result never appears. >=20 > Looking at online documentation (other projects) like=20 > https://org-babel.readthedocs.io/en/latest/eval/#inline-code-blocks I rea= lize that this may be a > problem in general (look at the Example sections, such as "The answer to = 2 + 3 is .") >=20 >=20 > 3) The source block never gets evaluated. I tried=20 > src_sh{touch /tmp/test21.txt} > but this file doesn't get created, only when I execute it directly. I ran this and it produced the file: src_sh{touch ~/test21.txt;echo "done"} Without the echo, export fails as touch produces no result. >=20 > Can anyone point out what I'm doing wrong, or is this actually a bug? I c= an't even get a basic > source block like >=20 > #+begin_src R :results output :session *R* :exports none > 5*5 > #+end_src >=20 > to ignore the code when exporting (but it's not evaluated). >=20 In my test, the code is evaluated in the session, but no results are report= ed. >=20 > Thanks! > Christian If I had to guess, I'd say there is something wrong with your installation. If you think otherwise, an ECM that runs with only a minimal init file (tha= t you specify) might be helpful. HTH, Chuck