From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Will Monroe Newsgroups: gmane.emacs.help Subject: Re: Advice on troubleshooting function to "unscroll" Date: Sun, 25 Jan 2015 16:01:35 -0600 Message-ID: <54C567BF.7020302@gmail.com> References: <54C5577D.4030700@gmail.com> <874mreh7c5.fsf@wmi.amu.edu.pl> <54C56398.1050404@gmail.com> <87zj96frux.fsf@wmi.amu.edu.pl> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1422223314 4231 80.91.229.3 (25 Jan 2015 22:01:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 25 Jan 2015 22:01:54 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Jan 25 23:01:54 2015 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YFVFg-0004sl-8Z for geh-help-gnu-emacs@m.gmane.org; Sun, 25 Jan 2015 23:01:52 +0100 Original-Received: from localhost ([::1]:39091 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YFVFf-0004gq-K5 for geh-help-gnu-emacs@m.gmane.org; Sun, 25 Jan 2015 17:01:51 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52980) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YFVFT-0004gl-Rv for help-gnu-emacs@gnu.org; Sun, 25 Jan 2015 17:01:40 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YFVFQ-0002UU-JY for help-gnu-emacs@gnu.org; Sun, 25 Jan 2015 17:01:39 -0500 Original-Received: from mail-oi0-x22d.google.com ([2607:f8b0:4003:c06::22d]:62338) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YFVFQ-0002UP-Eo for help-gnu-emacs@gnu.org; Sun, 25 Jan 2015 17:01:36 -0500 Original-Received: by mail-oi0-f45.google.com with SMTP id g201so4768848oib.4 for ; Sun, 25 Jan 2015 14:01:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=lc80zrvCFsgxKC/QzRmTyt5yqfSMODtvxrMckbNUoJM=; b=o3eWuhS13eAhrOR2xcdxNVYsq/KV/Fxmfh3dgRX/iN39abVLGXFVOhkXQTmbBEX5ym /hUU5fc2Lk0s4oSn7A0AXFMDPPADd6xZ9lW/ttGafBMHqLHArs5GhWg7B9CdwWql87O0 s2yrKXV329CYh9pZNxVG27CG9+ooyztbsI36BplDWf+RoqLhobln+QDafhif6eX0rzI9 v/R48F+vS59usG9Cw3I5Lmbs3MQAekARmFVvm5eNO8M6gNX7blB4H47PPDcKCeuFl0Be nEtm2ojNYIH56f7laIvHxMhjGUTg77qGssestyFdrKn8/W+ZxOdC3hUMORBpZ55HzQgt +c+g== X-Received: by 10.60.136.170 with SMTP id qb10mr11101803oeb.71.1422223295904; Sun, 25 Jan 2015 14:01:35 -0800 (PST) Original-Received: from [10.70.17.167] (wsip-66-210-63-210.br.no.cox.net. [66.210.63.210]) by mx.google.com with ESMTPSA id si7sm4336734obc.20.2015.01.25.14.01.35 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 25 Jan 2015 14:01:35 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 In-Reply-To: <87zj96frux.fsf@wmi.amu.edu.pl> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4003:c06::22d X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:102257 Archived-At: Marcin, Thank you for that mini-lesson to help me get started with Edebug! It's funny but I remember seeing a great visualization tool for Python scripts that graphically depicted the sequence of steps in simple scripts/programs. It was intended to help instruct novices and help debug code. I remember thinking, "if only there were something for Elisp tht did that". This is what I needed! Will On 01/25/2015 03:55 PM, Marcin Borkowski wrote: > > On 2015-01-25, at 22:43, Will Monroe wrote: > >> Marcin, >> >> Thanks for your quick and friendly response! > > You're welcome! > >> Thanks for the advice about Edebug. It's definitely something that is >> on my mind. But over the last day or so, I've hesitated from diving >> into Edebug because there was no "error" as such. That is, the code >> "worked" it just didn't do what I intended. Wasn't sure Edebug would >> help in a case like that...but your point is well taken. Thank you! > > It might. It lets you step through the execution of some part of the > code, seeing the result of evaluating each and every expression along > the way. It may be very helpful sometimes. And it's easy to just start > with it: just define the function with C-u C-M-x ("instrument" it for > Edebug), and then -- when the execution gest to it (and pauses) -- use > SPC to step through it or `G' to continue without stopping. When you're > happy with your understanding what's going on in the code, press C-M-x > on the defun again. (There's a lot more to Edebug than this, but it > should be enough to get you started.) > > Best, >