all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Andrew M. Scott" <amscott1@sedona.ch.intel.com>
Cc: "Andrew M. Scott" <amscott1@sedona.ch.intel.com>, emacs-devel@gnu.org
Subject: Re: (setq blink-matching-paren-dont-ignore-comments nil) ignored?
Date: Tue, 14 Feb 2006 06:54:51 -0700	[thread overview]
Message-ID: <17393.57643.99565.332674@chlr5836.ch.intel.com> (raw)
In-Reply-To: <E1F7FuP-0000Mi-K5@fencepost.gnu.org>

    >>>>> "Richard" == Richard M Stallman <rms@gnu.org> writes:
    Richard>     (setq debug-on-error t) ; ((setq debug-on-error nil))
    Richard>     The parentheses will blink-match all the close-parens
    Richard>     in the comment.

    Richard> The effect of the feature is to ignore previous parens
    Richard> that are in comments.
    Richard> I will clarify the documentation.
          
Richard, 

Unfortunately, even after reading the updated docstring several times
and experimenting, I still can't visualize what
blink-matching-paren-dont-ignore-comments is supposed to do. I also
looked for an example in (Info-find-node "emacs" "Matching") but there
is no mention of this variable there, either.


M-x describe-variable blink-matching-paren-dont-ignore-comments:

blink-matching-paren-dont-ignore-comments is a variable defined in `simple.el'.
Its value is t

Documentation:
*nil means `blink-matching-paren' ignores comments.
More precisely, when looking for the matching parenthesis,
it skips the contents of comments that end before point.

Puzzled,
Andy Scott

  reply	other threads:[~2006-02-14 13:54 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 [this message]
2006-02-14 23:26     ` Mathias Dahl
2006-02-16  4:41       ` Richard M. Stallman
2006-02-16 15:08         ` Andrew M. Scott
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17393.57643.99565.332674@chlr5836.ch.intel.com \
    --to=amscott1@sedona.ch.intel.com \
    --cc=emacs-devel@gnu.org \
    /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.