emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: bluedian <bluedian@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [babel] features request for Emacs Initialization
Date: Tue, 1 Dec 2009 08:19:22 +0000 (UTC)	[thread overview]
Message-ID: <loom.20091201T085124-655@post.gmane.org> (raw)

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.

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.

For instance, the code block :
  #+srcname: Name_Code_Block
  #+begin_src emacs-lisp 
   ;; code lisp ....  
   (desktop-save-mode 1) ;; for instance
  #+end_src

could be tangled in something like  

  ;; generated by org-babel-tangle
  ;; [[file:~/TEST.org::*foo][foo]]
  (message "starting Name_Code_Block")
  ;; code lisp ....  
  (desktop-save-mode 1) ;; for instance
  (message "ending Name_Code_Block")
  ;; foo ends here

Regards,
BlueDian

next             reply	other threads:[~2009-12-01  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01  8:19 bluedian [this message]
2009-12-05  5:33 ` [babel] features request for Emacs Initialization Eric Schulte
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=loom.20091201T085124-655@post.gmane.org \
    --to=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

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