all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Joe Wells <jbw@macs.hw.ac.uk>
To: Sven Joachim <svenjoac@gmx.de>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: parentheses matching failure on valid sexp
Date: Tue, 11 Sep 2007 08:07:30 +0100	[thread overview]
Message-ID: <863axlof2l.fsf@macs.hw.ac.uk> (raw)
In-Reply-To: <86abrtof9p.fsf@macs.hw.ac.uk> (Joe Wells's message of "Tue\, 11 Sep 2007 08\:03\:14 +0100")

Joe Wells <jbw@macs.hw.ac.uk> writes:

> Sven Joachim <svenjoac@gmx.de> writes:
>
>> Joe Wells <jbw@macs.hw.ac.uk> writes:
>>
>>> To reproduce this bug:
>>>
>>> 1. Save the attached file as foobar.el.
>>> 2. Run “emacs -Q foobar.el”.
>>> 3. Delete the trailing right parenthesis on line 435.
>>> 4. Type a right parenthesis.
>>>
>>> The correct behavior would be to match the leading left parenthesis on
>>> line 1.  The actual buggy behavior is that the message “Mismatched
>>> parentheses” is given.
>>>
>>> This bug is sensitive to the size of the input.  If you delete much of
>>> the input, then the bug goes away.
>>
>> This is documented behavior, see the variable blink-matching-paren-distance:
>
> Thank you for pointing this out!

I suggest there should be a different error message ("Could not find
matching parentheses within %d characters") if the failure is due to
exceeding the blink-matching-paren-distance limit.  The current
message of "Mismatched parentheses" in this case makes one think the
error is due to a bracket matching a brace, or something like that.

-- 
Joe




  reply	other threads:[~2007-09-11  7:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11  5:24 parentheses matching failure on valid sexp Joe Wells
2007-09-11  5:59 ` Sven Joachim
2007-09-11  7:03   ` Joe Wells
2007-09-11  7:07     ` Joe Wells [this message]
2007-09-13  6:40       ` Andreas Röhler
2007-09-11  6:46 ` martin rudalics
2007-09-11 12:55   ` Stefan Monnier

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=863axlof2l.fsf@macs.hw.ac.uk \
    --to=jbw@macs.hw.ac.uk \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=svenjoac@gmx.de \
    /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.