From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Matt Armstrong <marmstrong@google.com>
Cc: 24870@debbugs.gnu.org
Subject: bug#24870: 26.0.50; parse-partial-sexp ignores comment-end
Date: Thu, 1 Dec 2016 09:33:42 +0100 [thread overview]
Message-ID: <6979d874-dc17-6b6f-3d8d-000832e6ba50@easy-emacs.de> (raw)
In-Reply-To: <qf537i8h8q8.fsf@marmstrong-linux.kir.corp.google.com>
On 01.12.2016 00:02, Matt Armstrong wrote:
> Also, can you describe the visible symptom that caused you to begin
> looking at syntax-ppss and parse-partial-sexp? That description may
> help me or others spot similarities with other reported bugs.
>
> (I must say that I am not an Emacs expert, and I do not usually reply to
> Emacs bugs. I looked at a few bugs last night as a way to help
> maintainers triage the "easy" bugs. It does not look like this bug is
> easy!)
It broke some code relying on results of parse-partial-sexp
This , resp. syntax-ppss, is an internally widely used function.
prev parent reply other threads:[~2016-12-01 8:33 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
2017-01-24 0:30 ` npostavs
2016-12-01 8:33 ` Andreas Röhler [this message]
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=6979d874-dc17-6b6f-3d8d-000832e6ba50@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=24870@debbugs.gnu.org \
--cc=marmstrong@google.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 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.