From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>,
Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: RE: Debugger output: where to look for its explanation?
Date: Sat, 28 Mar 2015 18:01:07 -0700 (PDT) [thread overview]
Message-ID: <90f11922-7559-491a-bff9-b2c99508d6f8@default> (raw)
In-Reply-To: <874mp4iv1g.fsf@wmi.amu.edu.pl>
> so I got this as a *Backtrace*:
>
> Debugger entered--Lisp error: (scan-error "Containing expression ends
> prematurely" 2959 2959)
No doubt someone will give you interesting details about the info
in the backtrace.
FWIW, whenever I get that error message it's pretty clear what the
problem is, because I was evaluating a sexp (so I know which one is
problematic). It's typically because I forgot a right paren somewhere.
next prev parent reply other threads:[~2015-03-29 1:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 23:03 Debugger output: where to look for its explanation? Marcin Borkowski
2015-03-29 1:01 ` Drew Adams [this message]
2015-03-29 13:03 ` Marcin Borkowski
2015-03-30 7:00 ` Nicolas Richard
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=90f11922-7559-491a-bff9-b2c99508d6f8@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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).