From: "Andrew M. Scott" <amscott1@sedona.ch.intel.com>
Cc: amscott1@sedona.ch.intel.com, emacs-devel@gnu.org,
Mathias Dahl <mathias.dahl@gmail.com>
Subject: Re: (setq blink-matching-paren-dont-ignore-comments nil) ignored?
Date: Thu, 16 Feb 2006 08:08:13 -0700 [thread overview]
Message-ID: <17396.38237.161643.546885@chlr5836.ch.intel.com> (raw)
In-Reply-To: <E1F9axY-0003HY-HS@fencepost.gnu.org>
Richard,
Richard> (
Richard> ;;;;;;;; ( <=== This is skipped
Richard> and insert a ). You will see that this variable takes
Richard> effect.
1. Thanks to the examples provided by you & Mathias Dahl, I now
understand the function of variable
blink-matching-paren-dont-ignore-comments. Thank you both.
2. The current negative logic embodied in the variable name can be
confusing, e.g.:
(setq blink-matching-paren-dont-ignore-comments t)
I think it would be clearer if positive logic were used, e.g.
(setq blink-matching-paren-ignore-comments t)
(setq blink-matching-paren-ignore-comments nil)
with docstring:
blink-matching-paren-ignore-comments is a variable defined in `simple.el'.
Its value is t
Documentation:
*t means `blink-matching-paren' ignores comments.
More precisely, when looking for the matching open parenthesis,
skips the contents of comments that end before point.
3. I also recommend than an example similar to yours/Mathias's in this
thread be added to the (Info-find-node "emacs" "Matching") section.
Thank you,
Andy Scott
next prev parent reply other threads:[~2006-02-16 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 19:09 (setq blink-matching-paren-dont-ignore-comments nil) ignored? Andrew M. Scott
2006-02-09 17:48 ` Richard M. Stallman
2006-02-14 13:54 ` Andrew M. Scott
2006-02-14 23:26 ` Mathias Dahl
2006-02-16 4:41 ` Richard M. Stallman
2006-02-16 15:08 ` Andrew M. Scott [this message]
2006-02-17 3:21 ` Richard M. Stallman
2006-02-15 4:40 ` Richard M. Stallman
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=17396.38237.161643.546885@chlr5836.ch.intel.com \
--to=amscott1@sedona.ch.intel.com \
--cc=emacs-devel@gnu.org \
--cc=mathias.dahl@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 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).