From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Some Experiences with org-babel-load-file
Date: Tue, 11 Dec 2012 17:01:03 +0000 (UTC) [thread overview]
Message-ID: <876248eehe.fsf@mean.albasani.net> (raw)
In-Reply-To: 50C66343.2010202@miszellen.de
Florian Beck <fb@miszellen.de> writes:
> 1. `org-babel-load-file' doesn't seem to be in the org docu. The
> instructions on worg are obsolete (mentions `org-install') and
> needlessly complicated. Just putting
>
> (package-initialize) ;; only if you use the newest org
... and the newest emacs!
> (require 'ob-tangle)
> (org-babel-load-file "/path/to/your/org-init-file.org")
>
> into your .emacs (no need for .emacs.d/init.el) seems to suffice.
This is one way to do it, not necessarily the only way.
I don't think a 4 line init.el is that complicated ;).
> 4. When I babel-load "my-package.org", all emacs sees is the tangled
> "my-package.el", which of course is right. The problem, however, is
> that I often search for one of my functions, change it … and loose the
> changes the next time I start emacs (I already got zapped a couple of
> times). Integrating org-tangle with the emacs documentation would be
> tough I guess. But how about setting a read-only file locale variable
> to block the most stupid mistakes?
How do you change your functions?
If I want to do it, I tinker with them directly in my emacs.org and
evaluate from there or copy the relevant bits to the *scratch* buffer
and bring them back to emacs.org once it works. If the file changed,
the el file gets tangled fresh automatically next time I start emacs and
used right away.
I don't really see a problem?
Memnon
next prev parent reply other threads:[~2012-12-11 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 22:33 Some Experiences with org-babel-load-file Florian Beck
2012-12-11 14:52 ` Eric Schulte
2012-12-11 19:52 ` Florian Beck
2012-12-12 3:35 ` Eric Schulte
2012-12-11 17:01 ` Memnon Anon [this message]
2012-12-11 17:36 ` Jonathan Leech-Pepin
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=876248eehe.fsf@mean.albasani.net \
--to=gegendosenfleisch@googlemail.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 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).