GNU bug report logs - #180
GNU Emacs Lisp

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 180 in the body.
You can then email your comments to 180 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Stuart Cracraft <smcracraft <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: GNU Emacs Lisp
Date: Thu, 01 May 2008 15:59:50 -0700

Hi All,

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?

I have used edebug, by the way, and am seeking something
like the above as well, unless edebug can stop exactly
at the line in the source code where the S-expression is
broken, without having to single-step it.

Thanks ahead (anyone),

Stuart

Message #10 received at 180 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: Stuart Cracraft <smcracraft <at> gmail.com>
Cc: 180 <at> debbugs.gnu.org
Subject: Re: GNU Emacs Lisp
Date: Fri, 02 May 2008 11:17:03 -0400

> 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).

Message #15 received at 180 <at> emacsbugs.donarmstrong.com (full text, mbox):

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: Re: 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).
>
>   

Previous Next

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