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

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
This bug report was last modified 17 years and 74 days ago.

Previous Next

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