From: ndame <emacsuser@freemail.hu>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Is there a reason why iinvalid-read-syntax doesn't give me the location of the error?
Date: Wed, 7 Aug 2019 15:40:52 +0200 (CEST) [thread overview]
Message-ID: <AxwYKQ.ZaaBVMLXAAlk.zvffFt679MgjCrVrEyT@freemail.hu> (raw)
Sometimes I encounter huge generated elisp list data which has a
problem somewhere. So when I evaluate it I get the error:
Lisp error: (invalid-read-syntax ". in wrong context")
I wonder why the error message doesn't give me the location of the
error like scan-error. I have to bisect the file to find the bad part.
Doesn't invalid-read-syntax have the location where it encountered the
error? If it does then why doesn't it print it like scan-error?
next reply other threads:[~2019-08-07 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 13:40 ndame [this message]
2019-08-07 13:59 ` Is there a reason why iinvalid-read-syntax doesn't give me the location of the error? Michael Heerdegen
2019-08-07 14:17 ` Noam Postavsky
2019-08-07 14:34 ` ndame
2019-08-08 8:10 ` Stefan Monnier
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=AxwYKQ.ZaaBVMLXAAlk.zvffFt679MgjCrVrEyT@freemail.hu \
--to=emacsuser@freemail.hu \
--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).