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 <t...@tsdye.com> wrote:

> Aloha Marcelo,
>
> Marcelo de Moraes Serpa <celose...@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
>

Reply via email to