Charles Berry <ccberry@ucsd.edu> writes:

> Rainer M Krug <Rainer <at> krugs.de> writes:
>
>> 
>> Hi
>> 
>> I am calling (org-bable-tangle) in a code block in an org file and I
>> would show the files resulting from the tangling in a nice format.
>> 
>> But I do not manage. I have the following at the moment:
>> 
>> --8<---------------cut here---------------start------------->8---
>> #+begin_src emacs-lisp 
>> (replace-regexp-in-string "[)\"]" ""
>>      (replace-regexp-in-string "[(]" "- "
>>           (replace-regexp-in-string " " "\n- "
>>                (prin1-to-string (org-babel-tangle)))))
>> #+end_src
>> 
>
> [snip]
>
>> Which is neither elegant nor short, and I am sure I could do this
>> easier. Any suggestions?
>
> Something like this? Possibly with `(reverse (org-babel-tangle))'
>
> #+BEGIN_SRC emacs-lisp :results value
> (mapconcat (lambda (x) (file-relative-name x "..")) (org-babel-tangle) "\n")
> #+END_SRC

Thanks - this looks promising.

But I now have another problem: The result of tangling from a code block
is different then when calling interactively.

Consider the following org file:

--8<---------------cut here---------------start------------->8---
#+PROPERTY: header-args :tangle no

* DESCRIPTION File
:PROPERTIES:
:header-args+: :tangle ./DESCRIPTION
:END:

#+begin_src RDescr
test
#+end_src

* And the tangling
#+BEGIN_SRC emacs-lisp :results value
(mapconcat (lambda (x) (file-relative-name x "..")) (org-babel-tangle) "\n")
#+END_SRC

#+RESULTS:

--8<---------------cut here---------------end--------------->8---

When tangling interactively, the file DESCRIPTION is tangled properly.
But when I call (org-babel-tangle) from the code block, nothing is
tangled because in this case, the property =tangle= is equal to =no=
based on the file wide property setting in the beginning.

Is this a bug or is it simply not possible to tangle from a code block?

Thanks,

Rainer

>
>
> HTH,
>
> Chuck
>
>
>
>

-- 
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982