From: "Andrew M. Scott" <amscott1@sedona.ch.intel.com>
Subject: (setq blink-matching-paren-dont-ignore-comments nil) ignored?
Date: Tue, 7 Feb 2006 12:09:05 -0700 [thread overview]
Message-ID: <200602071909.k17J95s5029362@chlr5836.ch.intel.com> (raw)
I'm seeing blink-matches on parenthesese in comments with
(setq blink-matching-paren-dont-ignore-comments nil) [the default, BTW]
even though the docstring on blink-matching-paren-dont-ignore-comments
says I shouldn't.
% emacs -q &
In the *scratch* buffer, type
(setq debug-on-error t) ; ((setq debug-on-error nil))
The parentheses will blink-match all the close-parens in the comment.
Just for completeness, comment-start's value is ";" in *scratch*.
Thanks,
Andy
In GNU Emacs 22.0.50.1 (x86_64-unknown-linux-gnu, X toolkit)
of 2006-02-06 on chlr5836
X server distributor `The XFree86 Project, Inc', version 11.0.40201000
configured using `configure '--prefix=/stor/garray/linux_2.6.5_x86-64' '--x-includes=/usr/intel/pkgs/X11/R6.7.0-64/include' '--x-libraries=/usr/intel/pkgs/X11/R6.7.0-64/lib' 'CC=gcc' 'CFLAGS=-O2 -I/usr/intel/pkgs/X11/R6.7.0-64/include -L/usr/intel/pkgs/X11/R6.7.0-64/lib -I/usr/intel/pkgs/zlib/1.2.1-64/include -L/usr/intel/pkgs/zlib/1.2.1-64/lib -I/usr/intel/pkgs/ncurses/5.4/include -L/usr/intel/pkgs/ncurses/5.4/lib -I/usr/intel/pkgs/libungif/4.1.3/include -L/usr/intel/pkgs/libungif/4.1.3/lib -I/usr/intel/pkgs/libpng/1.0.16rc1-64/include -L/usr/intel/pkgs/libpng/1.0.16rc1-64/lib -I/usr/intel/pkgs/jpeg/6b-64/include -L/usr/intel/pkgs/jpeg/6b-64/lib' 'LDFLAGS=-L/usr/intel/pkgs/X11/R6.7.0-64/lib -L/usr/intel/pkgs/zlib/1.2.1-64/lib -L/usr/intel/pkgs/ncurses/5.4/lib -L/usr/intel/pkgs/libungif/4.1.3/lib -L/usr/intel/pkgs/libpng/1.0.16rc1-64/lib -L/usr/intel/pkgs/jpeg/6b-64/lib -Wl,-rpath=/usr/
intel/pkgs/X11/R6.7.0-64/lib:/usr/intel/pkgs/zlib/1.2.1-64/lib:/usr/intel/pkgs/ncurses/5.!
4/lib:/usr/intel/pkgs/libungif/4.1.3/lib:/usr/intel/pkgs/libpng/1.0.16rc1-64/lib:/usr/intel/pkgs/jpeg/6b-64/lib''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_US.UTF-8
locale-coding-system: utf-8
default-enable-multibyte-characters: t
Major mode: Lisp Interaction
Minor modes in effect:
tooltip-mode: t
auto-compression-mode: t
tool-bar-mode: t
mouse-wheel-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
unify-8859-on-encoding-mode: t
utf-translate-cjk-mode: t
line-number-mode: t
next reply other threads:[~2006-02-07 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 19:09 Andrew M. Scott [this message]
2006-02-09 17:48 ` (setq blink-matching-paren-dont-ignore-comments nil) ignored? 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
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=200602071909.k17J95s5029362@chlr5836.ch.intel.com \
--to=amscott1@sedona.ch.intel.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).