[O] org-babel-tangle-file not parsing code blocks

2013-03-25 Thread Marcelo de Moraes Serpa
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.


Re: [O] org-babel-tangle-file not parsing code blocks

2013-03-25 Thread Marcelo de Moraes Serpa
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 
celose...@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.






Re: [O] org-babel-tangle-file not parsing code blocks

2013-03-25 Thread Thomas S. Dye
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



Re: [O] org-babel-tangle-file not parsing code blocks

2013-03-25 Thread Marcelo de Moraes Serpa
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



Re: [O] org-babel-tangle-file not parsing code blocks

2013-03-25 Thread Marcelo de Moraes Serpa
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 
celose...@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 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





Re: [O] org-babel-tangle-file not parsing code blocks

2013-03-25 Thread Marcelo de Moraes Serpa
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 
celose...@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 
 celose...@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 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






Re: [O] org-babel-tangle-file not parsing code blocks

2013-03-25 Thread Marcelo de Moraes Serpa
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)

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


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 ?

Cheers!

- Marcelo.

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

 Aloha Marcelo,

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



Re: [O] org-babel-tangle-file not parsing code blocks

2013-03-25 Thread Thomas S. Dye
Aloha Marcelo,

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



Re: [O] org-babel-tangle-file not parsing code blocks

2013-03-25 Thread Thomas S. Dye
Aloha Marcelo,

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