From: "Eric Schulte" <schulte.eric@gmail.com>
To: bluedian <bluedian@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] features request for Emacs Initialization
Date: Fri, 04 Dec 2009 22:33:31 -0700 [thread overview]
Message-ID: <m2bpiegf2s.fsf@gmail.com> (raw)
In-Reply-To: <loom.20091201T085124-655@post.gmane.org> (bluedian@gmail.com's message of "Tue, 1 Dec 2009 08:19:22 +0000 (UTC)")
bluedian <bluedian@gmail.com> writes:
> Hi,
>
> Thanks for org-babel, my configuration file are now in org form and it's pretty
> easy to manage and document them. I was looking for that kind of things since a
> long time !
>
> I will find interesting to have two more things (perhaps it's already there) :
>
> 1) When the org configuration file aren't changed, a way to automatically load
> their tangled version (bytecompiled ?) in order to improve the initialization
> time of Emacs.
>
Hmm, maybe we should byte-compile elisp files by default when they are
tangled out of org-babel documents. Although I can't think of any off
the top of my head I image there are going to be cases when it would not
be appropriate to byte-compile tangled elisp files.
I'll add this feature as a task in our development list.
>
> 2) When in debugging mode (a variable, like "stater-kit-org-babel-debug-lisp put
> to t), could a trace be generated by the tangling process in order to trace the
> execution of the configuration file (simple trace like the generation of a
> message at the start and end of each emacs lisp block). That could be a good
> help for rapidly finding an error.
>
Hmm, I feel like this would require too much code in org-babel for too
limited a set of functionality. Maybe there is a more general feature
lying behind this request that would be more widely applicable?
Thanks for the suggestions -- Eric
next prev parent reply other threads:[~2009-12-05 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 8:19 [babel] features request for Emacs Initialization bluedian
2009-12-05 5:33 ` Eric Schulte [this message]
2009-12-07 7:31 ` bluedian
2009-12-07 16:06 ` Jonathan Arkell
2009-12-08 8:28 ` Sébastien Vauban
2009-12-08 17:18 ` Jonathan Arkell
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=m2bpiegf2s.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=bluedian@gmail.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).