better error messages in my *Messages* buffer?

better error messages in my *Messages* buffer?

[kleinerdrache]

Hi there,

learing elisp is fun, but debugging isn't for me at the moment.
From ruby and from python I'm spoiled with additional info like

Error X in file Y line Z

but my *Messages* buffer just tells me:

error in process filter: Wrong type argument: listp, [...] 

What do you do in that case to find out which line of your code creates
that error?

Thanks,
Martin

Re: better error messages in my *Messages* buffer?

[Joost Kremers]

kleinerdrache@gmx.at wrote:
> error in process filter: Wrong type argument: listp, [...] 
>
> What do you do in that case to find out which line of your code creates
> that error?

`M-x toggle-debug-on-error is the first thing that comes to mind. Or do
`M-x debug-on-entry RET <your_function> RET'. Make sure the relevant
functions are not byte-compiled. And read up on the debugger:

(info "(elisp) Debugging")
(info "(elisp) Debugger")

-- 
Joost Kremers                                   joostkremers@fastmail.fm
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

Re: better error messages in my *Messages* buffer?

[Marcin Borkowski]

Dnia 2014-03-19, o godz. 19:25:03
Joost Kremers <joost.m.kremers@gmail.com> napisał(a):

> kleinerdrache@gmx.at wrote:
> > error in process filter: Wrong type argument: listp, [...] 
> >
> > What do you do in that case to find out which line of your code
> > creates that error?
> 
> `M-x toggle-debug-on-error is the first thing that comes to mind. Or
> do `M-x debug-on-entry RET <your_function> RET'. Make sure the
> relevant functions are not byte-compiled. And read up on the debugger:
> 
> (info "(elisp) Debugging")
> (info "(elisp) Debugger")
> 

Also, Edebug comes to mind.

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

Re: better error messages in my *Messages* buffer?

[ian.tegebo]

Other people have suggested reading the manual regarding debugging and Edebug in particular; I'd agree with that.  However, *Messages* really should report from where and when a message arrived.  I used the following as a basis for my own tweaking:

http://www.emacswiki.org/emacs/DebugMessages

By itself, I think the above hack is a bit too noisy.  In particular, it interrupts completion in the minibuffer.

On Wednesday, March 19, 2014 12:17:05 PM UTC-7, kleine...@gmx.at wrote:
> Hi there,
> 
> 
> 
> learing elisp is fun, but debugging isn't for me at the moment.
> 
> >From ruby and from python I'm spoiled with additional info like
> 
> 
> 
> Error X in file Y line Z
> 
> 
> 
> but my *Messages* buffer just tells me:
> 
> 
> 
> error in process filter: Wrong type argument: listp, [...] 
> 
> 
> 
> What do you do in that case to find out which line of your code creates
> 
> that error?
> 
> 
> 
> Thanks,
> 
> Martin