emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: org-babel-tangle-file not parsing code blocks
Date: Mon, 25 Mar 2013 17:48:35 -0600	[thread overview]
Message-ID: <CACHMzOEpBeL4j_8g7BgtNBgj7N1U3LP-79DQr9MzAit9mtMGBw@mail.gmail.com> (raw)
In-Reply-To: <m1hajzkq1x.fsf@poto.myhome.westell.com>

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

Hi Thomas. Thanks again for the reply.

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. Take this code:

(org-babel-tangle-file "~/.emacs.d/config/peepopen-config.org")


* Load it
> #+BEGIN_SRC emacs-lisp
>   (add-to-list 'load-path (concat fullofcaffeine-vendor-dir "/peepopen"))
>   (require 'peepopen)
>   (textmate-mode)
> (provide 'peepopenconfig)

When I evaluate the (org-babel-tangle-file...) line, I get the following:

Tangled 0 code blocks from peepopen-config.org

I would expect it to tangle 1 block, and create a peepopen-config.el (no
need to define a TARGET_FILE string).

Two questions:

1) Not sure why it's not tangling the BEGIN_SRC emacs-lisp block
2) Am I wrong about the .el file creation assumption ?


- Marcelo.

On Mon, Mar 25, 2013 at 5:39 PM, Thomas S. Dye <tsd@tsdye.com> wrote:

> Aloha Marcelo,
> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
> > Oh, actually that wasn't the issue.
> >
> > org-babel-load-file seems to force tangling the file to an .el.
> > org-babel-tangle-file doesn't. Is there a way to force the output to the
> > .el file without using the parameter in the code block itself?
> >
> Yes, there is.
> (org-babel-tangle-file FILE &optional TARGET-FILE LANG)
> You should be able set TARGET-FILE with a buffer-wide header argument,
> like this:
> #+PROPERTY: tangle force-output-to-the.el
> 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

[-- Attachment #2: Type: text/html, Size: 3033 bytes --]

  reply	other threads:[~2013-03-25 23:48 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 [this message]
2013-03-26  0:58           ` Thomas S. Dye

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:

  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=CACHMzOEpBeL4j_8g7BgtNBgj7N1U3LP-79DQr9MzAit9mtMGBw@mail.gmail.com \
    --to=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.com \


* 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


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).