From: tsd@tsdye.com (Thomas S. Dye)
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: org-babel-tangle-file not parsing code blocks
Date: Mon, 25 Mar 2013 14:58:47 -1000 [thread overview]
Message-ID: <m1d2unkmd4.fsf@poto.myhome.westell.com> (raw)
In-Reply-To: <CACHMzOEpBeL4j_8g7BgtNBgj7N1U3LP-79DQr9MzAit9mtMGBw@mail.gmail.com> (Marcelo de Moraes Serpa's message of "Mon, 25 Mar 2013 17:48:35 -0600")
Aloha Marcelo,
Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
> I still don't understand why the TARGET_FILE argument is optional. I would
> expect it to create a file of the same name of the org file that is
> tangled.
Here is the docstring:
(org-babel-tangle-file FILE &optional TARGET-FILE LANG)
Extract the bodies of source code blocks in FILE.
Source code blocks are extracted with `org-babel-tangle'.
Optional argument TARGET-FILE can be used to specify a default
export file for all source blocks. Optional argument LANG can be
used to limit the exported source code blocks by language.
I suppose it is optional so you don't have to specify a default export
file for all source blocks. What if you want to tangle two or more
files from the same Org buffer?
> Take this code:
>
> (org-babel-tangle-file "~/.emacs.d/config/peepopen-config.org")
>
> Contents:
>
> * Load it
>> #+BEGIN_SRC emacs-lisp
>> (add-to-list 'load-path (concat fullofcaffeine-vendor-dir "/peepopen"))
>> (require 'peepopen)
>> (textmate-mode)
>> (provide 'peepopenconfig)
>> #+END_SRC
>
>
> When I evaluate the (org-babel-tangle-file...) line, I get the following:
>
> Tangled 0 code blocks from peepopen-config.org
Well, by default :tangle no, so unless you've changed this somewhere I
think Babel will defer to the default value.
hth,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
prev parent reply other threads:[~2013-03-26 0:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 22:02 org-babel-tangle-file not parsing code blocks Marcelo de Moraes Serpa
2013-03-25 22:03 ` Marcelo de Moraes Serpa
2013-03-25 22:19 ` Thomas S. Dye
2013-03-25 22:20 ` Marcelo de Moraes Serpa
2013-03-25 22:45 ` Marcelo de Moraes Serpa
2013-03-25 23:24 ` Marcelo de Moraes Serpa
2013-03-25 23:39 ` Thomas S. Dye
2013-03-25 23:48 ` Marcelo de Moraes Serpa
2013-03-26 0:58 ` Thomas S. Dye [this message]
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=m1d2unkmd4.fsf@poto.myhome.westell.com \
--to=tsd@tsdye.com \
--cc=celoserpa@gmail.com \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).