From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric Schulte" Subject: Re: [babel] features request for Emacs Initialization Date: Fri, 04 Dec 2009 22:33:31 -0700 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NGnH3-0003Vn-Nm for emacs-orgmode@gnu.org; Sat, 05 Dec 2009 00:33:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NGnGy-0003Ry-HU for emacs-orgmode@gnu.org; Sat, 05 Dec 2009 00:33:41 -0500 Received: from [199.232.76.173] (port=46675 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NGnGy-0003Rv-CP for emacs-orgmode@gnu.org; Sat, 05 Dec 2009 00:33:36 -0500 Received: from mail-pz0-f181.google.com ([209.85.222.181]:59247) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NGnGy-0007y3-IC for emacs-orgmode@gnu.org; Sat, 05 Dec 2009 00:33:36 -0500 Received: by pzk11 with SMTP id 11so2825012pzk.14 for ; Fri, 04 Dec 2009 21:33:35 -0800 (PST) In-Reply-To: (bluedian@gmail.com's message of "Tue, 1 Dec 2009 08:19:22 +0000 (UTC)") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: bluedian Cc: emacs-orgmode@gnu.org bluedian 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