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