On 2015-01-25, at 22:43, Will Monroe <wtmonroe.ls@gmail.com> 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,