From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Miguel Guedes <miguel.a.guedes@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Debugging Elisp
Date: Sun, 26 May 2013 11:49:40 +0200 [thread overview]
Message-ID: <87li72gjez.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <51a08001$0$32589$862e30e2@ngroups.net> (Miguel Guedes's message of "Sat, 25 May 2013 09:10:26 +0000")
The general solution is to turn debug-on-error on then replicate the
error. With post-command-hook on, though, it's much harder because this
hooks so deeply into the Emacs workflow.
Really, you need to find out what is on "post-command-hook" before it
crashes. This will allow you to narrow down a bit on where the problem
is.
Phil
Miguel Guedes <miguel.a.guedes@gmail.com> writes:
> Hello List,
>
> 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)
--
Phillip Lord, Phone: +44 (0) 191 222 7827
Lecturer in Bioinformatics, Email: phillip.lord@newcastle.ac.uk
School of Computing Science, http://homepages.cs.ncl.ac.uk/phillip.lord
Room 914 Claremont Tower, skype: russet_apples
Newcastle University, twitter: phillord
NE1 7RU
prev parent reply other threads:[~2013-05-26 9:49 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
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 [this message]
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=87li72gjez.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--cc=help-gnu-emacs@gnu.org \
--cc=miguel.a.guedes@gmail.com \
/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.