From: Tomi Ollila <tomi.ollila@iki.fi>
To: Austin Clements <amdragon@MIT.EDU>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: Fix bug in resynchronizing after a JSON parse error
Date: Sat, 15 Dec 2012 17:54:21 +0200 [thread overview]
Message-ID: <m2r4mrpaz6.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <1355497655-9571-1-git-send-email-amdragon@mit.edu>
On Fri, Dec 14 2012, Austin Clements <amdragon@MIT.EDU> wrote:
> Previously, if the input stream consisted only of an error message,
> notmuch-json-begin-compound would signal a (wrong-type-argument
> number-or-marker-p nil) error when reaching the end of the error
> message. This happened because notmuch-json-scan-to-value would think
> that it reached a value and put the parser into the 'value state.
> Even after notmuch-json-begin-compound signaled the syntax error, the
> parser would remain in this state and when the resynchronization logic
> reached the end of the buffer, the parser would fail because the
> 'value state indicates that characters are available.
>
> This fixes this problem by restoring the parser's previous state if it
> encounters a syntax error.
> ---
I couldn't understand this (setf... even reading the docstring
(and no time to experiment)
anyway the code change is pretty trivial and i cannot see what
it could break. I believe the code works as expected, so
+1
Tomi
>
> This patch was already okayed by Mark Walters [0] in the context of a
> larger series. Since it's independent of that larger series, I'm
> re-sending it separately.
>
> [0] id:87hanxgczt.fsf@qmul.ac.uk
>
> emacs/notmuch-lib.el | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
> diff --git a/emacs/notmuch-lib.el b/emacs/notmuch-lib.el
> index 9c4ee71..fb6d3e7 100644
> --- a/emacs/notmuch-lib.el
> +++ b/emacs/notmuch-lib.el
> @@ -465,15 +465,19 @@ Entering JSON objects is currently unimplemented."
> (with-current-buffer (notmuch-json-buffer jp)
> ;; Disallow terminators
> (setf (notmuch-json-allow-term jp) nil)
> - (or (notmuch-json-scan-to-value jp)
> - (if (/= (char-after) ?\[)
> - (signal 'json-readtable-error (list "expected '['"))
> - (forward-char)
> - (push ?\] (notmuch-json-term-stack jp))
> - ;; Expect a value or terminator next
> - (setf (notmuch-json-next jp) 'expect-value
> - (notmuch-json-allow-term jp) t)
> - t))))
> + ;; Save "next" so we can restore it if there's a syntax error
> + (let ((saved-next (notmuch-json-next jp)))
> + (or (notmuch-json-scan-to-value jp)
> + (if (/= (char-after) ?\[)
> + (progn
> + (setf (notmuch-json-next jp) saved-next)
> + (signal 'json-readtable-error (list "expected '['")))
> + (forward-char)
> + (push ?\] (notmuch-json-term-stack jp))
> + ;; Expect a value or terminator next
> + (setf (notmuch-json-next jp) 'expect-value
> + (notmuch-json-allow-term jp) t)
> + t)))))
>
> (defun notmuch-json-read (jp)
> "Parse the value at point in JP's buffer.
> --
> 1.7.10.4
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
next prev parent reply other threads:[~2012-12-15 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 15:07 [PATCH] emacs: Fix bug in resynchronizing after a JSON parse error Austin Clements
2012-12-15 15:54 ` Tomi Ollila [this message]
2012-12-15 18:35 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2r4mrpaz6.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=amdragon@MIT.EDU \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).