From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: help-gnu-emacs-mXXj517/zsQ@public.gmane.org
Subject: Re: Debugging Elisp
Date: Sat, 25 May 2013 21:00:40 +0200 [thread overview]
Message-ID: <86ehcu28br.fsf@somewhere.org> (raw)
In-Reply-To: 87wqqnjhrw.fsf@kuiper.lan.informatimago.com
Hi Pascal,
"Pascal J. Bourguignon" wrote:
> Miguel Guedes <miguel.a.guedes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
>> Is it possible to set up emacs so as to output more meaningful messages
>> when it steps into errors?
>>
>> I'd be so *very* grateful if someone contributed a tip that makes emacs
>> output a line:col pair when it steps into an error as messages of the
>> kind below are just so frustrating to debug (especially so when it's hard
>> to replicate what causes them):
>>
>> Error in post-command-hook: (wrong-type-argument characterp wrong-type-
>> argument)
>
> M-x set-variable RET debug-on-error RET t RET
>
> Now, in post-command-hooks, when there's an error, the hook is removed
> IIRC, so you have to put it back in, or invoke it separately to debug
> it.
What you say here resonates to me. I have the impression (from pragmatic
observations) that `toggle-debug-on-error' just shows the next first error,
then none. While `M-: (setq debug-on-error t)' will work forever.
The feature with `toggle-debug-on-error' is, for me, quite new. I thought it
was some kind of bug. You say it has been done on purpose. I find that very
strange: when I toggle, I know what I'm doing; if I don't want it anymore, I
toggle another time.
Your explanation clears my mind...
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-05-25 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 9:10 Debugging Elisp Miguel Guedes
2013-05-25 13:44 ` Pascal J. Bourguignon
2013-05-25 19:00 ` Sebastien Vauban [this message]
2013-05-26 0:43 ` Stefan Monnier
[not found] ` <mailman.390.1369529042.22516.help-gnu-emacs@gnu.org>
2013-05-26 19:12 ` Sebastien Vauban
2013-05-26 9:49 ` Phillip Lord
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=86ehcu28br.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=help-gnu-emacs-mXXj517/zsQ@public.gmane.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.