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