From: Davin Pearson <davin.pearson@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: How do I go about debugging my Elisp code?
Date: Sat, 8 Jan 2022 18:20:47 +1300 [thread overview]
Message-ID: <CAG9ihEv+vex+5=PLcn2Pvs1RLQQgGVjjD7_sGxcZOYscr2mj=g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
I sent this email to gnu.emacs.help but got no reply :-(
When it comes up with a back trace it notifies you of the
problematic line of code but doesn't tell you which line the
error comes from.
What I have to do with this is to put debugger checkpoints on
every second line of Elisp code. At least that gives you the
location of the error message, by looking at the *Messages*
buffer you can see the last checkpoint before the debugger
was entered...
See the file at the following location for an example.
In this file debug lines are commented out like so
;;(message "#cream:[0-9]+:")
http://davinpearson.nz/binaries/dmp-padderise.el
Executing the command in this file called dmp-padderise.el:
dmp-padderise--uncomment-hash-lines makes all the debug lines
visible to the Elisp system. Executing the following command:
dmp-padderise--comment-hash-lines comments out the debug lines.
Is there a better way to hunt down error messages?
Could someone email me a hyperlink to a superior debugging
system?
[-- Attachment #2: Type: text/html, Size: 1231 bytes --]
next reply other threads:[~2022-01-08 5:20 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 5:20 Davin Pearson [this message]
2022-01-10 10:11 ` How do I go about debugging my Elisp code? Michael Heerdegen
2022-01-10 10:37 ` Po Lu
2022-01-13 1:22 ` Fwd: " Davin Pearson
2022-01-13 1:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-13 12:58 ` Michael Heerdegen
2022-01-14 6:55 ` Marcin Borkowski
2022-01-14 8:24 ` Jean Louis
2022-01-14 23:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-14 13:46 ` Jean Louis
2022-01-14 14:56 ` Tassilo Horn
2022-01-14 15:20 ` Jean Louis
2022-01-14 16:23 ` Tassilo Horn
2022-01-14 16:53 ` Jean Louis
2022-01-14 17:24 ` Tassilo Horn
2022-01-14 17:57 ` Jean Louis
2022-01-14 18:58 ` Tassilo Horn
2022-01-15 7:34 ` Jean Louis
2022-01-14 18:56 ` Marcin Borkowski
2022-01-14 19:02 ` Jean Louis
2022-01-14 19:51 ` Tassilo Horn
2022-01-15 7:35 ` Jean Louis
2022-01-15 10:15 ` Tassilo Horn
2022-01-15 11:33 ` Jean Louis
2022-01-18 0:03 ` Davin Pearson
2022-01-14 23:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-14 23:26 ` NonGNU ELPA (was: Re: Fwd: How do I go about debugging my Elisp code?) Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 7:39 ` Jean Louis
2022-01-17 3:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-17 18:15 ` Jean Louis
2022-01-18 0:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-18 5:02 ` Jean Louis
2022-01-18 6:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-18 3:02 ` NonGNU ELPA Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-18 3:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-18 3:49 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-21 21:32 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 4:00 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-22 4:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 5:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 5:24 ` Po Lu
2022-01-22 5:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 6:32 ` Po Lu
2022-01-22 6:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 7:10 ` Po Lu
2022-01-22 12:24 ` Jean Louis
2022-01-22 12:38 ` Po Lu
2022-01-22 11:13 ` Jean Louis
2022-01-22 13:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-23 9:24 ` Jean Louis
2022-01-23 16:26 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-23 16:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 4:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 5:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-18 3:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-14 17:40 ` Fwd: How do I go about debugging my Elisp code? Yuri Khan
2022-01-14 17:51 ` Jean Louis
2022-01-14 23:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-14 23:24 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 2:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 8:24 ` Jean Louis
-- strict thread matches above, loose matches on Subject: below --
2022-01-08 5:36 No Wayman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG9ihEv+vex+5=PLcn2Pvs1RLQQgGVjjD7_sGxcZOYscr2mj=g@mail.gmail.com' \
--to=davin.pearson@gmail.com \
--cc=emacs-devel@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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.