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:24:50 -0600	[thread overview]
Message-ID: <CACHMzOFCJ34R+i5gVZrJRsjHx-4jP=U3Hxpt7Ux8SazfsMRXkw@mail.gmail.com> (raw)
In-Reply-To: <CACHMzOF6tF8eK-4VOLykOKgxcyxTMZUcb_hByvDKH-kegjgciQ@mail.gmail.com>

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

Perhaps I'm misunderstanding how org-babel-tangle-file works. Isn't it
supposed to create a correspondent .el file for the tangled org file?


On Mon, Mar 25, 2013 at 4:45 PM, Marcelo de Moraes Serpa <
celoserpa@gmail.com> wrote:

> 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?
>
> Thanks!
>
>
> On Mon, Mar 25, 2013 at 4:20 PM, Marcelo de Moraes Serpa <
> celoserpa@gmail.com> wrote:
>
>> Hi Thomas,
>>
>> Stupid me. There was a syntax error in the code block -- "emacs_lisp"
>> instead of "emacs-lisp".
>>
>> Thank you for taking your time to answer it, though!
>>
>> - Marcelo.
>>
>>
>> On Mon, Mar 25, 2013 at 4:19 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
>>
>>> Aloha Marcelo,
>>>
>>> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
>>>
>>> > Hi list,
>>> >
>>> > I have a simple babel file with an Emacs Lisp code block, that looks
>>> like
>>> > this:
>>> >
>>> > peepopen-config.org:
>>> >
>>> >
>>> > * Load it
>>> > #+BEGIN_SRC emacs_lisp
>>> >   (add-to-list 'load-path (concat fullofcaffeine-vendor-dir
>>> "/peepopen"))
>>> >   (require 'peepopen)
>>> >   (textmate-mode)
>>> > #+END_SRC
>>> >
>>> > (provide 'peepopen-config)
>>> >
>>> >
>>> > I'm trying to tangle it with (org-babel-tangle-file "
>>> peepopen-config.org"),
>>> > but I get the following in the "Messages" buffer:
>>> >
>>> > Tangled 0 code blocks from peepopen-config.org
>>> >
>>> >
>>> > I'm confused, since the file *does* contain a code block. Am I doing
>>> > something wrong?
>>>
>>> Not really, but you do need to tell Babel you want to tangle this code
>>> block.  See the header argument :tangle, which by default is set to
>>> `no'.  If you add :tangle yes to the code block header, then it should
>>> do what you want.
>>>
>>> hth,
>>> Tom
>>>
>>> >
>>> > Thanks in advance,
>>> >
>>> > - Marcelo.
>>> > Hi list,
>>> >
>>> >
>>> > I have a simple babel file with an Emacs Lisp code block, that looks
>>> > like this:
>>> >
>>> > peepopen-config.org:
>>> >
>>> >
>>> >     * Load it
>>> >     #+BEGIN_SRC emacs_lisp
>>> >       (add-to-list 'load-path (concat fullofcaffeine-vendor-dir
>>> >     "/peepopen"))
>>> >       (require 'peepopen)
>>> >       (textmate-mode)
>>> >     #+END_SRC
>>> >
>>> >     (provide 'peepopen-config)
>>> >
>>> >
>>> > I'm trying to tangle it with (org-babel-tangle-file
>>> > "peepopen-config.org"), but I get the following in the "Messages"
>>> > buffer:
>>> >
>>> >     Tangled 0 code blocks from peepopen-config.org
>>> >
>>> >
>>> > I'm confused, since the file *does* contain a code block. Am I doing
>>> > something wrong?
>>> >
>>> > Thanks in advance,
>>> >
>>> > - Marcelo.
>>> >
>>> >
>>> >
>>>
>>> --
>>> Thomas S. Dye
>>> http://www.tsdye.com
>>>
>>
>>
>

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

  reply	other threads:[~2013-03-25 23:24 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 [this message]
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

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='CACHMzOFCJ34R+i5gVZrJRsjHx-4jP=U3Hxpt7Ux8SazfsMRXkw@mail.gmail.com' \
    --to=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.com \
    /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).