0

考虑以下 org-mode 中的 MVE——它详细包含了我的完整问题。但是，总而言之，对于一些代码块，当我导出文档时，一些对其他代码块的 noweb 引用被内联替换，并且对于其他代码块，noweb 引用，在双引号中，被逐字复制到导出的 PDF 中。我不知道是什么导致了这种行为差异，我不知道如何控制它，但我想。我希望能够指定某些块具有行为 1（替换引用），而其他块具有行为 2（逐字引用）。

由此产生的PDForg-export位于此链接

#+BEGIN_COMMENT
The emacs lisp block must export results, even though the results are none,
otherwise the block will not be eval'ed on export, and we will get 
unacceptable confirmation requests for all the subsequent python blocks. 
#+END_COMMENT

#+BEGIN_SRC emacs-lisp :exports results :results none
(setq org-confirm-babel-evaluate nil)
#+END_SRC

** PyTests

   Define the test and cases. This code must be tangled out to an external file
   so =py.test= can see it.

   When I /export/ this to PDF, the noweb references, namely =<<imports>>= and
   =<<definitions>>=, are substituted inline, so the typeset version of this
   block in the PDF shows ALL the code.  This is not what I want.

#+NAME: test-block
#+BEGIN_SRC python :noweb yes :tangle test_foo.py 
<<imports>>
<<definitions>>
def test_smoke ():
    np.testing.assert_approx_equal (foo_func (), foo_constant)
#+END_SRC

#+RESULTS: test-block
: None

   The following blocks import prerequisites and do a quick smoke test:

** Do Some Imports

#+NAME: imports
#+BEGIN_SRC python 
import numpy as np
#+END_SRC

#+RESULTS: imports
: None

** Define Some Variables

   However, in the typeset PDF, the noweb reference =<<foo-func>>= in the block
   below is /not/ substituted in-line, but rather appears verbatim. I want /all/
   noweb references to appear verbatim in the exported, typeset, PDF document,
   just like this one.

#+NAME: definitions
#+BEGIN_SRC python 
foo_constant = 42.0
<<foo-func>>
#+END_SRC

#+RESULTS: definitions

** Define Some Functions

*** Foo Function is Really Interesting

#+NAME: foo-func
#+BEGIN_SRC python
def foo_func () :
    return 42.000
#+END_SRC

#+RESULTS: foo-func
: None

We want results from pytest whether it succeeds or fails, hence the /OR/ with
=true= in the shell

#+BEGIN_SRC sh :results output replace :exports both
py.test || true
#+END_SRC

#+RESULTS:
: ============================= test session starts ==============================
: platform darwin -- Python 2.7.10, pytest-2.8.0, py-1.4.30, pluggy-0.3.1
: rootdir: /Users/bbeckman/foo, inifile: 
: collected 1 items
: 
: test_foo.py .
: 
: =========================== 1 passed in 0.06 seconds ===========================
4

1 回答 1

-1

在此处找到适当的参考资料

这是从以下 .org 文件导出的更正 PDF。

这是更正后的 MVE（它本身解释了更正）：

#+BEGIN_COMMENT
The emacs lisp block must export results, even though the exports are none,
otherwise the block will not be eval'ed on export, and we will get unacceptable
confirmation requests for all the subsequent python blocks.
#+END_COMMENT

#+BEGIN_SRC emacs-lisp :exports results :results none
  (setq org-confirm-babel-evaluate nil)
#+END_SRC

** PyTests

   Define the test and cases. This code must be tangled out to an external file
   so =py.test= can see it.

   When I /export/ this to PDF, the noweb references, namely =<<imports>>= and
   =<<definitions>>=, are *NOT* substituted inline, but typeset verbatim. This
   is what I want.  You get this behavior by saying =:noweb no-export= in the
   header.

#+NAME: test-block
#+BEGIN_SRC python :tangle test_foo.py :noweb no-export :exports code :results none
dummy_for_org_mode = True
<<imports>>
<<definitions>>
def test_smoke ():
    np.testing.assert_approx_equal (foo_func (), foo_constant)
#+END_SRC

   The following blocks import prerequisites and do a quick smoke test:

** Do Some Imports

#+NAME: imports 
#+BEGIN_SRC python :exports code :results none
  import numpy as np
#+END_SRC

** Define Some Variables and Functions

   In this block, I want the noweb reference =<<foo-func>>= in the block to be
   substituted in-line and not to appear verbatim. Do that by saying
   =:noweb yes= in the header.

#+NAME: definitions 
#+BEGIN_SRC python :noweb yes :exports code :results none
  foo_constant = 42.0
  <<foo-func>>
#+END_SRC

** Define Some Functions

*** Foo Function is Really Interesting

Here, I want to talk about the implementation of foo function in detail, but I
don't want its code to be exported again, just to appear in the original
=.org= file as I reminder or note to me.

#+NAME: foo-func 
#+BEGIN_SRC python :exports none :results none
  def foo_func () :
      return 42.000
#+END_SRC

** Run the Tests

We want results from pytest whether it succeeds or fails, hence the /OR/ with
=true= in the shell

#+BEGIN_SRC sh :results output replace :exports both
  py.test || true
#+END_SRC

#+RESULTS:
: ============================= test session starts ==============================
: platform darwin -- Python 2.7.10, pytest-2.8.0, py-1.4.30, pluggy-0.3.1
: rootdir: /Users/bbeckman/foo, inifile: 
: collected 1 items
: 
: test_foo.py .
: 
: =========================== 1 passed in 0.08 seconds ===========================
于 2015-09-28T04:37:55.470 回答