GNU bug report logs - #180
GNU Emacs Lisp

Previous Next

Package: emacs;

Reported by: Stuart Cracraft <smcracraft <at> gmail.com>

Date: Thu, 1 May 2008 23:30:03 UTC

Severity: normal

Done: Chong Yidong <cyd <at> stupidchicken.com>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Stuart Cracraft <smcracraft <at> gmail.com>
To: Chong Yidong <cyd <at> stupidchicken.com>
Cc: Stuart Cracraft <smcracraft <at> gmail.com>, 180 <at> debbugs.gnu.org
Subject: bug#180: GNU Emacs Lisp
Date: Fri, 02 May 2008 08:29:30 -0700

Chong,

Thankyou very much.

Stuart

Chong Yidong wrote:
>> I see that when running a program in GNU Emacs Lisp
>> that errors in the message area below the mode-line but
>> without a line-number corresponding to the line of the
>> error in the source code being run.
>>
>> So, without the line number, it is hunt-and-peck, much
>> harder to find the section of code with the problem. Is there
>> a way to locate the erring S-expression more quickly?
>>     
>
> Set debug-on-error to t, and you will get a backtrace, which can be used
> to jump to the function that signalled the error (as well as the
> functions that called it).
>
>
This bug report was last modified 17 years and 73 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.