From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: org-babel-tangle-file not parsing code blocks
Date: Mon, 25 Mar 2013 16:03:47 -0600 [thread overview]
Message-ID: <CACHMzOHXb-2rqWDqQEeab-qQshPsrGE4W-jCkiUWWvnnTQBwOQ@mail.gmail.com> (raw)
In-Reply-To: <CACHMzOH3=RX5CTgNKHuvNkrwxp4piPPo34Bbo+O1o7cZdK+U5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
Versions:
Org-mode version 8.0-pre (release_8.0-pre-186-g8aeea9.dirty)
GNU Emacs 24.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of
2013-03-12
On Mon, Mar 25, 2013 at 4:02 PM, Marcelo de Moraes Serpa <
celoserpa@gmail.com> wrote:
> 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.
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1850 bytes --]
next prev parent reply other threads:[~2013-03-25 22:03 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACHMzOHXb-2rqWDqQEeab-qQshPsrGE4W-jCkiUWWvnnTQBwOQ@mail.gmail.com \
--to=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.