From: "ian.tegebo" <ian.tegebo@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: better error messages in my *Messages* buffer?
Date: Thu, 20 Mar 2014 09:44:09 -0700 (PDT) [thread overview]
Message-ID: <69d783d3-573b-4f13-bcc8-461b803fbf28@googlegroups.com> (raw)
In-Reply-To: <mailman.17570.1395256643.10748.help-gnu-emacs@gnu.org>
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
next prev parent reply other threads:[~2014-03-20 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.17570.1395256643.10748.help-gnu-emacs@gnu.org>
2014-03-19 19:25 ` better error messages in my *Messages* buffer? Joost Kremers
2014-03-20 2:04 ` Marcin Borkowski
2014-03-20 16:44 ` ian.tegebo [this message]
2014-03-19 19:17 kleinerdrache
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69d783d3-573b-4f13-bcc8-461b803fbf28@googlegroups.com \
--to=ian.tegebo@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).