emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Richard Riley <rileyrgdev@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-babel and emacs init
Date: Tue, 26 Jan 2010 11:37:40 -0700	[thread overview]
Message-ID: <87fx5s7lvv.fsf@gmail.com> (raw)
In-Reply-To: <hjjljj$ukt$1@ger.gmane.org> (Richard Riley's message of "Mon, 25 Jan 2010 09:43:32 +0100")

Hi Richard,

Richard Riley <rileyrgdev@gmail.com> writes:

> What approach have you taken to loading multiple files using the
> org-babel method?
>
> The example on the babel page searches out all org files and then
> untangles the elisp snippets and rewrites files with a .el extensions
> loading them as it goes.
>
> But how to order  this or how best to load /decode/execute at run time
> in say an autoload or eval after load? Simply call org-babel-load-file
> instead of require? 
>

Currently the only option is `org-babel-load-file'.  Off the top of my
head I don't see why an analogous `org-babel-require' function would not
work, and it seems that it would satisfy this need for conditional
loading.

>
> e.g say I wanted to keep my (typically large) .gnus.el file as an org
> file. How best to deal with that? Currently I have an eval after load
> with all the code in that used to be in my .gnus.el in my
> emacs-init.org. Other approaches?
>

again, maybe using something like the eventually-to-be-implemented
org-babel-require would work here?

>
> Would there be a way to get the load system to check for an org file
> first and call org-babel-load-file?
>

I'm not sure exactly what you mean here.

>
> Should possibly writing the org file auto create the .el file? Or is
> that best left to load time?
>

I think this will be more reliable if it is left as a load-time
operation, rather than as a save-hook or something.  Also, since the
file is only re-tangled when the .org file is newer than the .el file it
should not be a noticeable startup performance hit.

Thanks -- Eric

>
> Any opinions or discussions/pointers appreciated.
>
> regards,
>
> r.
>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-01-26 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25  8:43 org-babel and emacs init Richard Riley
2010-01-26 18:37 ` Eric Schulte [this message]
2010-01-26 19:42   ` Richard Riley
  -- strict thread matches above, loose matches on Subject: below --
2010-06-28 17:22 Richard Riley
2010-06-28 17:59 ` Eric Schulte
     [not found]   ` <AANLkTimTQEewn_27FFEaOD1TAydhceiGrVcdLuEZSHfP@mail.gmail.com>
     [not found]     ` <87mxu9wcp9.fsf@gmail.com>
2010-07-16  2:11       ` Julien Fantin

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=87fx5s7lvv.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rileyrgdev@gmail.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).