From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric Schulte" Subject: Re: Re: [babel] Executing sh-code Date: Mon, 30 Nov 2009 09:16:28 -0700 Message-ID: References: <87k4xey99s.fsf@mundaneum.com> <200911271900.08393.torsten.wagner@googlemail.com> <87ws1cgsd6.fsf@mundaneum.com> <877htb4uow.fsf@stats.ox.ac.uk> <87638tnivd.fsf@mundaneum.com> <8164.1259596929@alphaville.usa.hp.com> 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 1NF8vG-0003Ty-VK for emacs-orgmode@gnu.org; Mon, 30 Nov 2009 11:16:22 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NF8vC-0003Ra-8u for emacs-orgmode@gnu.org; Mon, 30 Nov 2009 11:16:22 -0500 Received: from [199.232.76.173] (port=41488 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NF8vB-0003RM-TE for emacs-orgmode@gnu.org; Mon, 30 Nov 2009 11:16:18 -0500 Received: from mail-px0-f178.google.com ([209.85.216.178]:55164) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NF8vB-0003xb-HE for emacs-orgmode@gnu.org; Mon, 30 Nov 2009 11:16:17 -0500 Received: by pxi8 with SMTP id 8so2790078pxi.27 for ; Mon, 30 Nov 2009 08:16:16 -0800 (PST) In-Reply-To: <8164.1259596929@alphaville.usa.hp.com> (Nick Dokos's message of "Mon, 30 Nov 2009 11:02:09 -0500") 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: nicholas.dokos@hp.com Cc: Org Mode Nick Dokos writes: > > There are two methods that I use that I think are much more effective > than sprinkling message calls all over the place: > > o edebug-defun: (in emacs-lisp mode, C-u C-M-x) will mark the > function so that when it is called, the interpreter stops and you can then > single-step through it with . At each point, you can > press "e" and evaluate variables (actually arbitrary expressions). > > o Insert a strategically placed (debug) call and then call the function. > If/when the debug call is executed, you are dropped into the debugger > and you can then evaluate arbitrary expressions. > Excellent. Thanks Nick, I look forward to the next bug so I can try these out. -- Eric > > HTH, > Nick