From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Alan Mackenzie <acm@muc.de>
Cc: John Wiegley <jwiegley@gmail.com>, 23019@debbugs.gnu.org
Subject: bug#23019: parse-partial-sexp doesn't output the full state needed for its continuance.
Date: Tue, 05 Apr 2016 09:50:41 -0400 [thread overview]
Message-ID: <jwvoa9oxj74.fsf-monnier+Inbox@gnu.org> (raw)
In-Reply-To: <20160405125409.GB3463@acm.fritz.box> (Alan Mackenzie's message of "Tue, 5 Apr 2016 12:54:09 +0000")
> One concern I have is that there is code out there which compensates for
> the previous inadequate behaviour (I know there is in CC Mode), and it
> may be more difficult to switch off this compensation if there isn't an
> easy way to distinguish new from old, such as (> (length state) 10).
I'd be very surprised if other packages went to that trouble, but if
needed you can still distinguish the new from the old with something like:
(defconst pps-is-new
(let ((st (make-syntax-table)))
(modify-syntax-entry ?/ ". 14" st)
(with-temp-buffer
(with-syntax-table st
(insert "/")
(nth 5 (parse-partial-sexp (point-min) (point-max)))))))
-- Stefan
next prev parent reply other threads:[~2016-04-05 13:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 9:13 bug#23019: parse-partial-sexp doesn't output the full state needed for its continuance Alan Mackenzie
2016-03-15 9:35 ` Andreas Röhler
2016-03-15 10:15 ` Alan Mackenzie
2016-03-15 13:38 ` Andreas Röhler
2016-03-17 12:58 ` Stefan Monnier
2016-03-17 21:49 ` Alan Mackenzie
2016-03-18 4:49 ` Stefan Monnier
2016-03-18 15:11 ` Alan Mackenzie
2016-03-18 15:22 ` Alan Mackenzie
2016-03-18 16:23 ` Stefan Monnier
2016-03-18 18:25 ` Alan Mackenzie
2016-03-18 19:36 ` Stefan Monnier
2016-03-19 17:06 ` Alan Mackenzie
2016-03-20 1:30 ` Stefan Monnier
2016-03-20 13:41 ` Alan Mackenzie
2016-04-03 22:53 ` John Wiegley
2016-04-04 12:15 ` Stefan Monnier
2016-04-05 12:54 ` Alan Mackenzie
2016-04-05 13:50 ` Stefan Monnier [this message]
2016-04-05 14:44 ` Alan Mackenzie
2016-03-18 16:27 ` Stefan Monnier
2016-03-18 19:16 ` Alan Mackenzie
2016-03-18 19:40 ` 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=jwvoa9oxj74.fsf-monnier+Inbox@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=23019@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=jwiegley@gmail.com \
/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://git.savannah.gnu.org/cgit/emacs.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).