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 23:47:24 +0200 [thread overview]
Message-ID: <87shukuryr.fsf@web.de> (raw)
In-Reply-To: <CAM6wYYL_Eua3NR+GRAxFVR4mqKExuGaDrMKbBfKZq3PHroKsxw@mail.gmail.com> (Andrew Hyatt's message of "Thu, 04 Aug 2016 20:17:08 +0000")
Andrew Hyatt <ahyatt@gmail.com> writes:
> It'd be nice, I guess, if you could just turn it to nil when in a
> comment.
Yes, I think we could bind `parse-sexp-ignore-comments' to nil around
the calls to `scan-sexps' in `show-paren--default' when point is inside
a comment. But I must admit that I don't understand the terse doc of
`parse-sexp-ignore-comments':
| Non-nil means `forward-sexp', etc., should treat comments as
| whitespace.
But what does nil mean, exactly? It seems that comments are then
treated as if they were indistinguishable from code. When I set
`parse-sexp-ignore-comments' to nil in emacs-lisp-mode, and have such a
file:
;; (
)
then show-paren-mode indicates the parens as matching, though one is
inside in a comment, and the other is not. `scan-sexps' behaves
accordingly. That would mean we would need to assure that the matching
paren position that `scan-sexps' has found is still inside the current
comment.
Michael.
next prev parent reply other threads:[~2016-08-04 21:47 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
2016-08-04 20:17 ` Andrew Hyatt
2016-08-04 21:47 ` Michael Heerdegen [this message]
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=87shukuryr.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.