unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: blink-matching-paren is missing
Date: Fri, 09 Jun 2006 10:22:45 +0300	[thread overview]
Message-ID: <u4pyusshm.fsf@gnu.org> (raw)
In-Reply-To: <m3slmfhydi.fsf@chenla.org> (message from Brad Collins on Fri, 09 Jun 2006 09:11:05 +0700)

> From: Brad Collins <brad@chenla.org>
> Date: Fri, 09 Jun 2006 09:11:05 +0700
> 
> I'm running a recent build from CVS (less than a month) and noticed
> the following in the manual.
> 
> ,----[ 31.4.3 Automatic Display Of Matching Parentheses ]
> |    `blink-matching-paren' turns the feature on or off: `nil' disables
> | it, but the default is `t' to enable match display.
> | 
> |    `blink-matching-delay' says how many seconds to leave the cursor on
> | the matching opening delimiter, before bringing it back to the real
> | location of point; the default is 1, but on some systems it is useful
> | to specify a fraction of a second.
> | 
> |    `blink-matching-paren-distance' specifies how many characters back
> | to search to find the matching opening delimiter.  If the match is not
> | found in that distance, scanning stops, and nothing is displayed.  This
> | is to prevent the scan for the matching delimiter from wasting lots of
> | time when there is no match.  The default is 25600.
> `----
> 
> None of these appear to exist any longer.

??? I clearly see them all in the current CVS.

How did you establish that these three variables are gone?

  parent reply	other threads:[~2006-06-09  7:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09  2:11 blink-matching-paren is missing Brad Collins
2006-06-09  7:10 ` Nick Roberts
2006-06-09  7:22 ` Eli Zaretskii [this message]
2006-06-09 15:59 ` Richard 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=u4pyusshm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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 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).