From: Michael Heerdegen <michael_heerdegen@web.de>
To: Andrew Hyatt <ahyatt@gmail.com>
Cc: Matrix <min.matrix@gmail.com>, 5410@debbugs.gnu.org
Subject: bug#5410: Parenthesis Matching Bug!!
Date: Thu, 04 Aug 2016 04:55:16 +0200 [thread overview]
Message-ID: <871t25fdkb.fsf@web.de> (raw)
In-Reply-To: <m2ziotcm45.fsf@Andrews-MacBook-Pro.local> (Andrew Hyatt's message of "Wed, 03 Aug 2016 22:18:50 -0400")
Andrew Hyatt <ahyatt@gmail.com> writes:
> Your example reproduces for me in Emacs 25. My guess is that emacs
> doesn't really assume that comment lines should be treated as a
> contiguous text block. Which is sometimes right, sometimes not, in my
> experience.
We are talking about `show-paren-mode', right? AFAICT this just calls
`scan-sexps' and looks if that errors or not, without doing syntactical
analysis itself.
`parse-sexp-ignore-comments' influences `scan-sexps's behavior in this
regard, and setting it to nil does change the behavior in this case for
me. I guess we could use this for a solution.
> For example, you could have comments that are something
> like:
>
> // This function does three things:
> // 1) Reverse the string
> // 2) Uuencode the string
> // 3) Rot-13 the string
>
> Which certainly wouldn't make a lot of sense treated contiguously.
Well, we would not loose anything in this case: parens are already shown
as mismatches now.
Michael.
next prev parent reply other threads:[~2016-08-04 2:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 12:20 bug#5410: Parenthesis Matching Bug!! Matrix
2016-08-04 2:18 ` Andrew Hyatt
2016-08-04 2:55 ` Michael Heerdegen [this message]
2016-08-04 20:17 ` Andrew Hyatt
2016-08-04 21:47 ` Michael Heerdegen
2016-08-11 3:57 ` Andrew Hyatt
2016-08-23 15:02 ` Michael Heerdegen
2022-05-02 9:02 ` bug#5410: bug#5411: show-paren-mode and parens spread over multi-line comments Lars Ingebrigtsen
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=871t25fdkb.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=5410@debbugs.gnu.org \
--cc=ahyatt@gmail.com \
--cc=min.matrix@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 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.