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

From: Rainer M Krug <Rainer@krugs.de>
To: Charles Berry <ccberry@ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Tangling from code block and header arguments WAS: Format output of org-babel-tangle for exported file
Date: Wed, 03 Sep 2014 17:46:04 +0200	[thread overview]
Message-ID: <m2lhq0g11f.fsf_-_@krugs.de> (raw)
In-Reply-To: <loom.20140903T161501-167@post.gmane.org> (Charles Berry's message of "Wed, 3 Sep 2014 14:19:19 +0000 (UTC)")

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

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

[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]

next prev parent reply	other threads:[~2014-09-03 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03 13:08 Format output of org-babel-tangle for exported file Rainer M Krug
2014-09-03 13:30 ` Rainer M Krug
2014-09-03 14:19 ` Charles Berry
2014-09-03 15:46   ` Rainer M Krug [this message]
2014-09-03 16:56     ` Tangling from code block and header arguments WAS: " Charles C. Berry

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=m2lhq0g11f.fsf_-_@krugs.de \
    --to=rainer@krugs.de \
    --cc=ccberry@ucsd.edu \
    --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).