From: npostavs@users.sourceforge.net
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 4920@debbugs.gnu.org
Subject: bug#4920: 23.1; (check-parens) problem with bash script case items unbalanced close paren
Date: Sun, 10 Jul 2016 08:14:15 -0400 [thread overview]
Message-ID: <87mvlpheqw.fsf@users.sourceforge.net> (raw)
In-Reply-To: <jwvk2gugs5y.fsf-monnier+Inbox@gnu.org> (Stefan Monnier's message of "Sat, 09 Jul 2016 22:11:43 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> FWIW, the new support in Emacs-25 for calling syntax-propertize directly
>>> from forward-parsing operations should make the above unnecessary (tho
>>> I must admit I haven't tested this).
>> The test I mentioned above still fails on Emacs-25. Where is
>> syntax-propertize supposed to be called from?
>
> Things like forward-sexp, parse-partial-sexp, scan-sexps, ...
Oh I see, but it's disabled by default, that's why my the test was still
failing. Doing
emacs -Q bug-4920-check-parens.sh --eval '(setq parse-sexp-lookup-properties t)' -f check-parens
succeeds. Should this variable be set by sh-mode along with the other
syntax propertize settings?
next prev parent reply other threads:[~2016-07-10 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 16:28 bug#4920: 23.1; (check-parens) problem with bash script case items unbalanced close paren Chong Yidong
2009-11-14 18:11 ` Stefan Monnier
2009-11-16 12:25 ` Jeremy Hall
2016-07-08 1:10 ` npostavs
2016-07-10 0:11 ` Stefan Monnier
2016-07-10 0:39 ` Noam Postavsky
2016-07-10 2:11 ` Stefan Monnier
2016-07-10 12:14 ` npostavs [this message]
2016-07-10 12:38 ` Stefan Monnier
2016-07-10 13:16 ` npostavs
2016-07-10 14:20 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2009-11-13 16:14 Jeremy Hall
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=87mvlpheqw.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=4920@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).