serted:
#+results: the_issue()
nil
I am currently running a2f29de86.
Thanks
Mark Cox
Hi,
Is it possible for the output of the expansion of a code block to
appear in the exported document?
Consider the example:
#+TITLE: No expansion of noweb references when exporting
* Example
:PROPERTIES:
:tangle: illustration.hpp
:END:
#+srcname: boiler-plate-code-generator()
#+begin_src emacs
Hi,
When tangling lisp source code blocks, the tangled code is wrapped in
a `(progn ,@body). For example,
the block
#+begin_src lisp :tangle example.lisp
(defun mischief ()
(/ 1 0))
#+end_src
produces
: (progn (defun mischief ()
: (/ 1 0))
: )
With the attached patch, the tangling process now
Hi,
This may be contentious and break backward compatibility for some people.
Currently, relative pathnames in Common Lisp source blocks are
meaningless as the *default-pathname-defaults* symbol is set to
whatever the value is when SLIME was invoked. This behaviour is
contrary to the shell source