From: Alan Mackenzie <acm@muc.de>
To: npostavs@users.sourceforge.net
Cc: 24870@debbugs.gnu.org, Matt Armstrong <marmstrong@google.com>
Subject: bug#24870: 26.0.50; parse-partial-sexp ignores comment-end
Date: Mon, 23 Jan 2017 20:12:32 +0000 [thread overview]
Message-ID: <20170123201232.GB4397@acm> (raw)
In-Reply-To: <87mvevzp8q.fsf@users.sourceforge.net>
Hello, Noam.
Sorry this is very late, but better that than not at all.
On Thu, Jan 12, 2017 at 21:07:49 -0500, npostavs@users.sourceforge.net wrote:
> npostavs@users.sourceforge.net writes:
> > Alan Mackenzie <acm@muc.de> writes:
> >> (ii) In `parse-partial-sexp-continue-over-comment-marker', variable aftC
> >> is the position in the middle of the comment closer "*/". I don't think
> >> you are testing in any way that element 10 (nil, or the syntax of the
> >> position just before the end point when that position might be the first
> >> character of a two-character construct, i.e. an escape or first char of a
> >> double-char comment delimiter) is correct.
> > My idea was that its effect would be tested by using pps-preC as
> > OLDSTATE, which avoids having to encode the specifics in the test. I
> > added another clause which uses pps-aftC to cover parsing from the
> > middle of a comment closer as well as opener.
> Ping? Agree/Disagree?
I've just had another fairly intensive look at the patches, and I agree.
I think it's time to commit these. What do you say?
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-01-23 20:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 19:38 bug#24870: 26.0.50; parse-partial-sexp ignores comment-end Andreas Röhler
2016-11-30 9:10 ` Matt Armstrong
2016-11-30 12:37 ` Andreas Röhler
2016-11-30 23:02 ` Matt Armstrong
2016-12-01 1:17 ` npostavs
2016-12-01 8:24 ` Andreas Röhler
2016-12-14 3:00 ` npostavs
2016-12-14 4:04 ` npostavs
2016-12-14 6:45 ` Andreas Röhler
2016-12-14 19:56 ` Alan Mackenzie
2016-12-15 8:18 ` Andreas Röhler
2016-12-15 16:01 ` Eli Zaretskii
2016-12-15 16:50 ` Alan Mackenzie
2016-12-15 17:59 ` Andreas Röhler
2016-12-14 21:58 ` Alan Mackenzie
2016-12-15 16:33 ` Noam Postavsky
2016-12-15 16:44 ` Alan Mackenzie
2016-12-18 5:39 ` npostavs
2016-12-29 11:14 ` Alan Mackenzie
2016-12-30 1:55 ` npostavs
2017-01-13 2:07 ` npostavs
2017-01-23 20:12 ` Alan Mackenzie [this message]
2017-01-24 0:30 ` npostavs
2016-12-01 8:33 ` Andreas Röhler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170123201232.GB4397@acm \
--to=acm@muc.de \
--cc=24870@debbugs.gnu.org \
--cc=marmstrong@google.com \
--cc=npostavs@users.sourceforge.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.