Re: Feature Request: Auto-jumping to source file (.el) upon elisp error

[Stefan Kamphausen]

Hi,

"Nordlöw" <per.nordlow@gmail.com> writes:

> But the top-most function, in your case produce-an-error(), is neither
> clickable nor mentioned about its file/buffer-origin in the Debugger
> output. This is sad because this is what the user/developer wants to
> see first in order to most easily understand the top-most (call-stack)
> context of the problem.

you are right that the function is not clickable in the backtrace if
being added interactively.  It does work however, if it was written
into a separate file and then loaded via (e.g.) M-x load-file.

Does that fit your needs?

Regards,
Stefan
-- 
Stefan Kamphausen --- http://www.skamphausen.de
a blessed +42 regexp of confusion (weapon in hand)
You hit. The format string crumbles and turns to dust.