From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Pascal J. Bourguignon" Newsgroups: gmane.emacs.help Subject: Re: Debugging Elisp Date: Sat, 25 May 2013 15:44:35 +0200 Organization: Informatimago Message-ID: <87wqqnjhrw.fsf@kuiper.lan.informatimago.com> References: <51a08001$0$32589$862e30e2@ngroups.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1369504167 22421 80.91.229.3 (25 May 2013 17:49:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 25 May 2013 17:49:27 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat May 25 19:49:29 2013 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 1UgIau-0007Dx-0U for geh-help-gnu-emacs@m.gmane.org; Sat, 25 May 2013 19:49:28 +0200 Original-Received: from localhost ([::1]:47616 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UgIat-0006Bv-J6 for geh-help-gnu-emacs@m.gmane.org; Sat, 25 May 2013 13:49:27 -0400 Original-Path: usenet.stanford.edu!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 29 Original-X-Trace: individual.net JPvlAbEKRFotavs4qH5JVQEUAojNXp84YpdhaWSWfrbRktoQm2 Cancel-Lock: sha1:ODI0Yzc4ZDlkMmYwNWQ0ZTQzMTJmNzJjNjhjNDNhNWY1MTQwOGY4MA== sha1:uuE3uOiTKr7dSocZb8IuMvdtR3I= Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA oElEQVR4nK3OsRHCMAwF0O8YQufUNIQRGIAja9CxSA55AxZgFO4coMgYrEDDQZWPIlNAjwq9 033pbOBPtbXuB6PKNBn5gZkhGa86Z4x2wE67O+06WxGD/HCOGR0deY3f9Ijwwt7rNGNf6Oac l/GuZTF1wFGKiYYHKSFAkjIo1b6sCYS1sVmFhhhahKQssRjRT90ITWUk6vvK3RsPGs+M1RuR mV+hO/VvFAAAAABJRU5ErkJggg== X-Accept-Language: fr, es, en User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Original-Xref: usenet.stanford.edu gnu.emacs.help:198780 X-Mailman-Approved-At: Sat, 25 May 2013 13:48:58 -0400 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:91047 Archived-At: Miguel Guedes 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) 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. When you enter the debugger, you can then go over some link and type RET to jump to the source of the faulty expression. -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}. You can take the lisper out of the lisp job, but you can't take the lisp out of the lisper (; -- antifuchs