From mboxrd@z Thu Jan 1 00:00:00 1970 From: bluedian Subject: Re: [babel] features request for Emacs Initialization Date: Mon, 7 Dec 2009 07:31:34 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NHY4k-0006rb-Eu for emacs-orgmode@gnu.org; Mon, 07 Dec 2009 02:32:06 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NHY4e-0006qw-TE for emacs-orgmode@gnu.org; Mon, 07 Dec 2009 02:32:05 -0500 Received: from [199.232.76.173] (port=37088 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NHY4e-0006qt-PT for emacs-orgmode@gnu.org; Mon, 07 Dec 2009 02:32:00 -0500 Received: from lo.gmane.org ([80.91.229.12]:40732) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NHY4e-0007lt-Kd for emacs-orgmode@gnu.org; Mon, 07 Dec 2009 02:32:00 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NHY4b-0003jO-1T for emacs-orgmode@gnu.org; Mon, 07 Dec 2009 08:31:57 +0100 Received: from ram49-2-88-168-184-167.fbx.proxad.net ([88.168.184.167]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Dec 2009 08:31:57 +0100 Received: from blue.dian by ram49-2-88-168-184-167.fbx.proxad.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Dec 2009 08:31:57 +0100 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: emacs-orgmode@gnu.org Thanks for your reply. Eric Schulte gmail.com> writes: > > 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? I understand. For now, I use this basic snippet when defining emacs code block in my configuration files, JDL-Debug is a flag I put to true when I want to debug my Emacs configuration. # -*- mode: snippet -*- # name: code org for emacs configuration blocks # key: cemacs # -- #+srcname: $1 #+begin_src emacs-lisp (if JDL-Debug (message "start $1")) $2 (if JDL-Debug (message "End $1")) #+end_src