unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@stupidchicken.com>,
	<5122@emacsbugs.donarmstrong.com>,
	"'Eli Zaretskii'" <eliz@gnu.org>
Subject: bug#5122: Mismatched parentheses when dealing with hugebuffercontent
Date: Sun, 6 Dec 2009 09:05:57 -0800	[thread overview]
Message-ID: <3C515F3078FA4C4CB6AA413FC1BE8906@us.oracle.com> (raw)
In-Reply-To: <878wdgw25e.fsf@stupidchicken.com>

> >> The circumstances in which the parenthesis are mismatched probably
> >> vastly outweigh the circumstances in which the user wants to change
> >> blink-matching-paren-distance.
> >
> > I suggested the modified message text _only_ for those 
> > cases where the search hits the limit.
> 
> How do you distinguish this from the plain old "no mismatched
> parenthesis" case?  Like I said, if there is no matching parenthesis
> within the search limit (which, btw, has been increased in 
> Emacs 22.3), in most cases the parentheses really are mismatched.

The code lets you distinguish. It simply needs to DTRT when it knows that the
arbitrary limit was reached.

Look at the code in both simple.el and paren.el. The code knows when it is using
the limit (narrowing etc.). Currently, it doesn't distinguish this case from the
case where it simply hits bob/eob, but it certainly could.

(No, I won't be sending a patch for this. If the will is there, you will see
easily enough what needs to be done.)






  reply	other threads:[~2009-12-06 17:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-05 20:57 bug#5122: Mismatched parentheses when dealing with huge buffercontent Chong Yidong
2009-12-05 21:42 ` Stefan Monnier
2009-12-05 22:06   ` Chong Yidong
2009-12-05 21:47 ` Eli Zaretskii
2009-12-05 22:11   ` Chong Yidong
2009-12-06  2:08     ` bug#5122: Mismatched parentheses when dealing with hugebuffercontent Drew Adams
2009-12-06 15:15       ` Drew Adams
2009-12-06 19:13       ` Chong Yidong
2009-12-06 20:57         ` Drew Adams
2009-12-06  4:03     ` bug#5122: Mismatched parentheses when dealing with huge buffercontent Eli Zaretskii
2009-12-06 15:30       ` Chong Yidong
2009-12-06 17:05         ` Drew Adams [this message]
2009-12-06 17:52         ` Eli Zaretskii
2009-12-06 18:59           ` Chong Yidong
2009-12-06 19:23             ` bug#5122: Mismatched parentheses when dealing with hugebuffercontent Drew Adams
2009-12-07  2:25   ` bug#5122: Mismatched parentheses when dealing with huge buffercontent Stefan Monnier
2011-07-13 14:59     ` Lars Magne Ingebrigtsen
2011-07-13 16:35       ` Drew Adams
2011-07-13 17:26       ` Drew Adams

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=3C515F3078FA4C4CB6AA413FC1BE8906@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=5122@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@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).